API v1 uses custom HTTP headers to provide metadata for encryption, decryption, and authentication for legacy proxy requests.

Authentication Header

string

required

Your unique API key used for authentication.

Content Control

string

required

Specifies the action to perform on the payload.Allowed values: encrypt, decrypt

string

required

A comma-separated list of field names in the JSON payload to be processed.

string

required

Must be set to application/json for all requests containing a JSON payload.

string

A URL to forward the encrypted data to. If provided, the processed payload will be sent to this destination instead of being returned to the client.

When using X-Qanapi-Destination, all non-Qanapi headers will be forwarded to the destination URL along with the processed payload.

Learn more about legacy v1 proxy requests in the overview.