Errors And Limits
Early access. Tell us what you're building and we'll set you up. Contact us
Lempile uses queue-first behavior so temporary runner pressure does not immediately fail fresh searches. Most new searches return 202 Accepted and are resolved later through polling.
Common Errors#
| HTTP | Code | Meaning |
|---|---|---|
400 |
invalid_search_parameters |
The request has invalid or conflicting search parameters. |
401 |
unauthorized |
The API key is missing or invalid. |
402 |
subscription_required |
The workspace has no active trial or subscription. Start the free trial or add a card in the dashboard (Subscription), and its keys work again right away. |
403 |
forbidden |
The API key does not include the required search scope. |
429 |
workspace_search_queue_full |
The workspace has too many queued or running Google searches. |
503 |
service_unavailable |
Platform configuration or authentication failed before queueing was possible. |
Google Blocks And CAPTCHA#
If Google returns a block, consent, or CAPTCHA page, Lempile records safe diagnostics in the final JSON response.
Diagnostics can include:
- CAPTCHA task type
- provider status
- solver request id
- whether a token was applied
- whether Google still returned a block page
Diagnostics never include raw proxy credentials, cookies, CAPTCHA tokens, API keys, or passwords.
Queue Limits#
Production runs conservatively:
- One active Google browser job per runner by default.
- Burst traffic queues instead of launching unlimited browser sessions.
- A single workspace can be rate-limited to protect the shared runner fleet.
When higher throughput is needed, add more runner capacity rather than increasing browser concurrency on one machine.
Was this page helpful?