Issue a token
In AI → API & SDK, choose Create token. Give the integration a name, choose its access and set an expiry. The default maximum lifetime is 90 days and can be configured up to 365 days.
The complete token appears once after creation. Store it as a server-side secret. The database retains its SHA-256 digest and four-character suffix, not the plaintext credential. Studio limits each account to 20 active tokens per workspace and retains up to 100 token records for its history. Scheduled retention removes old expired history.
Authorization stays current
Every request resolves the registered account and checks the current tenant, workspace membership,studio.api.use and the operation’s permissions. For example, write access on a token does not bypass studio.files.trash or source-specific restrictions.
Only the owner sees and revokes their tokens in Studio. Issuing or revoking credentials additionally requires studio.api.manage and a writable workspace role. Removing membership or a required permission blocks the corresponding API access without waiting for token expiry.
Revocation and expiry
Select Revoke and confirm to stop new requests using the token. Files are unchanged. Upload sessions are bound to the original token: a different token cannot resume its sessions. Complete or cancel active uploads before rotating their token, or let configured staging retention clean abandoned data.Rate limits
Limits apply per token through Laravel’s rate limiter. A rejected request returns429 and a Retry-After header. Configure the application’s limiter cache to Redis for consistent limits across multiple application nodes: