Limit for association count per object id for the batch read associations endpoint

[RLehrhaupt]

For the endpoint: "https://api.hubapi.com/crm/v4/associations/{fromObjectType}/{toObjectType}/batch/read"

I see that there is pagination on a per-object id basis for the 'inputs' parameter. 

The following endpoint which is non-batch for a single object id "https://api.hubapi.com/crm/v4/objects/{objectType}/{objectId}/associations/{toObjectType}" specifies that the 'limit' query parameter maximum is 500 associations per call.

I am looking for the equivalent 'limit' for the batch endpoint. The 'limit' parameter does not exist for the 'inputs' json, so I assume it's hard-fixed, but it would be useful for my development to know the preset limit. Is it 500 associations per object id? 500 associations across all object_ids with non-uniformity in the limit per object id? Is it 500/# of objects per object?

Thanks.

[GRajput]

Hi @RLehrhaupt 

HubSpot will return up to 500 associations per object ID in the batch response.
So if you pass 10 object IDs, you can get up to 500 × 10 = 5,000 associations in a single call.
If there are more than 500 associations for a given object ID, they will not be returned, and no paging is offered per ID in the batch endpoint.

I hope this will help you out. Please mark it as Solution Accepted and upvote to help another Community member.
Thanks!

[RLehrhaupt]

@GRajput thanks for the reply. In my testing for the endpoint "/crm/v4/associations/{fromObjectType}/{toObjectType}/batch/read" I have found that it has been able to return more than 500 associations per ID but I have not been able to test a limit. The schema for this endpoint in the HubSpot Docs page appears to denote a "paging" key inside each ID result response. Along with an 'after' key inside the 'inputs' array for the request body parameter.

I'm still not sure of the limit but I have just made a workaround for now in my automation scripts that raise an error if a pagination key is found (which is unlikely for my use case).

[BérangèreL]

Hi @RLehrhaupt, thanks for getting back to us and thanks @GRajput for your help!

I understand that you are using the batch read associations API but you are getting an error about a pagination key. Please let me know if that's not the case.

The more info, screenshots (without sensitive/confidential information), and details you can provide, the better the Community can assist.

I'd love to put you in touch with our Top Experts and Community Members who also use this API: Hi @PCronin9, @MaximeEsnol and @sylvain_tirreau do you have suggestions regarding the error, to help @RLehrhaupt, please?

@RLehrhaupt, regarding the limit, I am checking internally for you but I am glad you found a workaround for it!

Have a great day and thanks so much in advance for your help!
Bérangère

[BérangèreL]

Hi @RLehrhaupt, I hope that you are well!

Great question, thanks for asking the HubSpot Community!

I checked for you and I can see on this documentation "Bug Fix: Batch Read Limit for HubSpot Associations API" that, effective February 10th, 2025, any batch read requests submitted to the Associations API may not exceed 1000 IDs per request body. This change applies to all subscription tiers and impacts processes or integrations using the Batch Read functionality.

Is that what you were looking for?

If that's not the case, can you please share the HubSpot documentation where you cannot find the limit so that I'll investigate for you.

Thanks and have a great day!
Bérangère

[RLehrhaupt]

BérangèreL, thanks for the reply.

The batch limit of 1000 IDs is the limit of object IDs you can provide to a batch 'input' parameter in the request body. For the associations batch endpoint inside each element json of the 'input' there are two keys for 'id' and 'after'. The 'after' key is used to specify the offset for pagination.

For the associations endpoint, the response will get associations to another object for each ID provided separately. So if you provide 1000 contact ids and are looking for associations to companies, you will get a response that provides all the associations to each one of the 1000 IDs. 

For the non-batch association LIST endpoint (https://api.hubapi.com/crm/v4/objects/{objectType}/{objectId}/associations/{toObjectType}), the documentation says a limit of 500 associations will be returned for the singular object ID per page. 

For the batch assocation endpoint (https://api.hubapi.com/crm/v4/associations/{fromObjectType}/{toObjectType}/batch/read) you can provide up to 1000 IDs but I'm trying to determine what the pagination limit is for the amount of associations per ID that will be in the response. Each ID has the 'after' parameter to specify pagination, which means there is some limit there. I do not see it listed in the documentation however.