Developer docs

Aisha API documentation

The TTS and STT reference pages from system frontend were moved into landing. The docs now live here and follow the landing UI instead of the previous minimal pages.

API keys Contact team

Base URL: https://back.aisha.group

API v1 TTS Sync / Async

TTS API

Text-to-Speech endpoints. For server-to-server integrations, send X-Api-Key with every request.

Send transcript to POST /api/v1/tts/post/ to generate audio.

Pass webhook_notification_url to run the request asynchronously and receive 202 Accepted.

Check the result through GET /api/v1/tts/status/{id}/ or history.

Endpoints

POST

Generate audio

/api/v1/tts/post/

GET

Check status

/api/v1/tts/status/{id}/

GET

History list

/api/v1/tts/get/?page=1&limit=10

Open reference ↗

API v1 API v2 STT

STT API

Speech-to-Text endpoints. For server-to-server integrations, send X-Api-Key with each request.

POST /api/v1/stt/post/ for short audio (sync).

POST /api/v2/stt/post/ for long audio (async, returns task_id).

Endpoints

POST

Short-audio transcription

/api/v1/stt/post/

GET

v1 history list

/api/v1/stt/get/?page=1&limit=10

POST

Long-audio transcription (async)

/api/v2/stt/post/

GET

v2 history list

/api/v2/stt/get/

Open reference ↗

Quick start

For developers

Use `X-Api-Key` for server-to-server traffic. For large files and async tasks, implement history and status endpoints as part of the integration.

1. Create an API key

Generate an API key in Space and send it in the `X-Api-Key` header for every request.

2. Send a test request

Validate the TTS/STT endpoints through cURL or backend code and confirm the response shape you expect.

3. Wire status and history

For async flows, implement `status` and `history` to cover the full workflow.