Audio transcription

POST /v1/audio/transcriptions

Authentication

Use your NeonAPI API key in Authorization: Bearer YOUR_API_KEY. Keep the key in a trusted application environment.

Availability and compatibility

Check the selected model’s protocol, permissions, price and supported parameters before calling. Unsupported parameters may be rejected. Request examples use placeholders.

Request fields

multipart/form-data

Field	Type	Required	Constraints	Meaning
`file`	`string`	Yes	binary	Input audio file, sent as multipart data.
`model`	`string`	Yes	—	Exact published model ID.
`language`	`string`	No	—	—
`prompt`	`string`	No	—	Instruction or generation prompt.
`response_format`	`string`	No	`json`, `text`, `srt`, `verbose_json`, `vtt`; default: `"json"`	Desired output format where supported.
`temperature`	`number`	No	—	Sampling temperature where supported.
`timestamp_granularities`	`string[]`	No	—	—

Full field definitions, nested objects and referenced schemas are available in the downloadable specification.

Request example

export NEON_API_KEY="YOUR_API_KEY"
curl https://neon-api.com/v1/audio/transcriptions \
  -H "Authorization: Bearer $NEON_API_KEY" \
  -F "model=YOUR_MODEL_ID" \
  -F "file=@sample.wav"

Responses

Fields vary by model and protocol. The schema below describes the documented successful response; streams use protocol-specific events.

Status	Meaning
200	Successful response

Response schema

Field	Type	Required	Constraints	Meaning
`text`	`string`	No	—	—

Download the user API OpenAPI specification

See errors and streaming & tasks.