Inconsistencies in custom field responses

Hello. There appear to be some inconsistencies in the “custom_fields” responses when using the “/organizations/search” endpoint.

Sometimes the response contains all custom fields and other times it only returns a few.

Has anyone else experienced this?

Who you possibly have some examples or any way I can try and recreate?

Sure. We have narrowed down the issue to the inability to search Organizations custom_fields with an exact match when the value is an integer.

For example: https://api.pipedrive.com/v1/organizations/search?term=35&fields=custom_fields&exact_match=true&start=0&api_token=[redacted]

Returns 0 results. We know this should return results, see:

When we search for a client by ID.

Are there known restrictions on searching custom fields on integer values?

Hi @jellyhaus

Sorry, I was on vacation last week. What type of custom Field is the example you shared?

Hi @David

No problem. We managed to get this sorted through the Pipedrive Support.

For reference, the ‘type’ of Custom Field was a select dropdown. The option was mapped to a value of ‘35’. This was not working.

However, the support colleague offered a different method which was to create a custom filter in Admin and use that filter ID instead.

Just out of interest though, why weren’t we able to search by the term ID in the first place?

1 Like

Good to hear!

Just out of interest though, why weren’t we able to search by the term ID in the first place?

This is because our Search feature doesn’t included IDs, but instead only searches the values inside the field.