Skip to content

How Frysis works

Frysis sits between your backend and the APIs you call. Your backend stores sensitive data in Frysis once and keeps only a token. When you need to send that data somewhere, your backend calls one of your Frysis endpoints with the token; Frysis fills the real values into the upstream request and returns the upstream’s response.

  • Payload: a flat set of key/value pairs (strings, numbers, booleans) such as a card number and expiry. Stored encrypted, identified by a fry1. token, immutable, and never readable back through any API or the dashboard. To change data, create a new payload.
  • Secret: an organization-level value such as an upstream API key. Write-only; used in egress templates as {{secret.<name>}}.
  • Egress: a template for one upstream request: method, URL, headers and body, with placeholders. See Egress templates.
  • Ingress endpoint: a method and path you define, such as POST /charge, bound to one egress. Your backend calls it on your proxy host.
Host API key What it’s for
api.frysis.com management Configuration: egress, ingress endpoints, secrets, runtime keys. Mirrors the dashboard.
<org>.frysis-proxy.net runtime Your traffic: creating and deleting payloads, and proxy calls to /ingress/<path>.

<org> is your organization’s slug, shown on the Organization page of the dashboard.

  1. Your backend stores a card: POST https://<org>.frysis-proxy.net/v1/payloads → {"token": "fry1.…"}. You save the token.
  2. Later, your backend calls POST https://<org>.frysis-proxy.net/ingress/charge with {"payloads": {"card": "fry1.…"}, "input": {"amount": 1000}}.
  3. Frysis finds the egress bound to that endpoint, decrypts only the payloads it needs, fills the template and sends the request upstream.
  4. The upstream’s response comes back to you unchanged.

If any value the template needs is missing, Frysis returns missing_values and sends nothing.