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. Each entry includes:
| Field | Description |
|---|---|
| Timestamp | When the request was made |
| Method | HTTP method sent to the target (GET, POST, etc.) |
| Route | Which FourA endpoint was used (single, proxy, or browser) |
| Domain | Target domain extracted from the request URL |
| Status | HTTP status code returned by the target |
| App Status | Application-level status returned in the response body |
| Outcome | Request classification (success, client_error, rate_limit, etc.) |
| Duration | Total response time in milliseconds |
| Bytes In | Request payload size |
| Bytes Out | Response payload size |
| Key Name | Which API key was used |
| Client IP | IP address that made the request |
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 dialog with the full request and response payload preview. The dialog shows:
- Meta grid: timestamp, key, HTTP status, app status, outcome, duration, and the request's
X-Foura-Request-Id. - Request: pretty-printed JSON of the exact body sent, with a Copy button.
- Response: meta strip plus the body preview, with truncated and binary badges where they apply.
Payloads are kept for 24 hours, capped at the last 200 per API key. Rows older than that show the row only, no detail dialog.
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) |
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 the API Endpoints reference for details.
Related
- Metrics and Analytics: Aggregated performance data over longer periods
- Playground: Replay requests from Activity
- API Endpoints: Request and response shapes, including the request ID header
- Troubleshooting: Common problems and solutions