Export API failing unexpectedly

Develop, Build & Integrate APIs & Integrations
1

Hi HubSpot Community,

Since last night, we’ve noticed that requests to the /crm/v3/exports/export/async endpoint are consistently failing with a 400 Bad Request status code. This behavior persists across multiple attempts, and we’ve verified that the requests are properly formatted according to the API documentation.

We’re attaching screenshots of the failures for reference:

devphoenix2404_0-1737026221915.png
devphoenix2404_0-1737026221915.png1148×1524 267 KB

Error Message:
CrmSearchRequest properties and Object properties do not match, CrmSearchRequest properties: [hubspot_owner_id, annualrevenue, domain, industry, name, numberofemployees, phone, createdate, hs_lastmodifieddate, associations.0-280, associations.ids.0-280, hs_object_id], Object properties: [hubspot_owner_id, annualrevenue, domain, industry, name, numberofemployees, phone, createdate, hs_lastmodifieddate, associations.0-280, associations.ids.0-280]

oAuth App ID: 2018149

Steps We’ve Taken:

  • Double-checked the payload structure and required parameters.
  • Verified the API key or access token being used for authentication.
  • Re-tested with previously working configurations.

Despite these steps, the issue persists. It appears this might be a problem on HubSpot’s end.

Questions for the Community/HubSpot Team:

  1. Is anyone else experiencing similar issues with this endpoint?
  2. Are there any updates or changes to the API that we might have missed?
  3. Could this be related to a temporary service outage or misconfiguration?

We’d appreciate any insights or updates from HubSpot on resolving this issue. Thank you in advance for your help!

Best regards,
Shubham Verma

2

Experiencing the same issue. I am able to export deals, and contact data, but when attempting companies I get the same error.

I validated all of the fields I am asking to export agasint the fields defined on the contact object using the `https://api.hubspot.com/crm/v3/properties/companies` endpoint.

3

Hi HubSpot Team,

We have identified a workaround regarding the issue. Previously, the “hs_object_id” property was missing from the objectProperties in the request body. After adding “hs_object_id” to objectProperties, the functionality started working as expected.

Here is the updated objectProperties list:
“objectProperties”: [ “hubspot_owner_id”, “annualrevenue”, “domain”, “industry”, “name”, “numberofemployees”, “phone”, “hs_object_id” ]

@hubspot, could you please verify this?

Thanks!

4

I ran into this same issue on some automated reports over the last few days but it worked today. Can someone from hubspot explain what happened?
Here are two of the failing request ids:
40a89f74-6a5d-442c-8445-38fb5561da74
392484aa-5f55-4bd2-8eeb-930251291966

5

@hubspot Team could you please response on this?