Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.urltodata.ai/llms.txt

Use this file to discover all available pages before exploring further.

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"
}

​
HTTP status codes

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

​
Common errors

​
Missing API key

curl "https://api.urltodata.ai/v1/youtube/video?id=dQw4w9WgXcQ"
401
{
  "error": "unauthorized",
  "message": "Missing or invalid API key"
}

​
Missing required parameter

curl -H "Authorization: Bearer your-api-key" \
  "https://api.urltodata.ai/v1/youtube/video"
400
{
  "error": "invalid_request",
  "message": "Missing required parameter: id"
}

​
Insufficient credits

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

​
Resource not found

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

​
Rate limited

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

​
Rate limiting

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