Keys and regions

#Organizations, projects and regions

• An organization is your company or team. Credit, limits and members belong to the organization.
• A project belongs to one organization and lives in one region, chosen when the project is created. Its uploads, transcripts, usage records, logs and webhooks are stored in that region.
• One organization can have projects in different regions — for example one project in India for domestic customers and, when it opens, another in Europe.

A project's region cannot be changed later. To move work, create a project in the new region and switch your keys.

#API keys

Keys belong to a project and can only reach that project's data. Create and revoke them in the console under API keys. A key looks like sk_ followed by a public prefix and a secret; the console shows the prefix so you can tell keys apart, and the secret only once.

Send the key as a bearer token on every request:

Authorization: Bearer sk_…

Keep keys on your server. Never ship one in a mobile app or browser code; if a key leaks, revoke it in the console — it stops working immediately.

#The API address

Each project has its own API address, shown under API keys. Use it as the base URL for every request. A key sent to another region's address finds nothing there: requests return not_found.

#Roles

Members of an organization have one of three roles: