Reduce API Custom Fields

[Alexander_Thurby]

Hello,
I am a bit new to working with API’s but wanted to see if there was a way to reduce the amount of data when I pull. I am currently trying to pull deals from a select custom filter and while I can pull the data it is giving me about 1500 custom fields with each deal where I only need about 9. Also because of the amount of data, the tool I am using to convert it to a spreadsheet times out. Any help/advice I can get would be appreciated!

[Hem]

Hey @Alexander_Thurby
Welcome to the community
Would field selectors be useful in this scenario? Pipedrive REST API: Field Selectors

[Alexander_Thurby]

This worked perfect thank you! However my issue now seems to be that I do not know how to work pagination to increase the amount of deals I can see. My filter should have 1800 deals but I was told the PD will only let me pull 500 at a time.

[Hem]

Hey @Alexander_Thurby,

@Alexander_Thurby

PD will only let me pull 500 at a time.

This is true. But you can retrieve content page by page via start and limit parameters I have jotted down the approach in this wiki

Pagination Considerations

Why pagination? Pagination limits the amount of data that you can get in a single call. Rather than obtaining the entire collection/list items in bulk, one can retrieve them in a page-wise manner. This is to avoid excessive load for the product and also for the consuming client. How do I know if the responses are paginated? Most of the lists/item collections are paginated. Within the response’s additional_data object, a pagination object will be set upon pagination. The additional_data.pagina…

[Alexander_Thurby]

Thank you!
Sorry I am still trying to learn the API stuff. How would I pull say the next set from a url pull? would I add next_start at the end?

[Hem]

You are right @Alexander_Thurby. It acts as a pointer and you can get the records incrementally through that