Sending a credential to somebody's inbox, and what the message actually contains.
An email is a distribution with channel: "email". Nomi sends the message and tracks what happened to it; what travels inside is the same link as every other channel.
POST /v1/distributions
curl -X POST https://api.nomi-tech.com/v1/distributions \
-H "Authorization: Bearer nomi_sk_live_EXAMPLE" \
-H "Content-Type: application/json" \
-d '{
"credentialId": "cred_…",
"channel": "email",
"wallet": "apple_wallet",
"recipientName": "Alex Morgan",
"recipientEmail": "alex@example.com",
"message": "Your membership card for 2026."
}'channel is how it travels and wallet is where the pass ends up. They are separate on purpose — an email can land in Google Wallet and a QR code in Apple Wallet — and wallet: "web" is the honest answer for a desktop: the public page is the credential.
What you can see afterwards
A distribution moves through created, ready, opened, delivered, installed — or failed, expired, revoked. GET /v1/distributions is the same table the Distribution Center shows, filtered by credential, channel, wallet or status.
Sending to many people
Bulk sends are queued rather than sent in a burst, with a ceiling per hour, so a graduation of four hundred does not get the whole batch treated as spam. See Bulk issuance.