Bulk issuance

Issuing and sending at the scale of a graduation or an onboarding day.

There are three ways to do something for many people, and they are not interchangeable.

1. 1

   Upsert the people first

   PUT /v1/subjects is idempotent on externalId, so a re-run of your sync is safe. A group can also be imported in one call with POST /v1/groups/{id}/import.

2. 2

   Issue

   For wallet credentials, one POST /v1/credentials per person with an Idempotency-Key. For academic credentials, POST /v1/awards/bulk takes up to 500 recipients in one request.

3. 3

   Send

   A campaign queues the messages and paces them, instead of emptying four hundred emails into a queue at once.

curl -X POST https://api.nomi-tech.com/v1/awards/bulk \
  -H "Authorization: Bearer nomi_sk_live_EXAMPLE" \
  -H "Content-Type: application/json" \
  -d '{
    "achievementKey": "leadership_2026",
    "recipients": [
      { "subjectId": "sub_…" },
      { "subjectId": "sub_…", "narrative": "Completed with distinction." }
    ]
  }'

Every row is attempted on its own. One person missing a required field fails that row and nothing else — a graduation does not stop on the one record that was never filled in, and the response says exactly which ones to fix.

Acting on many at once

POST /v1/credentials/bulk applies suspend, resume, revoke or expire to a list of credential ids and answers with how many were applied and which failed.