Skip to main content
Every AdsCrawl plan comes with a credit allowance and a set of limits that govern how many requests you can make, how many browser sessions you can run simultaneously, and how many Cloud Browser profiles you can keep saved. Understanding these boundaries helps you design reliable automations that handle errors gracefully rather than hitting unexpected walls in production.

​
Credit Consumption

Credits are the billing unit for every operation on AdsCrawl. The table below shows how each API type consumes them.
Credits are non-refundable once consumed. If a browser task request fails during execution — after the credit has already been deducted — the credit is not returned. Validate your inputs before sending requests to avoid unnecessary credit loss.
Cloud Browser billing is per started minute, rounded up. A browser that runs for 90 seconds consumes 2 credits. Repeated stop notifications do not trigger duplicate charges — billing ends at the first confirmed stop.

​
Rate Limits

AdsCrawl enforces per-key rate limits to protect service stability. When you exceed a rate limit, the API returns HTTP 429. Back off and retry after a delay.
Implement exponential backoff when you receive a 429 response. Start with a 1-second delay and double it on each retry, up to a reasonable maximum (for example, 30 seconds), before giving up.

​
CDP Session Rate Limits

Remote CDP sessions have a per-API-key concurrency limit. Exceeding it returns:
with HTTP status 429 and the code SESSIONS_PER_API_KEY_LIMIT_REACHED. Delete an existing session before creating a new one, or distribute load across multiple API keys if your plan allows.

​
Concurrency Limits

​
Cloud Browser Concurrency

Each user account has a runningLimit — the maximum number of Cloud Browser sessions (in starting, running, or stopping state) that can be active at the same time. The default is 1. You can inspect your current usage at any time via GET /cloud-browsers:
  • limit — your plan’s saved Cloud Browser profile allowance
  • runningLimit — maximum simultaneous running sessions for your account
  • runningCount — sessions currently in starting, running, or stopping state, across all profiles, pages, and API keys
runningCount includes sessions across all your API keys and dashboard activity. A session in stopping state still occupies a running slot until it reaches stopped.
When you try to start a Cloud Browser and the running allowance is full, the API returns 409 CLOUD_BROWSER_CONCURRENCY_LIMIT:
Lowering your runningLimit does not stop existing sessions. It only prevents new starts until running sessions free up capacity. Stop a running browser before attempting a new start when you are at your limit.

​
Error Codes Reference

The following error codes indicate billing or capacity problems. Use the HTTP status code and the stable code field for error handling in your application — do not rely on the human-readable error message, which may change.

​
Request Size and Parameter Limits

The following hard limits apply to all API requests. Requests that exceed these bounds are rejected with HTTP 400 before any credit is consumed.