AudioLasso Docs

Errors and logs

Understand API error responses and queue log messages.

AudioLasso API errors use a structured JSON shape.

{
  "error": {
    "code": "INVALID_AUDIO_URL",
    "message": "input.audio_url must be a public HTTPS URL.",
    "param": "input.audio_url",
    "request_id": "req_01jabc"
  }
}

HTTP status codes

StatusMeaning
400Invalid request body or parameter
401Missing or invalid API key
402Not enough credits
403API key is missing a required scope
404Request or file was not found
409Request is not ready for the attempted operation
410Temporary file or result expired
413File is too large
500Internal server error
502Upstream model provider failed

Queue logs

Use ?logs=true on status or stream endpoints to include short progress messages.

curl "https://audiolasso.dev/v1/queue/requests/req_01jabc/status?logs=true" \
  -H "Authorization: Bearer $AUDIOLASSO_API_KEY"

Logs are meant for humans and agents. Treat status as the source of truth for program logic.

{
  "logs": [
    {
      "timestamp": "2026-04-25T08:00:00.000Z",
      "message": "Started audio separation"
    }
  ]
}
  • Branch on HTTP status and error.code.
  • Show error.message to developers.
  • Retry 502 and network errors with backoff.
  • Do not retry 400, 401, 402, or 403 without changing the request or key.

Webhooks

Receive terminal audio separation events when a queued request completes or fails.

CLI

AudioLasso CLI status and local development commands.

On this page

HTTP status codes
Queue logs
Recommended client behavior