Skip to main content
Version: 1

Yopass API

The HTTP API for creating and retrieving secrets, files and secret requests.

Encrypt before you send. The server checks the format, not the content: it rejects a message that is not ASCII-armored OpenPGP, but an armored message can still be unencrypted, and the server cannot tell. Only a correct client sends ciphertext. The label and note of a secret request are stored as plain text, so keep secrets out of them. Read the API guide for the encryption model and a worked example, or use the CLI to skip writing encryption code.

Some routes only exist when the server is configured for them. A route that is switched off answers 404 with a plain-text 404 page not found body, the same as an unknown URL:

Server settingRoutes that disappear
--read-onlyPOST /create/secret, POST /create/file and every /request route
--disable-uploadPOST /create/file, /file/{key} and /file/{key}/status
--prefetch-secret=falseGET /secret/{key}/status and GET /file/{key}/status
no licenseevery /request route (an expired license keeps them, but POST /request answers 403)

Licensed features. Secret requests, read receipts and require_auth token-gated creation need a licensed server. Operations marked Requires a licensed server answer 404 or 400 without one.

Authentication​

A static token the server operator configures with --api-token. It authorizes the creation endpoints only (/create/secret, /create/file, /request). See OpenID Connect.

Security Scheme Type:

http

HTTP Authorization Scheme:

bearer

License

Apache 2.0