Retrieve an audio file that was previously uploaded to CEQUENS Voice. Use this endpoint to download or verify audio files stored in your account.
Authentication
Bearer token in the Authorization header. Default shown in docs: "Bearer Your_Token_From_Login_Step". Files are scoped to the account that uploaded them. The account is taken from the token.
Method: GET
URL: https://apis.cequens.com/v1/voice/file/{fileId}
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
fileId | string | Yes | The recordId returned by the "Upload an Audio File" endpoint, for example 2f8c1c0e-9f2f-4a3a-9d1a-0b7f7b0d8c31.wav. |
Request Headers
| Header | Type | Required | Description |
|---|---|---|---|
Authorization | string | Yes | Bearer token from the sign-in step |
Response
Status Code: 200 OK
The response body contains the audio file binary data.
Response Headers
| Header | Description |
|---|---|
Content-Type | audio/wav - the stored media type of the file. |
Content-Length | 264044 - size of the file in bytes. |
Examples
Example Request
curl -X GET "https://apis.cequens.com/v1/voice/file/file_abc123def456" \
-H "Authorization: Bearer YOUR_API_KEY"NOTE: A successful response is binary audio and a failed one is JSON, so callers should branch on the HTTP status code (or on the Content-Type response header) before parsing the body.
cURL Sample
curl --location --request GET 'https://apis.cequens.com/v1/voice/file/2f8c1c0e-9f2f-4a3a-9d1a-0b7f7b0d8c31.wav' \
--header 'Authorization: Bearer XXXXXXXXX' \
--output welcome.wavError Handling
Error Responses
| Status Code | Error | Description |
|---|---|---|
400 | Bad Request | invalid fileId - the id is empty, or contains characters that are not allowed. |
401 | Unauthorized | There is no token provided |
404 | Not Found | file not found - no such file under this account, either because it was never uploaded or because it belongs to a different account. |
502 | Bad Gateway | failed to fetch file - temporary storage failure, retry. |
Error Response Format
All error responses are shaped as follows:
{
"reqId": "...",
"message": "..."
}