Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.spidra.io/llms.txt

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

Spidra returns consistent error responses using standard HTTP status codes and descriptive messages. If something goes wrong with your request—like invalid input, missing authentication, or rate limits—you’ll receive a clear JSON error object.

​
Error Response Format

{
	"status": "error",
	"message": "Detailed error explanation"
}

​
Common Error Codes

Status CodeDescription
400 Bad RequestThe request was malformed or missing required parameters.
401 UnauthorizedAuthentication failed. Check your API key.
403 ForbiddenYou do not have permission to access this resource.
404 Not FoundThe requested resource does not exist.
429 Too Many RequestsYou have exceeded a rate limit. See the code field for which one.
503 Service UnavailableThe service is temporarily at capacity. Retry after the retry_after value (seconds).
500 Internal Server ErrorAn unexpected error occurred on the server.

​
Error Codes

Some errors include a code field with a machine-readable identifier:
CodeStatusMeaning
TOO_MANY_PENDING_JOBS429You have too many jobs currently queued. Wait for some to complete before submitting more.
SERVICE_BUSY503The server queue is at capacity across all users. Retry after retry_after seconds.
PAYMENT_OVERDUE402Your payment is overdue. Update your payment method to continue.
{
  "status": "error",
  "message": "The scraping service is currently at capacity. Please retry in a few minutes.",
  "code": "SERVICE_BUSY",
  "retry_after": 60
}