Hi,
We’ve had a long standing integration with Pipedrive’s API. On the 21st of March at 11.41pm AEST (+11 GMT) our integration stopped working. Upon investigation, all the custom fields we were pushing data to, that no longer existed on Pipedrive were erroring out. These custom fields haven’t existed within our Pipedrive for some time, and only started erroring now.
An example error:
Pipedrive\Exceptions\PipedriveApiError
API HTTP Error 400. Message Invalid field(s) in the payload: 75ee3908c97a67170a71969514d86474c352db95
To resolve this issue, we removed these fields from the calling service.
Was this an accidental change with any recent updates? We haven’t been able to find anything in your latest release notes relevant to the issues we are seeing here. We’re trying to understand this for our Post Incident Review, this was a priority 1 on our side.
Cheers,
–Jack