nomiDocumentation
SupportBack to site
  • Getting started

    • Introduction
    • What is Nomi?
    • Quick start
    • Concepts
    • Authentication
  • Credentials

    • Create a credential
    • Issue a credential
    • Credential lifecycle
    • Revoke a credential
    • Verify a credential
    • QR verification
  • Distribution

    • Apple Wallet
    • Google Wallet
    • Email
    • Credential delivery
    • Bulk issuance
  • API

    • API overview
    • Authentication
    • Credentials API
    • Recipients
    • Verification
    • Revocation
    • Webhooks
    • Errors
  • Integrations

    • Moodle
    • WordPress
    • REST API
    • Webhooks
  • Security

    • Authentication
    • API keys
    • Webhook security
    • Data protection
    • Best practices
  • Resources

    • FAQ
    • Glossary
    • Changelog
  1. Documentation
  2. /
  3. Distribution
  4. /
  5. Credential delivery

Credential delivery

The distribution object: one link that is the QR, the email and the tag.

A distribution mints a link for one credential and returns it. That link is the whole delivery: a QR code is it drawn, an NFC tag is it written, an email is it inside a message.

POST/v1/distributions

Hands a credential to somebody, on one channel, for one wallet.

FieldValues
credentialIdThe credential being handed over. Required.
channellink, qr, email, api, web, app, nfc — how it travels.
walletapple_wallet, google_wallet, web — where the pass ends up.
recipientName, recipientEmailWho it is for. Required for email.
messageA line the recipient sees.
expiresAtWhen the link stops working.

201 Created

{
  "id": "…",
  "url": "https://…",
  "code": "…",
  "channel": "qr",
  "wallet": "apple_wallet",
  "status": "ready",
  "credential": { "id": "cred_…", "serial": "…", "state": "issued" }
}
If the credential was issued without the wallet you ask for, the channel is created and queued. The distribution stays created until there is something to hand over, then becomes ready.

Taking a link back

POST /v1/distributions/{id}/revoke kills one link without touching the credential — the right call when a message went to the wrong address. POST /v1/distributions/{id}/regenerate issues a fresh one in its place.

Bulk issuance

Four hundred at once.

QR verification

Reading it back.

PreviousEmailNextBulk issuance

Still stuck?

If this page did not answer it, the Help Center has the operational side of the same question — and a person reads what you send.

Go to the Help Center →
nomi

Digital credential infrastructure. Create, issue and manage credentials from the systems you already use.

Operated by

Country and currency

Platform

  • How it works
  • Templates
  • Lifecycle
  • Developers
  • Pricing
  • FAQ
  • Nomi Academic

Credentials

  • Memberships
  • Employee IDs
  • Student IDs
  • Events & loyalty

Developers

  • Documentation
  • Quick start
  • API reference
  • Webhooks
  • Integrations

Support

  • Help Center
  • Apple & Google Wallet
  • Verification
  • Contact support

Company

  • Request a demo
  • Talk to Nomi
  • Legal
  • Codingraph
PrivacyTermsCookiesSecurityContact

© 2026 Codingraph S.A. All rights reserved.

Nomi is a registered trademark used by Codingraph S.A. under licence.

Billed in USD

Apple Wallet and Google Wallet are trademarks of their respective owners.