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

# Debugging Session in Developer Portal

<BeforeYouBegin />

A **Debugging Session** captures the API calls made by a specific API user against a specific service, for a limited window, and lets you inspect each one — headers, body, and status code — without needing noon support to pull logs for you.

## Step 1 — Start a session

Go to **Debugging Session** and click **New Debug Session**. Fill in:

- **Session Name** — anything that helps you identify it later (e.g. "Order Processing Debug").
- **Service** — the API service whose calls you want to capture.
- **API User** — the API user (service account) making the calls you want to capture.

All three are required — **Create** stays disabled until they're filled in.

![New Debugging Session modal with Session Name, Service, and API User filled in][debugging-session/new-session-modal]

**Success check:** The session appears at the top of the Debugging Sessions list, tagged **Active**.

![Debugging Sessions list showing an Active session with a countdown, and an Ended session][debugging-session/sessions-list]

## Step 2 — Make the API calls you want to debug

While a session is active, calls made by that API user to that service are logged automatically — call your integration as you normally would (or ask whoever's testing it to). Nothing needs to change in your request; the portal captures it on noon's side.

A session stops capturing when its time window ends — its tag flips to **Inactive** and the countdown on its card shows **Ended** — or earlier if it hits its request limit, shown as **Requests limit exceeded** on the card. Either way, the calls already captured stay available to inspect.

## Step 3 — Inspect the captured calls

Click the session (or **View Details** from the list) to open it. You'll see the session's summary — name, status, service, API user, and time remaining — followed by a table of every call captured, with its endpoint, method, status code, and time sent.

Click a row to expand it and see the full **Request** and **Response** side by side. Each has a **Headers** / **Body** toggle — Body is shown as formatted, collapsible JSON.

![Session details page with a row expanded, showing Request and Response bodies][debugging-session/session-detail-expanded]

**If something goes wrong:**
- No sessions yet — click **New Debug Session** to start your first one.
- Session details load empty right after creation? Give it a moment: nothing is captured until a call is actually made after the session starts.

:::warning TODO
Clicking **View Details** from the sessions list can open a broken link (a 404) if it opens in a new tab — the link target seems to be missing part of the path. Clicking the session itself, or the row's title, navigates correctly. Worth confirming with the team; doesn't block using the feature.
:::

## Finding a session again

The Debugging Sessions list has a search box (search by name, press **Enter**), and **Service** / **API User** dropdown filters — filters are reflected in the URL, so you can bookmark or share a filtered view. Use **Clear Filters** to reset.

## Starting a new session with the same setup

Click **Clone** on any session in the list to immediately start a new session with the same name, service, and API user — useful for a fresh capture window without re-filling the form.

## Next steps

- [← Back to the Developer Portal overview][developer-portal-overview]