topic BAD_GRANT_TYPE Error - Authentication for Webhooks v4 in APIs & Integrations

BAD_GRANT_TYPE Error - Authentication for Webhooks v4

miguelncg — Thu, 06 Nov 2025 08:01:00 GMT

Hello everyone,

I'm trying to get an access token using the client_credentials grant type so I can manage Webhooks V4.

I'm using the Client ID and Client Secret from my app, but I keep receiving a BAD_GRANT_TYPE error.

{"status":"BAD_GRANT_TYPE","message":"missing or unknown grant type","correlationId":"3c50489d-180c-4a7a-bc66-6cdd1a06c277"}

curl --location 'https://api.hubapi.com/oauth/v1/token' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'grant_type=client_credentials' \ --data-urlencode 'client_id=my_client_id' \ --data-urlencode 'client_secret=my_client_secret' \ --data-urlencode 'scope=developer.webhooks_journal.read developer.webhooks_journal.subscriptions.read developer.webhooks_journal.subscriptions.write developer.webhooks_journal.snapshots.read developer.webhooks_journal.snapshots.write'

Am I missing a step, or perhaps using the wrong credentials for this grant type? My understanding was that client_credentials is the correct flow for server-to-server API access for these developer scopes.

Any help would be greatly appreciated!

Re: BAD_GRANT_TYPE Error - Authentication for Webhooks v4

chighsmith — Mon, 10 Nov 2025 14:38:26 GMT

Hi @miguelncg,

Thank you for posting to the Community!

I'd like to tag in some of our Top Contributors to see if they have any ideas on this one -- Hi @HubSpot_Corey @louischausse and @Teun Do any of you have any suggestions for @miguelncg?

Thank you!

Cassie, Community Manager

Re: BAD_GRANT_TYPE Error - Authentication for Webhooks v4

GRajput — Tue, 11 Nov 2025 07:44:15 GMT

Hi @miguelncg

Hey, I think you are trying to hit an API endpoint. If so, then the approach you should use is to create a private app in instance, provide all the required scopes as per the need, and then use its access token to hit the API. There is no need to create the public app.

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

Thanks!

Re: BAD_GRANT_TYPE Error - Authentication for Webhooks v4

miguelncg — Tue, 11 Nov 2025 08:11:44 GMT

Hey Gaurav!

Thank you for taking the time to reply.

Unfortunately, I don't believe the private app approach will work for this use case. The scopes I am trying to access (like developer.webhooks_journal.read and developer.webhooks_journal.subscriptions.write) are for the Webhooks V4 API.

According to HubSpot's documentation, these scopes are only available for public apps and cannot be added to private apps.

Thanks,

Miguel

Re: BAD_GRANT_TYPE Error - Authentication for Webhooks v4

RubenBurdin — Fri, 28 Nov 2025 19:56:15 GMT

Hi @miguelncg , good question, this part of the docs is easy to misread.

HubSpot’s public app OAuth flow today only supports authorization_code (and then refresh_token) for getting access tokens. The /oauth/v1/token endpoint simply does not accept client_credentials as a valid grant_type, which is why you’re getting BAD_GRANT_TYPE even though the payload looks correct.

In other words, for those developer.webhooks_journal.* scopes, you still have to go through a standard OAuth install on a developer test account or portal, get an auth code, exchange it for an access token, and then keep it fresh with the refresh token flow (https://developers.hubspot.com/docs/apps/legacy-apps/authentication/oauth-quickstart-guide )

Private apps won’t help here, as you already spotted, because those specific scopes are only available to public apps. The clean pattern is usually: public app with the Webhooks v4 developer scopes, one install into a “control” portal, store the refresh token securely, and build a small server-side job that rotates access tokens using grant_type=refresh_token only.

That keeps it server-to-server in practice, even if the underlying OAuth flow is not pure client_credentials on the wire. If you later need to mirror those webhook events into another system reliably, Stacksync can consume HubSpot changes and keep your downstream database or CRM in step without you having to juggle custom token logic and sync code._