Traffic Inspector

Monitor and capture requests to your mock APIs in real-time, then save them as reusable endpoints.

The Traffic Inspector logs all requests sent to your mock APIs, allowing you to inspect them and save interesting requests as permanent mock endpoints.

How Traffic Inspector Works

The inspector captures requests sent to your mock APIs for analysis and endpoint creation.

Enable Inspector

Turn on traffic logging for your mock API

Send Requests

Make requests to your mock API endpoints

Save as Endpoint

Convert captured requests to mock endpoints

Getting Started

Enable the traffic inspector to start capturing requests to your mock APIs.

Enable Traffic Inspector

1. Navigate to Your Mock API

Go to your mock API dashboard and locate the Traffic Inspector section.

https://your-api.mock.rest

2. Toggle Inspector On

Click the inspector toggle to start capturing traffic. The inspector will capture the last 50 requests.

Free Tier: Last 50 requests

Using the Traffic Inspector

The inspector shows real-time traffic with automatic refresh every 500ms.

Inspector Features

Real-Time Monitoring

• Live traffic updates every 500ms
• View method, path, status, and timing
• Inspect request/response details
• Copy requests for debugging

Save as Endpoint

• Convert any request to a mock endpoint
• Edit response before saving
• Add dynamic template functions
• Set custom status codes

Captured Request Details

View complete request and response information for each captured request.

Example: Captured Request

POST

/api/users/signup

Headers:

Content-Type: application/json
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)
Accept: application/json

Body:

{
  "email": "[email protected]",
  "password": "securepass123",
  "name": "John Doe"
}

Creating Mock Endpoints from Traffic

Convert captured requests into permanent mock endpoints with customization options.

Save as Endpoint Process

Select Request

Click "Save as Endpoint" on any captured request

Customize Response

Edit the response body and add dynamic templates

Save Endpoint

The endpoint is immediately available for use

You can modify the saved response with template functions like {{uuid}} or {{randomName}}

Current Limitations

Understanding what the traffic inspector can and cannot do.

Important Notes

The traffic inspector only captures requests sent directly to your mock API endpoints. It cannot intercept traffic between your app and external APIs.

What It Can Do

✓ Capture requests to mock APIs
✓ Store last 50 requests in memory
✓ Real-time traffic monitoring
✓ Save requests as endpoints

What It Cannot Do

✗ Act as a proxy for external APIs
✗ Capture browser traffic directly
✗ Persist logs after restart
✗ Filter traffic by patterns

Common Use Cases

How teams use the traffic inspector to improve their development workflow.

API Development

Test your app against mock APIs, capture the requests, then build the real API to match the expected interface.

Frontend Testing

Capture successful API responses during development and save them as reliable test fixtures.

Error Scenarios

Manually trigger different responses, capture them, and save as endpoints for error handling tests.

Demo Environments

Build realistic demo data by capturing and customizing actual API responses.

Best Practices

•

Enable the inspector only when actively developing to avoid filling up the 50-request buffer

•

Save important requests as endpoints promptly - logs are lost on server restart

•

Use template functions when saving endpoints to make responses dynamic

•

Review response data before saving to ensure no sensitive information is stored