Proxy calls
Base URL: https://<org>.frysis-proxy.net/ingress · Key: runtime
Each ingress endpoint you define (for example POST /charge) is served at https://<org>.frysis-proxy.net/ingress/charge with the method you chose.
Request body
Section titled “Request body”{ "payloads": { "card": "fry1.QCsC6MLZ74jxuFzDFf3XfvaqUCFU" }, "input": { "amount": 1000, "currency": "usd" }}payloads: name → token. The names are the ones your egress template uses:{{payloads.card.number}}needs a payload namedcard. Tokens the template doesn’t use are ignored.input: plain, non-sensitive values, used as{{input.<field>}}. Any JSON values.- Both are optional; an endpoint whose template uses neither can be called with
{}. Content-Type: application/json, at most 1 MB.
Secrets are never sent in the call; Frysis fills {{secret.<name>}} from your organization’s secrets.
Response
Section titled “Response”If the call reaches the upstream, the upstream’s response is returned unchanged: status, headers (except connection-level ones) and body. A 402 from the upstream reaches you as a 402 with its body.
Every response has a frysis-request-id header. Errors that Frysis itself returns are problem details with the same request_id.
Errors before anything is sent
Section titled “Errors before anything is sent”| Status | Code | Cause |
|---|---|---|
| 400 | invalid_json, invalid_body |
Malformed body, bad payload name or malformed token |
| 404 | endpoint_not_found |
No enabled endpoint for this method and path |
| 422 | missing_values |
The template needs a value the call didn’t provide |
| 422 | unknown_token |
A token that doesn’t exist |
| 503 | vault_unavailable |
Retry with backoff |
When the upstream can’t be reached or times out you get upstream_unreachable (502) or upstream_timeout (504).