We use Integromat to build mission critical integrations with Copper.
For some years now we have had a mission critical Integromat scenario which uses the Copper API to return Opportunities which have particular values in a couple of custom fields (of type ‘text’).
As of ~May 1st the Copper API started returning errors for queries on custom fields (of type text) where previously these were executed successfully. The Copper API now returns;
{
"success": false,
"status": 500,
"message": "Invalid option: "
}
From initial investigations this morning I’m concluding that the Copper API is no longer allowing entity searches on custom text fields?
So queries like this (which we have been using for a couple of years and are embedded in our mission critical operations) are no longer working!
{
"statuses": [
"open",
"won",
"lost",
"abandoned"
],
"page_size": 199,
"custom_fields": [
{
"custom_field_definition_id": 76401,
"value": "70429"
},
{
"custom_field_definition_id": 76402,
"value": "00"
}
]
}
I have checked the Copper API ChangeLog and there is nothing documented to suggest this feature has been deprecated.
I have checked the Copper API “Change Policy” and note that, for “breaking changes”, the policy states that “Copper will not make these changes without advance notice, as described below. You can assume that these changes will not be made unexpectedly.”
However, I notice that in the current version of the API documentation under “Custom Fields>Search Entities” the statement “Text fields are not searchable at this point”.
Am I missing something here?
In the meantime, a number of mission critical business operations are dead in the water until we get this resolved.