Payloads
Base URL: https://<org>.frysis-proxy.net · Key: runtime
Payloads are write-only and immutable. Their values can never be read back; they leave Frysis only inside an upstream request.
Create a payload
Section titled “Create a payload”POST /v1/payloads
{ "data": { "number": "4242424242424242", "exp_month": 12, "exp_year": 2030, "cvc": "123" } }datais a flat object: values are strings, finite numbers or booleans. No nested objects, arrays ornull.- Keys start with a letter or underscore and contain letters, digits and underscores (max 64 characters).
- Up to 50 keys and 64 KB.
201 Created
{ "token": "fry1.QCsC6MLZ74jxuFzDFf3XfvaqUCFU", "keys": ["number", "exp_month", "exp_year", "cvc"], "size_bytes": 72, "created_at": "2026-11-22T08:00:20.510Z" }Get payload metadata
Section titled “Get payload metadata”GET /v1/payloads/:token returns the same fields as create: token, key names, size and creation time. Never values.
Delete a payload
Section titled “Delete a payload”DELETE /v1/payloads/:token → 204 No Content. Deletion is permanent and the token stops working immediately.
Tokens
Section titled “Tokens”Tokens look like fry1.QCsC6MLZ74jxuFzDFf3XfvaqUCFU: the fry1. prefix followed by 28 base58 characters, 33 in all. Store all 33 characters.
- The token carries a checksum, so a typo, a truncated token or a character outside base58 is rejected with
invalid_tokenbefore any lookup. - Tokens are random: two payloads with the same data get different tokens.
- Treat tokens as sensitive references. They’re useless without your runtime key, but don’t publish them.