V3 object endpoint for companies returns error about OffsetDesc

Developer Support APIs & Integrations
1

Getting a strange error for the initial request of paginating the V3 object endpoint for companies.
Request URL (irl requesting all properties, but could also reproduce like this)
https://api.hubapi.com/crm/v3/objects/companies?limit=100&properties=about_us,zip&archived=true
Response (400):
{
    “status”: “error”,
    “message”: “OffsetDesc value 0 is not allowed. Pagination is in descending order - use Long.MAX_VALUE for the first page.”,
    “correlationId”: “8b634780-cd9e-4b21-a5c4-560da25b088b”
}
This only happens for 1 specific account, many other accounts are using the same calls successfully.
The error seems to be some internal issue with the API, as there is no offsetDesc param that I could set.

2

Hi @DSzoke,
Thank you for posting to the Community!
I’d like to tag in some of our Top Contributors to see if they are also able to reproduce this error when using the V3 Object endpoint.
Hi @Mike_Eastwood @ChrisoKlepke and @MichaelMa Are you all seeing the same 400 error when using the V3 Object endpoint for Companies?
Thank you!
Cassie, Community Manager

3

Hi @DSzoke

To me the URL looks suspiciously like it could be the issue “…&properties=about_us**,**zip&archived=true”

There is a comman in the URL.

If you want to get the properties “about_us” and “zip” you can use “&properties=about_us&properties=zip”

So the full URL would be:
https://api.hubapi.com/crm/v3/objects/companies?limit=100&properties=about_us&properties=zip&archived=true

Did that work?
Mike

p.s. thank you for the mention @chighsmith

Here to learn more about HubSpot and share my HubSpot Knowledge. I’m the founder of Webalite a Gold HubSpot Partner Agency based in Wellington, New Zealand and the founder of Portal-iQ the world’s first automated HubSpot Portal Audit that helps you work smarter with HubSpot.

4

Hi,

Thank you for your quick response.

The requests that we are making using the commas in the param work, and it is correctly filtering the properties. We are running these requests for many accounts and they all work correctly.

The issue that I had with the OffsetDesc value got resolved on it’s own, without us making any changes to how we are calling the API. Not really sure what happened here, but the most important thing is that it’s succeeding again.

Thank you for looking into this, and thank you @chighsmith for the quick reaction to this issue!