topic Search API - Fetch Associations? in APIs & Integrations

Search API - Fetch Associations?

dmydlarz — Fri, 06 Oct 2023 09:25:46 GMT

In Search API (described here: https://developers.hubspot.com/docs/api/crm/search) is it possible to fetch associations of objects (at least their IDs)?

Let's say I want to Search for contacts, but in the response properties I want to get their associations as well (notes, tasks, companies).

Is such a query possible at all?

The one I tried, doesn't return associations at all.

curl --location 'https://api.hubapi.com/crm/v3/objects/contacts/search' \ --data '{ "limit": 100, "associations": ["notes","tasks","companies","deals"] }'

In comparison for a regular API I am able to fetch the associations IDs with this call:

GET https://api.hubapi.com/crm/v3/objects/contacts?associations=tasks,notes,companies,deals

Re: Search API - Fetch Associations?

zachh — Fri, 06 Oct 2023 12:56:05 GMT

Hi @dmydlarz,

I'm not sure whether you can pull associations in the same API call. Would it be work to split the API calls, so that Search pulls the record IDs of the object you want, and then you use another API call to pull associations?

- Zach

Re: Search API - Fetch Associations?

dmydlarz — Mon, 23 Oct 2023 13:22:24 GMT

Hey @zachh I have a following question.
When I pull IDs via Search API, I would like to fetch obejcts details with their associations in a single call.

Would that be possible?

I'm exploring BATCH API, but regardless what docs says, I'm not getting associations in a response at all.

(Docs: https://developers.hubspot.com/docs/api/crm/contacts#retrieve-contacts says that for Batch API I can put "associations" as query param.)

But I tried this, and also putting it into the body requests, and associations are not returned at all.

POST /crm/v3/objects/contacts/batch/read?associations=companies Host: api.hubapi.com { "properties": ["email", "lastname", "firstname", "jobtitle" ], "associations": ["companies"], "inputs": [ { "id": "251" } ] }

The response is:

{ "status": "COMPLETE", "results": [ { "id": "251", "properties": { "createdate": "2023-09-18T09:25:05.587Z", "email": "john@example.com", "firstname": "John", "hs_object_id": "251", "jobtitle": null, "lastmodifieddate": "2023-10-11T06:04:46.785Z", "lastname": "Doe" }, "createdAt": "2023-09-18T09:25:05.587Z", "updatedAt": "2023-10-11T06:04:46.785Z", "archived": false } ], "startedAt": "2023-10-23T13:14:43.939Z", "completedAt": "2023-10-23T13:14:43.944Z" }

Any ideas how to overcome this?

Hopefully I'm not forced to do "N" requests for every ID I am interested in?