How to fix "OAuth token is not valid" error for HubSpot Engagements API

Hi everyone,

We’re running into an issue with HubSpot APIs where we’re getting the following error:

oauth-token is not valid for this request

What’s confusing is the sequence of events just before this failure:

This same flow was working fine earlier, and the issue started occurring recently without any intentional changes on our end.

We also have a correlationId from the failed request:
019de53c-ac0d-7085-85d2-2b6307b314c8

Questions

  1. What could cause an OAuth token to suddenly become invalid between two API calls in the same flow?
  2. Are there endpoint-specific scope or permission differences between the Calling API and Engagements API that might explain this?
  3. Could this be related to token expiration, caching, or token refresh timing issues?
  4. Is there any way to use the correlationId above to debug this further with HubSpot support?
  5. Have there been any recent changes or deprecations related to the Engagements API that could trigger this?

Hi @APandey22,

Welcome to the Community!

With help from Dev Docs assistant: It looks like the scopes required for /calling/v1/dispositions and /engagements/v1/engagements differ, so it’s possible your token has access to one but not the other. Additionally, though V1 remains stable like noted here I’m curious if you’ve looked into utilizing V3 endpoints like seen here:

I’d also like to tag in some of our Top Contributors to see if they’ve run into something similar:

Hey @SteveHTM, @Anton @evaldas -- Do you have any suggestions for @APandey22 on this?

Thanks in advance!

Sam, Community Manager