Request Logs
The Logs page gives you a searchable, per-request activity feed for your account: every API call's lifecycle events, errors, durations, and unit usage. Use it to debug failed requests, trace a specific request ID, or audit what an API key has been doing.
Open it from the dashboard sidebar under Tools → Logs, or go directly to browserless.io/account/logs. The sidebar entry appears on Cloud Unit and Dedicated plans.
Availability and lookback
Request logs are available on Cloud Unit and Dedicated plans. How far back you can search depends on your plan:
| Plan | Maximum lookback |
|---|---|
| Free | 8 hours |
| Prototyping | 24 hours |
| Starter | 3 days |
| Scale | 7 days |
| Dedicated | 7 days |
Custom and legacy cloud plans can search back up to 7 days.
What gets logged
Each request produces lifecycle events as it runs. You can filter by these event names:
request.completed/request.failed: the outcome of an API requestnavigation.started/navigation.completed: page navigations performed during the requestbql.parse.failed,bql.validation.failed,bql.operation.failed,bql.execution.failed,bql.transport.failed: BrowserQL-specific failures, from a query that failed to parse or validate down to an individual mutation that errored
Every event carries a level (INFO, WARN, or ERROR) and, where applicable, an outcome.
Reading the log table
| Column | What it shows |
|---|---|
| Timestamp | When the event occurred, shown in your local time |
| Event | The event name, such as request.failed |
| Level | INFO, WARN, or ERROR |
| Outcome | The result recorded for the event |
| Details | The error message, reason, or category, plus the HTTP status when one was recorded |
| Endpoint / region | Which API endpoint handled the request and the region it ran in |
| Target URL | The page the request was operating on |
| Duration | How long the request took |
| Units | Total units the request consumed; hover to see the breakdown across time, proxy, captcha, and agent units |
| Request ID | The unique ID for the request, with a copy button |
Columns are resizable: drag the divider next to a column header, or focus it and use the arrow keys.
Filtering logs
Set any combination of filters and click Apply:
- Time range: last hour, 8 hours, 24 hours, 3 days, or 7 days, capped at your plan's maximum lookback
- Request ID: find every event from a single request
- Target URL: match requests by the page they operated on
- Endpoint: match a specific API endpoint
- Outcome: match the recorded outcome
- Events: one or more event names from the list above
- Levels: one or more of
INFO,WARN,ERROR - API key: scope results to one of your API keys, including revoked keys
Results are paginated 50 entries at a time; use Previous and Next to move through pages.
Tracing a failed request
Error responses from Browserless APIs include the request's ID as a suffix on the error message:
Timed out waiting for selector "h1" (requestId: f3a9c2d81b7e4a06)
Paste that ID into the Request ID filter to see everything the request did before it failed: navigations, the failing operation, its duration, and the units it consumed. This is also the ID to include when contacting support, so they can find the matching server-side logs.