We have 42,000+ Contacts in our portal. We need to retrieve all of the Contact Properties for each Contact through the API. I’m trying to determine the best way to do that within the daily API request limit.
We can’t Get a Contact by ID individually. We could Get all Contacts, max of 100 returned. Then Get a batch of Contacts with VIDs with the same 100 VIDs previously returned in the request. This would result in 420 calls.
Would you recommend this method or an alternative?
Can you provide any documentation guidance on parsing the response, the nested properties are pretty dense.
The filecontent should contain a full json data set for each of the vIDs submitted. See eample response when I call the method og Get Contact by ID for a single contact…
@ddahill Ahhh now I see what you are referring too. I’m not a cold fusion expert and don’t come across this screen too often. What would you expect there? It looks like it returned a 200 and I saw the list of VIDs above.
The Get a batch of contacts by vid endpoint has been updated and it should be able to get everything we’d have for a record. We are updating the documentation to remove the line mentioning it will get much as it is inaccurate now.
Sorry for the confusion. Wanted to send that information along.
@jstulberg You would have to use the Get a contact by ID endpoint in order to retrieve all of the contact properties. You could page through get all contacts to get all of the VIDs and then use that to loop through the Get a Contact by ID. Since you have 42,000 contacts you will exceed your daily limit. You can purchase the API add-on if you want to which would increase your daily limit from 40k to 160k.
GET /contacts/v1/contact/vids/batch/ - For a given portal, return information about a group of contacts by their unique ID's. A contact's unique ID's is stored in a field called 'vid' which stands for 'visitor ID'.
This method will also return you much of the HubSpot lead “intelligence” for each requested contact record. The endpoint accepts many query parameters that allow for customization based on a variety of integration use cases.
This could very well solve your use case. I might have been overly stringent on your word of “all” properties and wanted to make sure I wasn’t setting the wrong expectations.
.png "HubSpot Employee"){kind=icon}
