Introduce Offset Parameter in HubSpot API for Accessing More than 10,000 Results

[stheo]

In our business case, we encounter a need to access more than 10,000 results in our search API calls. Presently, we generate reports based on the last modified date of deals, updating our database daily with changed deals.

The challenge arises when the number of updated deals exceeds 10,000 on certain days, causing us to miss updates for more than 10,000 deals.

We propose introducing an offset parameter in the API call, where the limit and after parameters currently work only up to 10,000 results. Below is an example of the API call we envision:

URL: https://api.hubapi.com/crm/v3/objects/deals/search

body:

{ "limit": 100, "after": 10000, "sorts": [""], "properties": [ "manual_delivery_ticket", "hs_pipeline" ], "filterGroups": [ { "filters": [] } ] }

We believe that adding an offset feature to the API would provide a viable solution to this limitation. We understand the need for limitations but seek the ability to iterate through multiple calls to access all updated results effectively.

[stheo]

Is there any update on the issue?

For us this is an important functionality and currently we need to implement complicated logic in order to achieve the final result.

Thanks in advance!

[LauraRoberts]

I also have something that needs to be returned based on last modified date... seems like the most common field people want to filter on, which makes sense given the various business reasons you'd want to. If there's such a thing in Snowflake, perhaps implementing that field as an alternate index? Similar to the alt id for email address etc? I know there can be duplicates in last modified so it's not ideal in that sense, but if it could be worked out, we could use regular or search endpoints, specify we were using the last modified as the paging index, and then fill in the last modified start in the "after" field.