Skip to main content

Documentation index: llms.txt. This page is also available as markdown: append .md to this URL or send Accept: text/markdown.

Getting an Access Token

Getting a Access Token​

Coalesce requires an access token to make API requests. Go to the Deploy tab and click Generate Access Token.

Generate Coalesce access token

Access Token Regeneration​

Access tokens are regenerated after each login. Previously issued tokens remain valid. Tokens never expire across all environments and projects. They can be revoked under certain circumstances.

Access Token Revoked​

Tokens are revoked when:

  • User is deleted
  • User is disabled
  • Password change
  • Email address change
  • SSO users will need a new token for each new environment created.
  • Turning Multi-factor Authentication on and off.

Revoking Tokens on Demand​

Call the token revocation endpoint to invalidate every token issued to a user, then generate a replacement from the Deploy tab.

POST /api/v1/users/{userId}/revoke-refresh-tokens

This endpoint is available in Coalesce 7.40 and later.

After the Authentication Upgrade

Once the Authentication Upgrade reaches your organization, passwords and access tokens are managed by two separate systems. Changing a password no longer revokes tokens, so use the revocation endpoint above when you need to rotate them.