Errors

urltodata uses standard HTTP status codes and returns errors in a consistent JSON format.

Error format

{
  "error": "Short error type",
  "message": "Human-readable description of what went wrong"
}

Code	Meaning
`200`	Success
`202`	Accepted — async job created, poll for results
`400`	Bad request — missing or invalid parameters
`401`	Unauthorized — missing or invalid Bearer token
`402`	Payment required — insufficient credits
`404`	Not found — resource doesn’t exist
`409`	Conflict — resource already exists (e.g. duplicate email)
`429`	Rate limited — too many requests
`500`	Internal server error

curl "https://api.urltodata.ai/v1/youtube/video?id=dQw4w9WgXcQ"

401

{
  "error": "unauthorized",
  "message": "Missing or invalid API key"
}

curl -H "Authorization: Bearer your-api-key" \
  "https://api.urltodata.ai/v1/youtube/video"

400

{
  "error": "invalid_request",
  "message": "Missing required parameter: id"
}

402

{
  "error": "insufficient_credits",
  "message": "Not enough credits. Purchase more at /v1/credits/packages"
}

404

{
  "error": "not_found",
  "message": "Video not found or unavailable"
}

429

{
  "error": "rate_limited",
  "message": "Too many requests. Try again later."
}

Requests are rate limited per API key. If you receive a 429 response, back off and retry. Use exponential backoff starting at 1 second.