Overview
Parsefy implements rate limiting to ensure fair usage and API stability. There are two types of limits:- Request Rate Limits: How many requests you can make per second
- Credit Limits: How many document pages you can process (playground only)
Rate Limits by Endpoint
/v1/extract (Authenticated)
/v1/playground (Unauthenticated)
Credits reset at midnight UTC each day.
Understanding Credits
Credits are Parsefy’s unit for measuring document processing:- PDF: Approximately 100KB per page
- DOCX: Approximately 50KB per page
Example Credit Usage
Rate Limit Headers
When you hit a rate limit, the API returns HTTP status429 with details:
Handling Rate Limits
Automatic Retry (SDKs)
Both official SDKs implement automatic retry with exponential backoff:- Python
- JavaScript
Manual Retry (cURL/Custom)
Implement exponential backoff in your own code:Best Practices
Batch Processing
When processing multiple documents, add delays between requests to stay under rate limits.
Queue System
For high-volume processing, implement a queue that respects rate limits.
Error Handling
Always handle 429 errors gracefully with retry logic.
Monitor Usage
Track your credit usage in the dashboard to avoid unexpected limits.
Example: Rate-Limited Batch Processing
File Size Limits
In addition to rate limits, there are file size restrictions:
Files exceeding 10 MB will receive a
400 Bad Request error:
Increasing Limits
Need higher rate limits for your use case? Contact us:- Email: support@parsefy.org
- Enterprise plans: Custom rate limits and dedicated infrastructure available
Enterprise customers can get dedicated API endpoints with higher throughput and SLA guarantees.
