Migration approach
Proxy Hopper requires a single code change: instead of calling the third-party API directly, point your HTTP client at Proxy Hopper and add theX-Proxy-Hopper-Target header.
The migration is typically done per-client or per-service and can be rolled out incrementally.
Migrating from direct API calls
Before:Authorization, X-API-Key, etc.) are passed through to the destination unchanged. Only X-Proxy-Hopper-* headers are consumed and stripped by Proxy Hopper.
Migrating from a standard HTTP proxy
If your application was previously using an HTTP proxy via environment variables or proxy settings, the migration is straightforward. Before (proxy viarequests proxy settings):
- Remove proxy settings from your client configuration
- Set
X-Proxy-Hopper-Targeton the session - Change the base URL to point at Proxy Hopper
Migrating multiple API integrations
For applications that call several different APIs, use one session per API:httpx migration
aiohttp migration
Verifying the migration
- Check the Proxy Hopper logs — you should see requests being dispatched for your target
- Verify responses are as expected
- Check Prometheus metrics (if enabled) —
proxy_hopper_requests_totalshould show new requests
Non-idempotent requests
If you havePOST, PUT, PATCH, or DELETE calls, set retries to 0 to avoid duplicate actions on failure: