Authentication
Every request carries an API key as a bearer token:
Authorization: Bearer fry_rt_…There are two key types. Create and revoke them on the API keys page of the dashboard; a key’s secret is shown once.
| Type | Prefix | Accepted on | Can |
|---|---|---|---|
| Runtime | fry_rt_ |
<org>.frysis-proxy.net |
Create, read (metadata) and delete payloads; call ingress endpoints. Use in your production backend. |
| Management | fry_mg_ |
api.frysis.com |
Everything the dashboard can configure: egress, ingress, secrets, runtime keys, organization. Use in CI or infrastructure-as-code. |
- A missing, malformed or revoked key returns
unauthorized(401). - The right key on the wrong host returns
wrong_key_type(403). - A runtime key used on another organization’s subdomain returns
not_found(404). - Management keys can’t create, list or revoke management keys; that’s dashboard-only.