API Documentation
Error Handling
Understanding and handling ScrapeGraphAI API errors
Error Format
All API errors follow a simple format:
HTTP Status Codes
400 Bad Request
Indicates that the request was malformed or invalid.
401 Unauthorized
Authentication-related errors.
429 Too Many Requests
Rate limiting errors.
500 Server Error
Internal server errors.
Error Handling Best Practices
Retry Strategy
Our SDKs implement automatic retries for certain errors. For direct API usage, implement your own retry logic.
-
Retryable Errors
- Rate limit exceeded (429)
- Service unavailable (500, 503)
- Network timeouts
-
Non-Retryable Errors
- Invalid parameters (400)
- Authentication errors (401)
- Invalid schemas (400)
Example Error Handling
Support
If you encounter any errors not documented here or need assistance:
Was this page helpful?