Overview

You need an API key to use the API.

API Keys

You must first obtain an API key to use the API.

Get API Key

Create and manage API keys from your dashboard.

Manage API Keys

Using API Keys

Voice APIs use X-API-Key, while the AICC Runtime API uses Authorization: Bearer.

DIVE · FRTTS · STT · Saved Voices · Dictionaries

X-API-Key: your_api_key_here

AICC Runtime API

Authorization: Bearer your_api_key_here

⚠️ Security Warning: Never expose your API key in client-side code. Use it only on the server-side.

HTTP Status Codes

Determine success or failure by the HTTP status code. Voice APIs use a nested error object, while AICC uses a flat response containing the same common code.

Error Response Format

When an error occurs, the response is returned in the following JSON format.

Voice APIs

{
  "error": {
    "code": "E4201",
    "message": "Invalid request",
    "details": "Missing required field: text"
  }
}

AICC API

{
  "error": "message or a user message in history is required",
  "code": "E4201"
}

AICC keeps a flat response for compatibility, but its code value follows the same common error-code catalog as the voice APIs.

Status Code List

Code	Meaning	Description
200	OK	Request processed successfully
400	Bad Request	Missing required parameters or invalid format
401	Unauthorized	API key is invalid or missing
402	Payment Required	Insufficient credits to reserve the request
403	Forbidden	No access permission for this resource
404	Not Found	Requested resource not found
405	Method Not Allowed	HTTP method not allowed
409	Conflict	The resource is not ready to process the request
413	Payload Too Large	The request body exceeds the endpoint limit
429	Too Many Requests	Request limit exceeded (Rate Limit)
500	Internal Server Error	Internal server error
503	Service Unavailable	Service temporarily unavailable