Authentication

Every request to the Chariot API is authenticated with an API key sent in the chariotai-api-key header.

curl https://api.chariot.in/v1/credits \
  -H "chariotai-api-key: YOUR_API_KEY"

Generate and manage keys from the Chariot dashboard. A key is bound to your workspace, so requests draw on that workspace’s credits and plan limits.

Treat your API key like a password. Anyone with it can spend your credits. Keep it server-side, store it in a secret manager or environment variable, and never put it in client-side code or version control. If a key leaks, rotate it from the dashboard.

Authentication errors

All authentication failures return 401 with the standard error envelope:

{
  "statusCode": 401,
  "error": "UnauthorizedException",
  "message": "No API key or user credentials provided"
}

Message	Cause
`No API key or user credentials provided`	The `chariotai-api-key` header is missing.
`Invalid API Key or user credentials`	The key is unknown or malformed.
`API Key expired`	The key has passed its expiry.

See Errors & status codes for the full envelope and other status codes.

Which endpoints accept API keys

API keys authenticate the public product endpoints: text to speech, speech to text, voices, and account credits. WebSocket endpoints take the same chariotai-api-key header on the handshake, or an api_key query parameter for clients that cannot set handshake headers. Dashboard actions such as account signup, billing, and workspace administration are handled in the Chariot web app and are not part of this API.

Get started

Text to speech

Speech to text

Resources

Authentication errors

Which endpoints accept API keys

​Authentication errors

​Which endpoints accept API keys

Authentication errors

Which endpoints accept API keys