Skip to main content
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

Use this path when you want browser-focused debugging context such as screen activity, console logs, network logs, and environment details.

Record Bug Reports

Capture reproducible bug reports directly from the browser workflow.

​
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 or Record API Sessions 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

Record Bug Reports

Capture browser activity and rich debugging context for issue reproduction.

Capture API Sessions

Record and analyze traffic captured from interception workflows.

Import HAR Files

Open and analyze existing HAR files in Requestly Interceptor.

Access Control

Control who can view and use shared sessions.

Inspect Traffic First

Start with HTTP Interceptor if you need to capture traffic before recording a reusable session.

Mock From Captured Traffic

Use captured sessions to create repeatable mocking workflows.