Audio transcription
Behavior
File formats and translation target depend on upstream.
Endpoint and authentication
POST /v1/audio/transcriptionsUse an XHub API key: Authorization: Bearer . Do not use upstream provider credentials as gateway keys.
Use the gateway root Base URL shown in the playground, without appending /v1; send requests to the full endpoint path above.
Request example
curl "$XHUB_BASE_URL/v1/audio/transcriptions" \
-H "Authorization: Bearer $XHUB_API_KEY" \
-F "model=YOUR_MODEL_NAME" -F "file=@sample.wav"Request parameters
| Field | Type | Description |
|---|---|---|
| model | string · required | Public model name; deployment must support this protocol. |
| file | file · required | Multipart audio upload. |
| response_format / language | string | Supported response format; source language for transcription. |
Success response
{
"text": "Hello, welcome to XHub."
}| Field | Type |
|---|---|
| text | string |
Errors and troubleshooting
| HTTP | Meaning |
|---|---|
| 400 | Invalid request. Check JSON, parameters and query. |
| 401 | Missing or invalid XHub credential. |
| 403 | Permission denied. Check model scope or policy. |
| 429 | Limit exceeded. Inspect response details and Retry-After. |