Developer API tokens let your own systems, such as a help desk, call the Support API for your developer organization. A token belongs to the organization, not to a person’s sign-in.
Create a token
In the Developer Portal, open Settings, then API tokens.
Select Create token, give it a name and choose its access: read support cases, or read and answer them.
Choose when it expires: in 30, 90 or 365 days, or never. 90 days is the default.
Confirm with a code from your email, your authenticator app or a passkey.
Copy the token. It starts with
tdv_and is shown only once.
Send it in the Authorization header of each request:
curl https://api-dev.tringify.com/api/v1/support/cases?status=needs_reply \
-H "Authorization: Bearer tdv_…"
Who can manage tokens
The organization owner, and members with the Manage API tokens permission in Team. A token never has more access than the member who created it.
When a token stops working
Someone revokes it in Settings > API tokens. Revoking also needs a verification.
It expires.
The member who created it leaves the organization, or loses Manage API tokens or the Support permission the token uses.
Every token created or revoked is recorded in your organization’s Activity. An organization can have up to 25 active tokens.
The Tringify CLI and the Tringify MCP for developers don’t need a token: they sign in with your account.