# Request Logs

### Logs table

The main table lists API requests with the following columns:

<table><thead><tr><th width="184">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Method</strong></td><td>HTTP method (GET, POST, PATCH, DELETE) with colour-coded badge</td></tr><tr><td><strong>Path</strong></td><td>The API endpoint that was called</td></tr><tr><td><strong>Status</strong></td><td>HTTP response code (green for 2xx, red for 4xx/5xx)</td></tr><tr><td><strong>Duration</strong></td><td>How long the request took to process (in milliseconds)</td></tr><tr><td><strong>API Key</strong></td><td>The key prefix used for the request</td></tr><tr><td><strong>Timestamp</strong></td><td>When the request was made</td></tr></tbody></table>

### Filtering

Use the filter controls at the top of the table to narrow results:

* **Method filter** — show only GET, POST, PATCH, or DELETE requests
* **Status filter** — filter by response status code (e.g. show only 422 errors)

Filters apply immediately and reset the pagination to page 1.

### Viewing request details

Click any row to open the **Log Details Modal**. This shows the full request and response data:

* **Request body** — the JSON payload sent to the API (for POST/PATCH requests)
* **Response body** — the JSON payload returned by the API
* **Headers** — request headers including the API key prefix
* **IP address** — the IP the request originated from
* **Duration** — exact processing time in milliseconds

This is the fastest way to debug a specific API call. If a transfer creation is failing, find the POST request in the logs, open it, and inspect the error response to see exactly what went wrong.

### Pagination

Logs are paginated with 15 results per page. The pagination bar at the bottom shows:

* Which results you are viewing (e.g. "Showing 1-15 of 1,247")
* Previous and next page controls

### Common debugging workflows

#### *"My transfer creation is returning an error"*

1. Open Request Logs
2. Filter by **Method: POST** and **Status: 4xx** (or the specific error code)
3. Find the failed request to `/api/v1/off-ramp` or `/api/v1/on-ramp`
4. Click to open details and inspect the error response

#### *"My webhook is not being received"*

1. Check Request Logs for the original API call that should trigger the webhook
2. Then check the Webhook Logs to see if the delivery was attempted
3. If the delivery shows a 500 status, the issue is on your server side

#### *"I want to see all requests from a specific key"*

1. Look at the **API Key** column to identify which key prefix was used
2. Cross-reference with your API Keys page to identify the key by name

{% hint style="info" %}
Request logs are retained for 30 days. If you need historical data beyond that, export your transaction data from the Transactions page.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zynta.com/dashboard/request-logs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.