# Request log

See each call that your API keys and MCP clients make to Risotto, with its status, duration and errors

The request log lists the calls that your organization's [API keys](https://www.tryrisotto.com/docs/dashboard/settings/developers/api-keys) and MCP clients make to Risotto, newest first. Use it to check that an integration is working, and to find out why a call failed.

Go to **Settings > Developers > Request log**. Only Org Admins and Managers see this page.

*Product example: Settings, Developers, Request log: the path filter, View, and recent requests with their method, path, status, API key, duration and time.*

## What the log records

The log records:

- **Public API requests** - every request to `https://api.tryrisotto.com/v1/` made with a valid API key, whether it succeeds or fails. That includes requests refused for a missing scope (`403`) or for going over the [rate limit](https://www.tryrisotto.com/docs/dashboard/settings/developers/api-keys#rate-limits) (`429`).
- **MCP server requests** - every call to your organization's [MCP server](https://www.tryrisotto.com/docs/integrations/mcp-server), from a client signed in with OAuth or from a headless client that uses an API key. The steps of an OAuth sign-in (`/authorize`, `/token`, `/register` and `/revoke`) are recorded too.

The log doesn't record:

- Requests with a missing, mistyped or revoked API key. Risotto can't tell which organization they're for.
- Visits to the API reference.
- [Webhook](https://www.tryrisotto.com/docs/integrations/webhooks) deliveries, which Risotto sends to your systems rather than receives. See [Delivery logs and testing](https://www.tryrisotto.com/docs/integrations/webhooks#delivery-logs-and-testing).

## Read the log

Each row is one request:

- **Method** - the HTTP method, such as `GET`, `POST`, `PATCH` or `DELETE`.
- **Path** - the path that was called, such as `/v1/tickets/IT-139`. An MCP server request shows your MCP server's path, `/o/<org_id>/mcp`.
- **Status** - the HTTP status code. Codes from `200` to `299` are green, and codes from `400` up are red.
- **API Key** - the name of the key that made the request. Requests from OAuth clients, such as Claude Desktop, show **Unknown**.
- **Duration** - how long Risotto took to answer, in milliseconds.
- **Date** - how long ago the request came in. Hover over it to see the exact date and time.

The footer shows the total number of requests, **Rows per page**, and buttons to move between pages. On a narrow screen, each request shows as a card with its method, path, status, date, error message, request ID, IP address and user agent.

## Find a request

- To find requests to one endpoint, type part of its path in the **Filter by path or method** box, for example `/v1/tickets`. The box matches text in the request's path.
- To sort the log, click **View**, then choose a column in **Sort by**: **Method**, **Status**, **Duration** or **Date**. Turn on **Sort descending** to reverse the order. You can also click a sortable column's header.
- To show or hide columns, click **View**, then click the column names under **Columns**. Click **Reset to default** to show the usual columns again.

## See a request's details

1. **Open a request**

   Click the request's row. Its details open under it.

   *Product example: A denied PATCH request expanded in the request log, its path in outline: request ID, IP address, user agent, error code and error message.*

2. **Read the details**

   The details show:

   - **Request ID** - the same ID that Risotto returned in the response's `X-Request-ID` header. Search your integration's logs for it to match the two sides of a call.
   - **IP Address** - the address the request came from. When the request passed through a proxy, it's the first address in the `X-Forwarded-For` header.
   - **User Agent** - the client's `User-Agent` header.
   - **Error Code** and **Error Message** - for a failed public API request, the `code` and `message` from the error response, for example `authorization_error` and the scopes the endpoint needs.
   - **Query Parameters** - the request's query parameters. For an MCP tool call, the arguments the client passed to the tool.

   A field shows only when the request has a value for it.

3. **Close the details**

   Click the row again. Opening another row also closes the first one.

## Common errors

| Status | What it means                                             | What to do                                                                                                                                                                                                  |
| ------ | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `403`  | The API key doesn't have a scope that the endpoint needs. | Read the **Error Message** for the scopes that would allow the call. [Create a key](https://www.tryrisotto.com/docs/dashboard/settings/developers/api-keys#create-a-key) with them, and revoke the old key. |
| `404`  | The record the path names doesn't exist.                  | Check the ticket key or ID in the path.                                                                                                                                                                     |
| `429`  | The key went over its hourly limit.                       | Slow the integration down, or wait for the time the error message gives. See [Rate limits](https://www.tryrisotto.com/docs/dashboard/settings/developers/api-keys#rate-limits).                             |

A `401` for a bad key never shows in the log. If an integration gets `401` responses and nothing appears here, check that it sends a current key. See [Use a key](https://www.tryrisotto.com/docs/dashboard/settings/developers/api-keys#use-a-key).

Source: https://www.tryrisotto.com/docs/dashboard/settings/developers/request-log
