Skip to main content
A 429 response can mean several different things. Read its code before deciding whether to wait, stop a browser, or check your account quota.

Requests per minute and per hour

Profile API calls are subject to minute and hour limits. Responses report the allowance and remaining requests:
These numbers are examples; read the headers for your account. Either window can block a request. Waiting one minute is not enough when the hour window is exhausted. Use bounded backoff with jitter and reduce the request rate after rate_limits_reached. Avoid frequent polling of account or session endpoints when an application record can answer the same question.

Parallel browsers

Running browsers count against the slot limit even if the worker that started them has crashed. GET /users/browser-limits reports the current count and, on capped accounts, the available slots; see concurrency for the response and how to use it. Availability can change immediately, so your application must still handle a rejected start.

Traffic

Shared and premium proxy traffic have separate quota endpoints:
Quota availability and response fields depend on your plan. In particular, premium_quota_not_applicable means the plan has no premium quota to report. Using another tier requires that tier to be enabled for your account. A different proxy may also change the site’s behavior or invalidate a login tied to an IP. Choose it deliberately. See proxy selection. Reduce unnecessary downloads with request blocking or shared cache, and measure the effect on completed jobs.

Stored objects

Deleting a profile also deletes its saved state. Export anything you need before deleting it.

Check your plan

Use the dashboard and account endpoints for current allowances. See errors for response codes and troubleshooting for failed jobs.