Verifiable credential issuance API

Turn a claim into a credential
anyone can verify.

Inflowra signs W3C Verifiable Credentials, mobile driving licences, and SD-JWT VCs through one API. We sign what you send us — we don’t keep it.

Read the docs

Standards-compliant with W3C VC 2.0, ISO/IEC 18013-5, and OpenID4VC.

credential.json
{
  "credentialSubject": {
    "role": "Backend Engineer",
    "clearance": "L2"
  },
  "issuer": "did:web:inflowra.io",
  "issuanceDate": "2026-07-08T09:12:00Z",  "proof": {
    "type": "DataIntegrityProof",
    "cryptosuite": "eddsa-rdfc-2022",
    "proofPurpose": "assertionMethod",
    "proofValue": "z58DAdF...3jT9c2"
  }
}

Built on

W3C VC 2.0ISO/IEC 18013-5 (mDL)DID Core 1.0SD-JWT VCOpenID4VCBitstringStatusList

By the numbers

Running in production.

Real usage across issuers building on Inflowra today.

Credentials issued

Active issuers

Verifications performed

0.00%

API uptime

Why Inflowra

Built around three constraints.

The parts of credential issuance most platforms get wrong.

Nothing stored

Claims and keys pass through the API and never touch a database. What you send is what gets signed — then it's gone.

Every format, one API

SD-JWT, mdoc, and JSON-LD credentials come from the same request shape. Switch formats without switching integrations.

No verifier lock-in

Anything issued through Inflowra is checkable by walt.id, Credo-TS, or your own verification code. Standard formats, no proprietary wrapper.

How it works

Four steps, one request cycle.

No provisioning calls, no onboarding review. Register a schema once, then issue credentials on demand.

Register a schema

Define the shape of the credential you want to issue — the claims, their types, and the format.

Send claims + a holder DID

POST the subject's claims and their decentralized identifier to the credentials endpoint.

Get back a signed VC

Inflowra signs the payload and returns a complete, standards-compliant verifiable credential.

Anyone can verify it

The holder presents it, and any compliant verifier can check the signature — no call back to us.

API

It’s just a request and a response.

No SDK required to get started — a single authenticated POST returns a signed credential.

Request

curl https://api.inflowra.io/v1/credentials \ -H "Authorization: Bearer sk_live_..." \ -H "Content-Type: application/json" \ -d '{ "format": "vc+sd-jwt", "type": "EmployeeCredential", "holder": "did:key:z6Mkf...", "claims": { "role": "Backend Engineer", "clearance": "L2" } }'

Response · 200 OK