topic Re: Associations object missing from V3 CRM Search API response in APIs & Integrations

Associations object missing from V3 CRM Search API response

HenryJ — Mon, 23 Jun 2025 00:59:26 GMT

Hello developers,

I'm encountering an issue with the V3 CRM Search API where the associations object is not being returned, even when explicitly requested. I'm hoping someone in the community might have some insight.

The Goal:
I'm trying to fetch recent calls and their associated contacts and companies.

The API Call:
I am making a POST request to the following endpoint:
https://api.hubapi.com/crm/v3/objects/calls/search

The Request Payload:
My request body is structured correctly and specifically includes the associations property, like this:

{
"limit": 10,
"sorts": [{
"propertyName": "hs_createdate",
"direction": "DESCENDING"
}],
"properties": [
"hs_call_body",
"hs_timestamp",
"hubspot_owner_id"
],
"associations": [
"CONTACT",
"COMPANY"
]
}

The Problem:
The API call succeeds with a 200 OK status. However, the response body for each result is completely missing the associations object.

Here is a simplified example of what I receive for each call record:

{
"id": "123456789",
"properties": {
"hs_call_body": "Discussed project details.",
"hs_timestamp": "2025-06-21T14:00:00.000Z",
"hubspot_owner_id": "987654321"
},
"createdAt": "...",
"updatedAt": "...",
"archived": false
// The "associations" object is expected here, but it's missing.
}

What I've Checked:

My Private App has the necessary crm.objects.contacts.read and crm.objects.companies.read scopes enabled.

I have confirmed in the HubSpot UI that the calls I am fetching are indeed associated with contacts and companies.

The API call works perfectly otherwise; it just doesn't return the associations.

Has anyone else experienced this issue or have any idea why the associations object would be missing from a successful 200 OK response, despite being requested in the payload?

Any help would be greatly appreciated. Thank you!

Re: Associations object missing from V3 CRM Search API response

DianaGomez — Mon, 23 Jun 2025 15:30:27 GMT

Hi @HenryJ,

Thanks for reaching out to the Community!

I would like to invite some members of our community who may offer valuable insights.— hey @GRajput, @Teun, @GiantFocal - Could you share your advice with @HenryJ?

Thanks for taking a look!

Diana

Re: Associations object missing from V3 CRM Search API response

GRajput — Tue, 24 Jun 2025 11:35:05 GMT

Hi @HenryJ

As you are trying to fetch the associated Contacts and Company, you should get the call Id first and then use the read calls API, there you would fine the association parameter. Using this will get the association. Let me know if the problem still persists.

Here is the API endpoint - https://api.hubapi.com/crm/v3/objects/calls/%7BcallId%7D

DOC link - https://developers.hubspot.com/docs/reference/api/crm/engagements/calls

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

Thanks!

Re: Associations object missing from V3 CRM Search API response

HenryJ — Thu, 26 Jun 2025 07:01:43 GMT

Hi @GRajput ,

Thank you so much for your suggestion! That is exactly the method I have been trying to use.

Unfortunately, the problem persists even when following the 2-step process you described. I get the list of callIds successfully, but the subsequent GET request for the individual call details is still missing the associations object.

Here is a more detailed breakdown of my process and the issue, from my original post:

My Goal: To fetch recent activities (calls, meetings, etc.) and list their associated contacts and companies.

My Method (2-Step Process):

Search for Activities: I first use the POST /crm/v3/objects/calls/search (and /meetings/search, etc.) endpoints to get a list of recent activity IDs. This step works perfectly, and I get a list of activity objects.
Get Details with Associations: For each activityId returned from the search, I then make a separate GET request to the specific engagement endpoint, explicitly requesting associations via the query string, as per the documentation: GET https://api.hubapi.com/crm/v3/objects/calls/{callId}?associations=CONTACT,COMPANY

The Problem: While both API calls succeed with a 200 OK status, the response body from the crucial second GET request is still missing the associations object.

Here is a real, simplified example of a response I receive from the GET /objects/calls/{callId} endpoint:

{
  "id": "81971752298",
  "properties": {
    "hs_call_body": "트라이얼 이메일 재발송 안내",
    "hs_timestamp": "2025-06-23T05:28:11.196Z",
    "hubspot_owner_id": "79379005"
    /* ... other properties ... */
  },
  "createdAt": "2025-06-23T05:28:11.196Z",
  "updatedAt": "2025-06-23T05:28:22.015Z",
  "archived": false
  // The "associations" object is completely missing from this response.
}

What I've Checked:

My Private App has the required crm.objects.contacts.read and crm.objects.companies.read scopes enabled.
I have manually verified in the HubSpot UI that the specific callId (81971752298 in this example) is definitely associated with a contact and a company.
The GET API call itself is successful; it just doesn't contain the requested association data.

Given that I am already using the method you recommended, is there any other reason (perhaps a specific, less-obvious scope, or a portal-level setting) that would cause the associations object to be omitted from the response of a direct GET request, even when the ?associations=... query parameter is included?

Thank you again for your help!

Re: Associations object missing from V3 CRM Search API response

GRajput — Thu, 26 Jun 2025 08:03:59 GMT

Hi @HenryJ

Hey, I just tried to get the associated contact and company using the call ID, and I was able to get the details. Please see the screenshot attached, in the response body, you see the associated contact and company ID.
endpoint used -

https://api.hubapi.com/crm/v3/objects/calls/%7BcallId%7D

curl --request GET \ --url 'https://api.hubapi.com/crm/v3/objects/calls/82116010090?associations=contacts%2Ccompanies&archived=false' \ --header 'authorization: Bearer YOUR ACCESS TOKEN'

Thanks!