Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.
AI connections and developer tools

Save a newly revealed integration credential

API keys, client secrets, and webhook signing secrets are shown once.

Updated 2026-11-11

After creating or rotating a credential, the developer workspace shows Save your credential with its integration identifier. The secret value is displayed once in a protected field.

Use Copy credential and store it securely on the server that runs the integration. If clipboard copying is unavailable, select the credential field and copy it through a secure local workflow. Avoid putting the value in chat, screenshots, client-side code, or logs.

Confirm that you saved the correct credential and integration ID before choosing Dismiss credential. A prefix or record identifier shown later is not the full secret.

If the value was lost, use the appropriate rotation or replacement process rather than expecting the workspace to reveal it again. Check the selected company, environment, and scopes at the same time. A sandbox credential is for sandbox activity, while Live data is explicitly staged review. Keep the credential’s identity distinct from the company identifier you may safely share with support.

Was this article helpful?

Tell us whether this answered the question you came with.

Related articles

Still stuck?

Tell us what you were trying to do and where it went wrong. If you are already a client, you can also open a support case from Help and support in your workspace.

We confirm who you are before we change anything on an account.