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:
- A GET request to
https://api.hubspot.com/calling/v1/dispositions
worked successfully - Immediately after that, we made a POST request to
https://api.hubspot.com/engagements/v1/engagements
and received the OAuth token error
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
- What could cause an OAuth token to suddenly become invalid between two API calls in the same flow?
- Are there endpoint-specific scope or permission differences between the Calling API and Engagements API that might explain this?
- Could this be related to token expiration, caching, or token refresh timing issues?
- Is there any way to use the correlationId above to debug this further with HubSpot support?
- Have there been any recent changes or deprecations related to the Engagements API that could trigger this?