# Find and inspect a request

import BeforeYouBegin from '_core/components/BeforeYouBegin/BeforeYouBegin';

<BeforeYouBegin />

This guide shows you how to find a specific API call in Request Logs and read what noon received and returned. By the end, you'll have the call's status, error code, and payloads open in front of you.

## Prerequisites

- Developer Portal access to the project that made the call — see the [Developer Portal overview][developer-portal-overview].
- The call was made to a non-public endpoint within the last 14 days — see [what gets logged][developer-portal-request-logs].
- Ideally, the value of the call's `x-request-id` response header. If you don't have it, you can still find the call by time, API user, status, and endpoint in Step 2.

## Step 1 — Open the Request Logs dashboard

1. Sign in to the [noon Developer Portal][developer-portal-app].
2. In the sidebar, go to **Request Logs → Dashboard**.

![Request Logs dashboard with the filter bar, the request list on the left, and a POST request's details on the right][request-logs/dashboard]

**Success check:** The page title reads **Request Logs**, and the list shows your project's most recent requests, newest first.

## Step 2 — Find the request

**If you have the request ID:**

1. Paste the `x-request-id` value into **Search request ID** and press **Enter**.

When you search by request ID, the other filters don't apply — the list shows that one request.

**If you don't have the request ID**, narrow the list with filters. They apply as soon as you change them:

1. **Requested at** — pick **Last hour**, **Last 12 hours**, **Today**, **Last 24 hours**, or **Last 7 days**, or enter your own dates. Logs go back up to 14 days.
2. **API user** — the API user that made the call.
3. **Status** — **Success (2xx)** or **Failure (non-2xx)**.
4. **Method** — **GET** or **POST**.
5. **Endpoint** — pick a marketplace first, then one or more endpoints. Select a service to include all of its endpoints at once.

Use **Previous** and **Next** below the list to page through results, and the clear-filters button next to the date picker to reset everything. Filters are saved in the page URL, so you can bookmark or share a filtered view.

![Endpoint filter open with the noon marketplace selected and all /fbpi endpoints checked][request-logs/endpoint-filter]

**Success check:** The request you're looking for appears in the list — with a request ID search, it's the only row.

**If something goes wrong:**

- **The call you just made isn't there** — calls take a few seconds to appear. Wait, then click **Refresh** at the top right; **Last updated** shows when the list was last loaded.
- **No requests match these filters** — widen the **Requested at** range or clear filters. Also check the call went to a non-public endpoint within the last 14 days.
- **A request ID search returns nothing** — make sure you copied the full value and that the call was made by this project. On rare occasions a call doesn't show up in the dashboard; its log can still be retrieved through a [support case][developer-portal-support-cases] — include the request ID.

## Step 3 — Inspect the request

1. Click the request in the list. Its details open in the panel on the right. The details panel shows, from top to bottom:

- **Summary** — **Request ID**, **Time**, **Duration**, **IP address**, **API user**, **Project code**, **Marketplace**, **Error code** (failed calls only), and **User agent**. Request ID and API user have copy buttons.
- **Query parameters**
- **Request payload** and **Response payload** — formatted JSON, with **Wrap**, **Expand**, and **Copy** buttons.
- **Request headers** and **Response headers**

A successful GET has no response payload or response headers, and a GET never has a request payload — see [what each log contains][developer-portal-request-logs].

**Success check:** The details panel shows the request ID you searched for, along with its status and, if it failed, its error code.

To understand the error code, look it up in [Errors][errors]. If a call was throttled, the rate-limit headers under **Response headers** show how much quota was left and when to retry — see [Rate Limits & Usage][rate-limiting].

## Next steps

- [Errors][errors] — what each error code means
- [Error Handling][error-handling] — how to handle failures in your integration
- [Support Cases][developer-portal-support-cases] — raise a case and include the request ID
- [← Back to the Request Logs overview][developer-portal-request-logs]