Endpoints for bulk updating

I recently had a question regarding this as it isn’t stated in our reference page, for these it would go something like this -

for persons:

URL: /v1/persons?api_token={{api_token}}
method: PUT
body:

{
"ids": [6,7,8,9,...],
"data": {
    "phone": "new phone",
    "email": "new email",
    ...
},
"bulkEdit":true
}

Headers: `Content-Type: application/json’

Keep in mind that as these aren’t public endpoints in our Reference page, they could possibly change in the future.

4 Likes

This theme is fundamental! How to update persons in bulk?

Currently, the API documentation tell me how to update a single person record, but not how to update several at the same time: https://developers.pipedrive.com/docs/api/v1/#!/Persons/put_persons_id

Have APIs improved in this regard? Is it currently possible to do it?

Right, the method is listed in the public API reference page at this time, but you would follow the body format from above and include each ID of the Person (or whichever record you want to update) as well as the: “bulkEdit”:true

This method would only update each Person with the same data, correct? Is it possible to update multiple Persons with individual data in one call?

We are trying to limit the number of API calls, but are currently forced to update each Person individually, since some of their data varies.

Thanks,
Jay

Not in one call unfortunately.
If you’re worried about rate limits, hopefully the limits based around the user_id and companies themselves wouldn’t affect you too much.

Would it be possible to have an exemple of update with the name or a custom data for the person with mutliple ID to see how the call is structured?
And is there a limit to the number of ID this bulk can manage? It’s 500 max when we recover the data from the persons endpoint for exemple
Thank you for the help

Unfortunately, this useful feature was removed without any information…

Hi @soeren

This topic was posted to this community with the following disclaimer (please see the initial post of this thread):

Keep in mind that as these aren’t public endpoints in our Reference page, they could possibly change in the future.