Skip to main content
POST
Mint receipt
Creates a cryptographically signed, transparency-log-anchored receipt event. Receipts are validated against the registered receipt type schema before signing.

Receipt types

Headers

string
required
UUID for idempotent minting. If you submit the same key twice, the original receipt is returned.

Request

string
required
UUID of the issuer signing the receipt.
string
required
Key ID of the signing key.
string
required
Signing algorithm: Ed25519, ES256, or RS256.
string
required
Receipt type name (e.g. payment_receipt, security_event_receipt, or a custom type).
string
required
Subject identifier for the receipt.
object
required
Receipt payload — validated against the receipt type’s JSON Schema.
object
Optional metadata attached to the receipt envelope.

Response

string
UUID of the created receipt.
string
The receipt type name.
string
active
string
UUID of the signing issuer.
string
Subject identifier.
object
Cryptographic signature: alg, kid, value.
string
ISO 8601 timestamp.

Webhook event

A receipt.created webhook event is delivered to all configured endpoints after a successful mint.

Authorizations

X-API-Key
string
header
required

API key for machine-to-machine authentication

Headers

Idempotency-Key
string
required

UUID for idempotent minting

Body

application/json
issuer_id
string
required

UUID of the issuer signing the receipt

kid
string
required

Key ID of the signing key

alg
enum<string>
required

Signing algorithm

Available options:
Ed25519,
ES256,
ES384,
ES512,
RS256,
RS384,
RS512,
PS256,
PS384,
PS512
receipt_type
string
required

Receipt type name

subject
string
required

Subject identifier

payload
object
required

Receipt payload validated against schema

metadata
object

Optional metadata

Response

Receipt created

receipt_id
string
receipt_type
string
status
string
issuer_id
string
subject
string
signature
object
issued_at
string