Skip to main content
POST

Authorizations

X-Qanapi-Authorization
string
header
required

A machine credential, qk_ followed by its secret. The first twelve characters are an indexed prefix; the rest is compared in constant time against a stored SHA-256 hash. A key reaches only the configurations it is linked to.

It may also be sent as Authorization: Bearer qk_..., which is recognised by the prefix.

Headers

X-Qanapi-Fields
string

Comma-separated dot paths to encrypt or decrypt, for example ssn,user.address.postcode. Absent in whole-body mode.

Example:

"ssn,user.dob"

X-Qanapi-Full-Body
string

Treat the whole body as one payload. true, 1, yes or on.

Example:

"true"

X-Qanapi-Mode
enum<string>

Alternative spelling of whole-body mode; full_body.

Available options:
full_body,
full-body
X-Qanapi-Destination
string<uri>

Forward the processed payload to this absolute URL and relay the answer back. Every request header travels except x-qanapi-*, authorization and the hop-by-hop set. Restricted by FORWARD_ALLOWED_HOSTS where the installation sets it.

Path Parameters

proxy
string
required

The configuration's proxy slug. Sixteen random lowercase characters unless one was pinned at creation.

Example:

"952zpx6vyig3sdyp"

Body

The body is of type string.

Response

The plaintext, in the shape it was encrypted from.