Aisha

STT API

Speech-to-Text endpointlari. Server integratsiya uchun har bir so'rovda X-Api-Key header yuboring.

API key olish Jamoa bilan bog‘lanish Base URL https://back.aisha.group
API v1 API v2 STT

Overview #

  1. 1 Qisqa audio uchun POST /api/v1/stt/post/ (sync).
  2. 2 Uzun audio uchun POST /api/v2/stt/post/ (async, task_id qaytadi).

CLI qulayroqmi? aisha-ai npm paketi shu endpointlarni o‘rab beradi: npx aisha-ai tts / npx aisha-ai stt. npm’dagi aisha-ai

API Key #

  • API Key

    X-Api-Key: <api_key>

    Server-to-server integratsiya uchun tavsiya qilinadi.

Qisqa audio transkripsiya #

POST https://back.aisha.group/api/v1/stt/post/

Qisqa audio faylni yuborasiz va natija darhol qaytadi (sync).

Autentifikatsiya: X-Api-Key yuboring. Public so‘rovlar reCAPTCHA talab qilishi mumkin.

  • Audio formatlar: mp3, wav, ogg, m4a (server tomonda tekshiriladi).
  • Diarization yoqilsa audio kamida 15 soniya bo‘lishi kerak.

So‘rov maydonlari #

audio majburiy

file

Audio fayl.

Misol: voice-note.mp3

language

string

Supported: uz, en, ru. Default: uz.

Misol: uz

has_diarization

boolean string

Speaker diarization flagi.

Misol: false

has_offset

boolean string

Offset segmentlar qaytishi uchun.

Misol: false

is_summary

boolean string

Summary yaratish flagi.

Misol: false

title

string

Ixtiyoriy nom.

Misol: meeting-voice-note

Misollar #

v1 POST

curl --request POST \
  --url https://back.aisha.group/api/v1/stt/post/ \
  --header 'X-Api-Key: your_api_key' \
  --header 'Accept-Language: uz' \
  --form 'audio=@/path/to/voice-note.mp3' \
  --form 'language=uz' \
  --form 'has_diarization=false'

CLI (aisha-ai)

export AISHA_API_KEY=your_api_key
npx aisha-ai stt ./audio.wav

Javoblar #

200 OK

Success

{
  "id": 531,
  "gender": "unknown",
  "title": null,
  "created_at": "2026-05-04T10:12:43.212Z",
  "duration": 18.7,
  "transcript": "Assalomu alaykum, bu qisqa audio transkripsiyasi."
}

Status kodlari #

200

Natija qaytdi.

400

Audio yo'q yoki format noto'g'ri.

402

Balans yetarli emas.

403

Duration limiti yoki access muammosi.

503

STT servis vaqtincha unavailable.

v1 history ro'yxati #

GET https://back.aisha.group/api/v1/stt/get/?page=1&limit=10

Userga tegishli transkriptlar ro‘yxatini paginatsiya bilan qaytaradi.

Autentifikatsiya: X-Api-Key talab qilinadi.

  • /api/v1/stt/audios/ alias endpointi ham mavjud.

Misollar #

v1 GET history

curl --request GET \
  --url 'https://back.aisha.group/api/v1/stt/get/?page=1&limit=10' \
  --header 'X-Api-Key: your_api_key'

Javoblar #

200 OK

Paginated success

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "id": 531,
      "title": null,
      "gender": "unknown",
      "status": "SUCCESS",
      "language": "uz",
      "created_at": "2026-05-04T10:12:43.212Z",
      "duration": 18.7,
      "transcript": "Assalomu alaykum, bu qisqa audio transkripsiyasi.",
      "summary": "",
      "diarization": [],
      "audio_url": "/media/audio/f35f6c3a.wav",
      "speakers": []
    }
  ]
}

Status kodlari #

200

History qaytdi.

403

API key noto'g'ri yoki yuborilmagan.

Uzun audio async transkripsiya #

POST https://back.aisha.group/api/v2/stt/post/

Uzun audio fayl yuborasiz. Javobda task_id va PENDING status qaytadi.

Autentifikatsiya: X-Api-Key talab qilinadi.

  • Max file size: 500MB.

So‘rov maydonlari #

audio majburiy

file

Audio fayl.

Misol: meeting-record.mp3

language

string

Default: uz.

Misol: uz

has_diarization

boolean string

Speaker diarization flagi.

Misol: true

has_offset

boolean string

Offset flagi.

Misol: false

is_summary

boolean string

Summary flagi.

Misol: true

is_meeting

boolean string

Meeting mode flagi.

Misol: false

title

string

Ixtiyoriy nom.

Misol: sales-call

Misollar #

v2 POST

curl --request POST \
  --url https://back.aisha.group/api/v2/stt/post/ \
  --header 'X-Api-Key: your_api_key' \
  --form 'audio=@/path/to/meeting-record.mp3' \
  --form 'language=uz' \
  --form 'has_diarization=true' \
  --form 'is_summary=true'

Javoblar #

200 OK

Queued

{
  "id": 901,
  "has_diarization": true,
  "is_meeting": false,
  "task_id": "66e92db4-95cf-4bb9-acbc-49462039d19f",
  "status": "PENDING",
  "title": "sales-call-13-aprel",
  "audio_url": "/media/audio/273bc5f8-1f91-4573-b3df-3c38c44294d0.mp3"
}

Status kodlari #

200

Task yaratildi.

400

Audio yo'q yoki file juda katta.

401

API key yuborilmagan yoki noto'g'ri.

403

Balans yoki access xatosi.

500

Ichki xato.

v2 history ro'yxati #

GET https://back.aisha.group/api/v2/stt/get/

Async transkriptlarni paginatsiya bilan history ro‘yxati.

Autentifikatsiya: X-Api-Key talab qilinadi.

  • Detail uchun alohida endpoint: GET /api/v2/stt/get/{id}/.

Misollar #

v2 history

curl --request GET \
  --url 'https://back.aisha.group/api/v2/stt/get/?page=1&limit=10' \
  --header 'X-Api-Key: your_api_key'

Javoblar #

200 OK

History

{
  "count": 1,
  "next": null,
  "previous": null,
  "results": [
    {
      "id": 901,
      "title": "sales-call-13-aprel",
      "status": "PENDING",
      "created_at": "2026-05-04T10:39:58.501Z",
      "duration": null,
      "audio_url": "/media/audio/273bc5f8-1f91-4573-b3df-3c38c44294d0.mp3"
    }
  ]
}

Status kodlari #

200

History yoki detail qaytdi.

401

API key yuborilmagan yoki noto'g'ri.

404

Transcript topilmadi.

v2 transcript detail #

GET https://back.aisha.group/api/v2/stt/get/{id}/

Bitta async transkript yozuvining holati va natijasini qaytaradi.

Autentifikatsiya: X-Api-Key talab qilinadi.

  • Status SUCCESS bo'lganda transcript natijasi qaytadi.

Misollar #

v2 detail

curl --request GET \
  --url https://back.aisha.group/api/v2/stt/get/901/ \
  --header 'X-Api-Key: your_api_key'

Javoblar #

200 OK

Completed

{
  "id": 901,
  "title": "sales-call-13-aprel",
  "status": "SUCCESS",
  "created_at": "2026-05-04T10:39:58.501Z",
  "duration": 612.4,
  "transcript": "Uzoq meeting transcript matni...",
  "summary": "Qisqa summary...",
  "diarization": [],
  "audio_url": "/media/audio/273bc5f8-1f91-4573-b3df-3c38c44294d0.mp3"
}

Status kodlari #

200

Detail qaytdi.

401

API key yuborilmagan yoki noto'g'ri.

404

Transcript topilmadi.

Task status polling #

GET https://back.aisha.group/task-status/{task_id}/?instance_id={id}

Async task holatini tekshiradi. instance_id ownership tekshiruv uchun majburiy.

Autentifikatsiya: Bearer token (JWT) talab qilinadi. API key bilan ishlamaydi.

  • Bu endpoint X-Api-Key emas, user session/JWT bilan ishlaydi.

Misollar #

task-status

curl --request GET \
  --url 'https://back.aisha.group/task-status/task-123/?instance_id=944' \
  --header 'Authorization: Bearer your_access_token'

Javoblar #

200 OK

Pending

{
  "task_id": "task-123",
  "status": "PENDING",
  "transcript_status": "PENDING",
  "message": "Task is still processing"
}
200 OK

Success

{
  "task_id": "task-123",
  "status": "SUCCESS",
  "transcript_status": "SUCCESS",
  "result": {
    "transcript": "Hello world"
  }
}

Status kodlari #

200

Task holati qaytdi.

400

instance_id yo'q.

403

Access rad etildi.

500

Task failed yoki unknown state.