When a PDFCrowd API client exceeds its plan’s request-rate allowance, PDFCrowd returns HTTP 429. When too many conversions are running simultaneously, it returns HTTP 430 instead. Slow the rate of new submissions for 429; reduce parallel work and let active conversions finish for 430. The exact limits depend on your license.
429 and 430 mean different things
PDFCrowd distinguishes requests submitted over time from conversions being processed at the same time. The HTTP status and, when present, PDFCrowd’s reason code help identify which limit you reached.
As an Amazon Associate I earn from qualifying purchases.
| Response | What exceeded the limit | Immediate response |
|---|---|---|
| HTTP 429; reason code 120 | Request rate: conversion submissions over time. PDFCrowd’s FAQ describes the allowance in terms of requests within a minute. | Pause or slow new submissions, then reduce the request rate. |
| HTTP 430; reason code 121 | Concurrency: too many conversions running simultaneously. | Let active conversions finish and lower the number running at once. |
PDFCrowd labels these errors “Request rate limit reached” and “Concurrent request limit reached.” Its API documentation notes that both allowances depend on the license. PDFCrowd’s status-code reference lists the status meanings and reason codes.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhat to do when you receive HTTP 429
- Stop adding pressure. Pause or slow new conversion submissions rather than immediately repeating the failed request.
- Reduce the request rate. Space out submissions so your client sends fewer conversions over time.
- Check the allowance for your license. PDFCrowd defines its rate limit as the maximum number of conversions allowed per minute, but the exact numeric allowance depends on the account’s license. Review your current account or plan terms rather than assuming a universal threshold.
- Consider a plan change only if the problem persists. If rate errors continue after you have controlled the sending rate, compare your workload with the allowance for your license.
The FAQ describes a 429 when request frequency within a minute surpasses the plan allowance. The documentation does not establish a universal block duration or a precise reset time for every account. PDFCrowd’s rate-limit FAQ covers the distinction and guidance for recurring limit pressure.
#1 Best Overall
What to do when you receive HTTP 430
- Stop increasing parallel work. Do not start more conversions while the client already has too many in progress.
- Let active conversions finish. This is a concurrency limit, not simply a high total number of requests over time.
- Set a lower concurrency ceiling. Keep fewer conversion jobs active at once, then submit additional work as existing jobs complete.
- Review your license if the workload still needs more parallelism. PDFCrowd’s concurrency allowance varies by license.
PDFCrowd defines concurrency as the number of conversions that can run simultaneously. Its pages do not provide one numeric concurrency threshold that applies to all plans. See PDFCrowd’s plan-parameter definitions for how it describes rate and concurrency.
Capture the response details before changing your client
When a limit error recurs or its cause is unclear, record the status, response body, relevant headers, and job ID. PDFCrowd identifies x-pdfcrowd-reason-code as the reason-code header and x-pdfcrowd-job-id as an identifier useful for finding a conversion in logs or support requests. Reason code 120 points to the request-rate limit; 121 points to concurrency.
Rank #2
- LIGHTWEIGHT AND FOLDABLE STRUCTURE: Foldable design (30x6x8cm) and lightweight (1000g) make it portable for travel or home use. Compact shape fits perfectly on your workbench without taking up much space
- SIMPLE CONNECTION: Works with USB connection without the need for additional programs for quick installation. Simple controls make it easy to operate both beginners and regular users with regular size papers
- QUICK DOCUMENT PROCESSING: Automatically scan suggestions one page per second, greatly increase productivity. Ideal for workplaces, schools, legal/financial areas where large capacity is required
- TEXT CONVERSION TECHNOLOGY: Smart OCR function works in over 200 languages, changes scanned files to editable text for easy storage and editing Seamless digital conversion of paper documents improves workflow
- EXCELLENT IMAGEING: Equipped with a 16MP clear camera, this portable document scanner produces crisp, accurate images of documents and keeps important content intact. Perfect for striking scans of contracts, receipts and books
The HTTP API can return structured error details by appending ?errfmt=json to the endpoint; otherwise, errors are plain text by default. Consult PDFCrowd’s HTTP API documentation for response diagnostics and retry guidance.
Retry carefully; do not treat every error as a rate limit
For temporary failures, PDFCrowd recommends a bounded number of retries with increasing delays. Apply that cautiously to limit responses: a retry sent immediately at the same rate or concurrency can reproduce the problem. First reduce the request rate for 429 or the number of simultaneous jobs for 430.
- Correct non-temporary errors first. PDFCrowd advises fixing invalid input, authentication, or account problems before retrying those requests.
- Distinguish HTTP 503 from 429. The API guide describes 503 as a temporary network issue; 429 specifically indicates a request-rate limit.
- Log enough to diagnose repeats. Keep the status, response body, reason-code header, job ID when available, and useful debug logs.
How to tell whether you need a plan change
First determine whether the pressure is on request rate or concurrency. A client that sends requests too quickly needs pacing; one that starts too many jobs at once needs a concurrency cap. If either limit is still reached consistently after adjusting the client, compare that workload with the current license allowance and consider whether a different plan is appropriate. PDFCrowd’s published materials establish that limits vary by license but do not state numeric allowances for each plan in the pages cited here.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your broader workflow is capturing website pages as images or PDFs rather than converting documents through PDFCrowd, ScreenshotNeo is a website screenshot API and MCP server. It is an alternative to try first for website screenshots: cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; and AI agents can use its MCP server to take screenshots.
One GET request returns an image or PDF. See the ScreenshotNeo API documentation for options and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo includes 1,000 screenshots a month free with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo to get started.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
