Sign upLog in

Platform overview

Inflowra is a credential issuance API. You send it a subject's claims and a holder identifier; it validates them against your schema, signs them inside its key service, and returns a standards-compliant verifiable credential. The holder presents that credential wherever they need to, and any compliant verifier can check it — without calling Inflowra.

How issuance works

  1. Define a schema. Describe the shape of the credential you want to issue — the claims, their types, and the format.
  2. Send claims + a holder DID. POST the subject's claims and their decentralized identifier to the credentials endpoint.
  3. Receive a signed credential. Inflowra signs the payload and returns a complete, standards-compliant verifiable credential.
  4. Verify anywhere. The holder presents it, and any compliant verifier can check the signature — no call back to us.

Design principles

Stateless by design

Claims and keys pass through the API and never touch a database. What you send is what gets signed — then it's gone. Request logs record that an issuance happened (issuer, schema, format, timestamp) — never what was in it. The trade-offs are deliberate: Inflowra cannot reissue a lost credential (your system re-sends the claims) and there is no claim-level history dashboard. Read more in Why we don't store what we sign.

One request shape, every format

SD-JWT, mdoc, and JSON-LD credentials come from the same request shape. Switch formats without switching integrations — set the format field and keep the rest of your request unchanged.

Verifiable with standard tooling

Anything issued through Inflowra is checkable by walt.id, Credo-TS, or your own verification code. Standard formats, no proprietary wrapper. Inflowra also operates a hosted verify API and a public verify portal for spot checks.

Platform components

  • Issuance API — the core credentials endpoint your backend calls.
  • Issuer portal — manage issuers, API keys (create / rotate / revoke), plans and billing.
  • Verify API — public, unauthenticated endpoint that checks signature and revocation status for any pasted credential.
  • Hosted status lists — revocation infrastructure included on paid plans.

Plans

Plans are credit-based, sized by credentials issued per month (e.g. 1,000/month on the starter tier and 25,000/month on the growth tier, with SSO/SAML, audit exports and a dedicated support channel on the enterprise tier). See pricing for current numbers.