API Request Builder
This action sends data to the server
Why: Managed HTTP requests pass through this deployment's proxy. Native HTTP and gRPC require an authenticated localhost runtime. Mock configurations create a temporary loopback server on your device.
Sent to the server:
- Target URL after {{variable}} substitution
- Method, headers (Authorization included), query string and body — exactly as composed
- SSL/TLS options if you configured them (CA bundle, mTLS cert/key)
- For gRPC: proto files, selected method, metadata and request messages; for mocks: response configuration and allowed browser origins
Data handling: the server relays this request to your target and returns its response; the target receives the fields above.
Request credentials and payloads are not written to application logs. Saved HTTP requests, history, environments and collection plans use browser storage. RPC inputs/results remain in page memory. Mock configuration and recent requests remain in the localhost runtime's memory until stopped, expired or restarted.
Audit the source: src/app/api/proxy/route.ts
Standards, sources and review dates
- PHP cURL · PHP 8.5+ handle cleanup · Reviewed
Generated PHP uses CurlHandle lifetime cleanup rather than curl_close(), which is deprecated as of PHP 8.5. Actual local raw/multipart request fixtures pass. Review interval: 90 days.