Server-Side MITMServer MITM• 5 min read

How to Override API Responses Server-to-Server Using Proxy Forwarding

Summary: Route server-to-server HTTP calls through ProxyCeptor forwarder to apply active profile mocks, merges, and block rules without browser extensions.

Why This Rule Matters for Developers & QA

Backend microservices, curl scripts, and CI/CD pipelines cannot run Chrome extensions. The server-side forwarder route applies active workspace rules to any HTTP client.

Step-by-Step Implementation Guide

Send Request Through Proxy Route

Direct your client to `https://api.proxyceptor.com/proxy?url=https://api.thirdparty.com/data` or use the `x-target-url` header.

Provide API Key & Override Header

Attach `x-sdm-api-key: YOUR_KEY` and `x-sdm-server-override: true`.

Receive Intercepted Response

The server executes your active workspace rules (synthetic mocks, deep merges, status flips) and returns the modified response directly.

Configuration Snippet

How to Override API Responses Server-to-Server Using Proxy Forwarding — proxyceptor-rule.json

JSON

1curl -X GET "https://api.proxyceptor.com/proxy" \
2  -H "x-target-url: https://api.production.com/v1/status" \
3  -H "x-sdm-api-key: your_api_key_here" \
4  -H "x-sdm-server-override: true"

Frequently Asked Questions

Explore More Debugging Guides

Redirect / Rewrite

URL Modify & Redirect

4 min read

JSON Deep Merge

Payload Modify & Deep Merge

5 min read

Inject Headers

Request Header Modify

4 min read