Docs › Dashboard › Activity Log

Activity Log

The Activity Log shows your most recent API requests in real time. Use it to debug individual requests, check response codes, and verify that your integration is working.

What You'll See

The log displays requests made within the last hour, with the most recent at the top. Nine columns carry the whole row:

Column What it shows
Time When the request was made
Key Which API key was used
Request The call itself: a colored product dot (single, proxy, or browser), the HTTP method, and the target domain. Sorts by domain.
Status Two values in one cell, separated by a slash: the HTTP status of your call to FourA, then the status the target returned. A dash means the target never answered.
Outcome Request classification (Success, Client Error, Rate Limited, and so on)
Duration Total response time in milliseconds
Bytes Transfer both ways in one cell: down arrow for the request payload, up arrow for the response
Credits Credits spent on the call (see Response Headers)
Client IP The address that made the request

Click any column header to sort the table by that column; direction cycles descending, ascending, then off. Ctrl or Cmd click resets to the default (newest first).

Filtering

Three controls narrow the log.

By API Key

Use the API key dropdown to show requests from one key. Only keys within your access scope appear in the dropdown.

By Product

Filter to one endpoint with the single / proxy / browser selector. Useful when you want to debug browser-only failures separately from single requests.

By Limit

The activity log defaults to 50 entries. Use the limit selector to change how many entries are shown:

Limit Notes
10 Quick scan
50 Default
100 Extended view
200 Maximum

All entries are from the last hour. For historical data, use the Metrics section, which aggregates data over days and weeks.

Opening a Request

Click any row to open a detail panel with the full request and response payload preview. The panel opens on a meta grid built from the row itself, so it stays useful even after the stored payload has aged out: timestamp, key, HTTP status, app status, outcome, duration, credits, proxy, and the request's X-FourA-Request-Id.

Below the grid, one pane shows at a time, selected by tab:

Tab What it shows
Request Pretty-printed JSON of the exact body sent
Response headers The headers the target returned, with a count on the tab
Response body The stored body preview, with truncated and binary badges where they apply
Other fields Anything else the engine returned beyond status, timings, proxy, and headers. Hidden when there's nothing extra.

A Copy button copies whichever pane is open. Payloads are kept for 24 hours, capped at the last 200 per API key. Rows older than that show the row only, without a payload.

Body Pane Messages

The body pane uses different placeholder text depending on what happened:

Message What it means
(no body — the request failed: <error>) The request errored before the target returned a body
(no body captured for this request) Payload aged out or wasn't stored
(empty body — the server returned 0 bytes) The target returned a real empty response

Open in Playground

The detail dialog has an Open in Playground button. Click it to load both the archived request and the archived response into the Playground form. From there you can tweak parameters and replay against the live API, or just inspect what came back without re-running the request.

The button is disabled for non-replayable payloads (oversized request stubs and non-API routes), with a hint explaining why.

Using the Request ID

Every API response carries an X-Foura-Request-Id header. Log it on your side, and you can paste it into a support ticket to point at the exact request in the Activity Log. The ID is the same one used in this dialog and matches the X-Foura-Request-Id returned by the API. See Response Headers for details.

Last updated: August 12, 2026
← Metrics Usage & Limits →