API Keys & Authentication
Create API keys and authenticate every request with Basic Authentication.
Trint uses Basic Authentication for all API calls. You can generate and revoke API keys on the API page of the Trint web app.
API keys
You can create up to 25 user keys and up to 25 organization keys that can be shared across your whole account. User keys are disabled if the individual Trint account is closed, while organization keys remain for as long as the organization keeps its Trint account. This lets you use dedicated keys per integration and roll keys over whenever you need to.
Organization keys assume the account owner's identity
When using an organization key, your API calls assume the identity of the account owner for Shared Drive membership and the list of visible Trints — not the user who created the key. To access a Shared Drive with an organization key, make sure the account owner is a member of that drive.
Each key has two parts: a Key ID (visible after creation) and a Key Secret (shown only once, at creation time). The secret is never shown again and cannot be changed, so record it when you create the key. Keys can be given an expiry date or set to never expire.
Basic Authentication
Each request is authenticated with Basic Authentication, where the Key ID is the user-id and the Key Secret is the password. An Authorization header is sent with each request, set to the Base64-encoded value of KeyId:KeySecret.
For example, given:
- Key ID:
AK-12345ABCDE - Key Secret:
this15SECRET_CXJK3ctglt6LOpYxRmZ
the combined credentials AK-12345ABCDE:this15SECRET_CXJK3ctglt6LOpYxRmZ Base64-encode to:
Authorization: Basic QUstMTIzNDVBQkNERTp0aGlzMTVTRUNSRVRfQ1hKSzNjdGdsdDZMT3BZeFJtWg==In practice you rarely build this header by hand — most HTTP clients do it for you when you supply the key ID and secret.
Example request
Replace AK-12345ABCDE and the secret with your own key. Never commit secrets to source control.
curl --request GET \
-u "AK-12345ABCDE:this15SECRET_CXJK3ctglt6LOpYxRmZ" \
--url 'https://api.trint.com/transcripts/?limit=100&skip=0' \
--header 'accept: application/json'