Reproduce difficult integration bugs

Intercept, inspect, and mock API traffic with one click

Route HTTP and HTTPS traffic through Beeceptor to debug live integrations, capture outbound calls, and control upstream responses directly from your dashboard.

   
proxy.beeceptor.com:8080
MethodHostPathStatus
GETapi.github.com/users/defunkt200 OK
POSTcheckout.stripe.com/v1/chargesMocked
DELETEapi.mybackend.internal/records/892403 Err

How Forward Proxy Works

Seamlessly sit between your client and upstream services to gain complete visibility and control over your traffic.

Route Traffic

Configure your browser, script, mobile device, or test runner to use Beeceptor as a forward proxy using the HTTP CONNECT method.

Decrypt & Inspect

Install the Beeceptor proxy CA certificate to enable SSL inspection and view full request and response payloads in plain text.

Mock or Forward

Define rules to return static mocks, simulate delays, or forward requests to the original destination untouched.

Universal Client Configuration

Connect any client that supports standard HTTP/HTTPS proxies.
Download the CA cert to get started with TLS inspection.

Terminal & Shell

Route backend services, SDKs, curl commands, and CLI tools through Beeceptor using standard proxy environment variables.

Authenticate with endpoint name and proxy password.
Verify with the Beeceptor echo endpoint before testing real APIs.
# HTTP and HTTPS traffic
export http_proxy="http://:@forward-proxy.beeceptor.com:8443"
export https_proxy="http://:@forward-proxy.beeceptor.com:8443"

# Test the configuration
curl https://echo.free.beeceptor.com/

Chrome Browser

Launch Chrome with an isolated browser profile so forward proxy testing stays separate from your everyday browser session.

Trust the Beeceptor Proxy CA certificate for HTTPS inspection.
Sign in to the proxy prompt with endpoint name and password.
google-chrome \
  --proxy-server=http://forward-proxy.beeceptor.com:8443 \
  --user-data-dir=/tmp/beeceptor-chrome \
  https://echo.free.beeceptor.com/

Playwright / E2E

Route Chromium test traffic through Beeceptor to inspect frontend API calls, mock selected integrations, and keep application code unchanged.

Add a proxied project to your Playwright config.
Run only that project when you need captured browser traffic.
proxy: {
  server: 'http://forward-proxy.beeceptor.com:8443',
  username: '',
  password: '',
}

macOS & Android

Capture system or mobile app traffic by trusting the Beeceptor Proxy CA and routing HTTP/HTTPS traffic to the forward proxy host.

View Setup Guides

macOS

Enable Web Proxy and Secure Web Proxy with server `forward-proxy.beeceptor.com` on port `8443`.

Android

Install the proxy CA, set Wi-Fi proxy to Manual, then use host `forward-proxy.beeceptor.com` and port `8443`.

Filter:Host: api.github.com
GET /users/octocatCaptured
POST /analytics/trackIgnored

Live Traffic Monitor & Host Filtering

Watch outbound requests land in the endpoint Console with method, host, path, status, and timing. Use Host Filter to focus on one upstream service while background traffic stays out of the way.

Filter captured traffic by target host during debugging.
Inspect the exact request your client sends before it reaches the API.

Advanced Mocking & Overrides

Intercept requests before they reach the server and respond with static or dynamic mocks. Perfect for simulating edge cases, errors, or APIs still in development.

Return custom JSON payloads instantly.
Simulate HTTP 500 errors or network timeouts.
Modify request headers before forwarding.
If request matchesPath contains /checkout
Then respond with500 Internal Server Error
{"error":"Payment gateway timeout"}
Search logs: status:500 path:/checkoutExport HAR
200GET /api/v1/users2ms ago
502POST /checkout/process15ms ago
404GET /static/logo.png1m ago
201PUT /profile/update5m ago

Request Logs & History

Turn every proxied call into a searchable trail your team can revisit after the live debugging session. Keep recent request and response payloads for up to 15 days, isolate failures by path, status, headers, or body content, and export HAR files when an issue needs deeper analysis.

Come back to captured traffic after the first debugging pass.
Spot failed requests faster with filters for status, path, method, headers, body, attachments, and time range.
Share HAR exports with teammates for offline review.