NeonAPI Docs
API reference

Audio translation

Endpoints, request fields and response schemas for calling NeonAPI.

POST /v1/audio/translations

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

FieldTypeRequiredConstraintsMeaning
filestringYesbinaryInput audio file, sent as multipart data.
modelstringYes—Exact published model ID.
promptstringNo—Instruction or generation prompt.
response_formatstringNo—Desired output format where supported.
temperaturenumberNo—Sampling temperature where supported.

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/translations \
  -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.

StatusMeaning
200Successful response

Response schema

FieldTypeRequiredConstraintsMeaning
textstringNo——

Download the user API OpenAPI specification

See errors and streaming & tasks.