> ## Documentation Index
> Fetch the complete documentation index at: https://interceptor-docs.requestly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Learn when to use Sessions, how to record bug reports or API sessions, and how to share debugging context with your team.

Sessions help you capture the evidence around a problem so it is easier to debug, replay, share, or turn into a mock later.

## When To Use Sessions

Use Sessions when you want to:

* record browser activity, console logs, network logs, and environment context for bug reports
* capture API traffic from the Desktop App for replay, analysis, or bulk mocking
* import HAR files for investigation
* share reproducible debugging context with teammates

You may still encounter older references to **Session Book** in the product or legacy links. In the docs, this workflow is documented under **Sessions**.

## Choose The Right Session Workflow

> [tab] Record Bug Reports
>
> Use this path when you want browser-focused debugging context such as screen activity, console logs, network logs, and environment details.
>
> > [card] [Record Bug Reports](https://interceptor-docs.requestly.com/sessions/record-bug-reports.md)
> >
> > Capture reproducible bug reports directly from the browser workflow.

> [tab] Capture API Sessions
>
> Use this path when you want to record API traffic from the Desktop App, inspect requests and responses, or create mocks from captured traffic.
>
> > [card] [Capture API Sessions](https://interceptor-docs.requestly.com/sessions/record-api-sessions.md)
> >
> > Record and analyze network traffic from interception workflows.

## First Success Path

**1. Pick Bug Reports Or API Sessions**

Start with browser bug reports if you need user-facing reproduction context. Start with API sessions if the problem is primarily network behavior.

**2. Capture The Session**

Use [Record Bug Reports](https://interceptor-docs.requestly.com/sessions/record-bug-reports.md) or [Record API Sessions](https://interceptor-docs.requestly.com/sessions/record-api-sessions.md) depending on the workflow.

**3. Share Or Reuse The Output**

Share the session, import/export HAR files, or use captured traffic to support mocking and debugging flows.

## Explore Sessions

> [card] [Record Bug Reports](https://interceptor-docs.requestly.com/sessions/record-bug-reports.md)
>
> Capture browser activity and rich debugging context for issue reproduction.

> [card] [Capture API Sessions](https://interceptor-docs.requestly.com/sessions/record-api-sessions.md)
>
> Record and analyze traffic captured from interception workflows.

> [card] [Import HAR Files](https://interceptor-docs.requestly.com/sessions/import-view-har-file.md)
>
> Open and analyze existing HAR files in Requestly Interceptor.

> [card] [Access Control](https://interceptor-docs.requestly.com/sessions/access-control-of-session.md)
>
> Control who can view and use shared sessions.

> [card] [Inspect Traffic First](https://interceptor-docs.requestly.com/interceptor/overview.md)
>
> Start with HTTP Interceptor if you need to capture traffic before recording a reusable session.

> [card] [Mock From Captured Traffic](https://interceptor-docs.requestly.com/guides/record-and-mock-flaky-apis-in-bulk.md)
>
> Use captured sessions to create repeatable mocking workflows.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.