Skip to main content
A business first mints a signed attestation, then delivers a reference to a consumer. Delivery does not mint the attestation, verify its claims, or make private records public.

1. Mint

Follow the quickstart using the business workspace’s issuer and signing key. Provide application claims through structured schema and claims input, or encode the exact original bytes as payload_b64url. Do not combine both modes. Keep the returned attestation_id; do not substitute a made-up att_ identifier where the API requires a UUID.

2. Deliver

Use Deliver to inbox with attestation_id, the recipient’s email in consumer_reference, and optional safe_metadata. Use an issuer credential for the workspace owning the attestation. HTTP 201 records delivery to an existing consumer inbox. HTTP 202 with status: pending and reason: consumer_not_registered records a pending delivery. Neither response proves an email reached the recipient. Avoid sensitive claims in display metadata.

3. Read the inbox

The consumer authenticates separately and uses Inbox. read_state accepts UNREAD, READ, ARCHIVED, or ALL. A business key must not be used as the consumer’s identity. Inbox delivery and public portfolio visibility are separate. Do not assume an inbox item was publicly shared merely because delivery succeeded.

4. Verify

Use Verify with the attestation ID, and optionally the original encoded payload or document hash. This endpoint does not accept a base64 proof_bundle field. Inspect the verdict and reasons rather than HTTP status alone. For offline proofs, follow the proof bundle specification. Offline cryptographic validation needs trusted public keys and cannot establish current revocation status without fresh status information. Neither online nor offline signature verification proves the underlying real-world claim is true.