Error Codes

DataBlue uses standard HTTP status codes. All error responses include a JSON body with error and message fields.

Code Name Description
400 Bad Request Invalid request body, missing required fields, or validation error (e.g. URL format, parameter constraints).
401 Unauthorized Missing, invalid, or expired authentication token. Re-authenticate or generate a new API key.
403 Forbidden Authenticated but insufficient permissions. Your plan may not include access to this endpoint.
404 Not Found The requested resource (job ID, monitor, schedule) does not exist.
429 Rate Limited You have exceeded your plan's rate limit. Wait for the reset window and retry. See the retry_after field.
500 Internal Error Server-side error. This may indicate a bug or infrastructure issue. Retry with exponential backoff.
503 Service Unavailable Endpoint is temporarily disabled or under maintenance. Data APIs may return this if a scraper is being updated.

Error Response Format

// 400 Bad Request
{
  "success": false,
  "error": "Bad Request",
  "message": "Field 'url' is required"
}

// 401 Unauthorized
{
  "success": false,
  "error": "Unauthorized",
  "message": "Invalid or expired authentication token"
}

// 429 Rate Limited
{
  "success": false,
  "error": "Rate limit exceeded",
  "message": "You have exceeded the rate limit of 60 requests per minute",
  "retry_after": 23
}

// 500 Internal Error
{
  "success": false,
  "error": "Internal Server Error",
  "message": "An unexpected error occurred. Request ID: req_a1b2c3d4"
}

Scrape-specific error codes: Scrape responses may include an error_code field with values like BLOCKED_BY_WAF, CAPTCHA_REQUIRED, TIMEOUT, JS_REQUIRED, or NETWORK_ERROR for more granular error classification.