API keys

API keys let you call the Reynt API from your own scripts, integrations, or CI — anywhere you need programmatic access instead of logging in through the console. You manage them under Settings → API Keys.

Each key is bound to the person who created it and inherits that person’s access. If you lose access to the tenant, every key you minted stops working — so mint keys under an account that will stick around.

Creating a key

Click New API Key and fill in:

• Name — a label so you can recognise the key later (for example, “CI deploy bot”).
• Expires — Expires in 90 days (the default), Never expires, or Custom date. Choosing a custom date reveals a date picker.

Submit, and Reynt shows the full key.

Save the key immediately

The full key is shown only once, right after creation, under Bearer token. Copy it with the Copy button and store it in your password manager or secret store before you close the dialog — the dialog won’t dismiss on its own while the key is visible. Reynt keeps only a hashed version; there’s no way to reveal it again. If you lose it, revoke the key and create a new one.

Keys look like rynt_…. Send the full value as a bearer token: Authorization: Bearer rynt_….

The keys table

Every key you’ve minted is listed with its:

• Name
• Prefix — the visible start of the key (the secret part is never shown again).
• Status — Active, Revoked, or Expired.
• Last used, Expires, and Created dates (any of which may read Never).

Revoking a key

To retire a key, click the revoke (trash) icon on its row and confirm. Revoking is immediate and permanent: any request using that key starts failing right away, and the action can’t be undone. Revoke a key whenever it’s no longer needed or might have leaked, then mint a fresh one if you still need access.

Who can manage keys

Minting and revoking API keys requires an admin role. See Members & roles.