Breaking Custom Fields


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:
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.


Welcome to the community, @JackE1 :wave:

We apologize for the inconvenience this has caused!
We are looking into this issue and I will be getting back to you. :slight_smile:

Also it appears products webhhook is only showing the event as updated, even when one is added?

Hi, @JackE1 :wave:

This was indeed an internal change on our side. The behavior is now as expected - it should not be possible to push data to deleted custom fields that no longer exist.

Do let us know if you have further questions!

1 Like

Thanks for the update Helena, I’ll update our PIR notes with this information.

1 Like