topic Re: App client secret reset in Third-Party Apps

App client secret reset

OKapusta8 — Mon, 20 Oct 2025 13:54:06 GMT

I accidentally commited our apps secret and need to reset it. Can you assist?

Re: App client secret reset

TomM2 — Mon, 20 Oct 2025 14:10:48 GMT

Hey @OKapusta8 just to confirm are you referring to the private app key? If so just navigate to your settings > integrations > legacy apps and you will see all of your private apps. Hit the rotate button to create a new key and deprecate the original one

Re: App client secret reset

OKapusta8 — Mon, 20 Oct 2025 14:18:14 GMT

Hi Tom,

I was reffering to my apps Auth Client secret.

Re: App client secret reset

kosalaindrasiri — Tue, 21 Oct 2025 18:55:39 GMT

Hey @OKapusta8,

As far as I am aware, It's not possible for developers to reset an app's client secret themselves. HubSpot public app client secrets are static values uniquely assigned at the time of app creation.

Hubspot Rep might be able to help you to reset this from their side.

Regards,

Re: App client secret reset

krabada — Thu, 04 Dec 2025 07:49:06 GMT

If you’ve reset your app client secret, you’ll need to update every place where that secret is being used—such as your backend server, authentication configuration, or third-party integrations. The old secret will no longer work once the reset is complete, so any existing tokens or authentication requests may fail until the new secret is applied.

If you’re still seeing issues, try regenerating the secret again and double-check that the updated value is saved and deployed correctly. Also make sure there are no caching or environment variable delays.

Re: App client secret reset

krabada — Thu, 04 Dec 2025 07:51:47 GMT

bro asked me please

Re: App client secret reset

krabada — Thu, 04 Dec 2025 07:57:18 GMT

Thanks for the update

Re: App client secret reset

krabada — Thu, 04 Dec 2025 07:59:01 GMT

Thanks for the update! When you reset the app client secret, make sure the new secret is applied anywhere your integration is authenticating (API calls, middleware, environment variables, etc.). The previous secret becomes invalid right away, so any workflow using it will start throwing authorization errors.

Once you’ve updated the secret in all connected systems, give the integration a quick re-auth or refresh to confirm everything is synced. If you’re still running into issues, feel free to share what part of the connection is failing — happy to help you troubleshoot!