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. API
  4. /
  5. API overview

API overview

Base URL, request shape, pagination, idempotency and what a version means here.

A REST API over JSON. Every request is authenticated with a bearer token, every resource belongs to the organisation that token belongs to, and every write can be retried safely.

The shape of a request

POST /v1/credentials HTTP/1.1
Host: api.nomi-tech.com
Authorization: Bearer nomi_sk_live_EXAMPLE
Content-Type: application/json
Idempotency-Key: order_example_12345

Base URL and version

Everything lives under https://api.nomi-tech.com. The /v1 prefix is the API's version: fields are added to responses without notice, and nothing is removed or given a new meaning inside a version.

Pagination

List endpoints take limit (1–100, default 25) and page in one of two ways. cursor is the nextCursor from the previous response and is what a job should use. offset also returns total, which is what a screen showing page numbers needs.

Any list response

{
  "data": [ … ],
  "nextCursor": "…",
  "total": 1284
}

Idempotency

Send an Idempotency-Key on any POST or PATCH and a retry replays the first response instead of doing the work twice. Keys live for 24 hours and are scoped to your organisation. Three cases:

  • Same key, same request, already answered — the stored response is replayed.
  • Same key, a different request — refused. Serving the first answer to a second, different call is a write that disappears silently.
  • Same key, still running — 409. Retry in a moment.

Credentials API

The main family.

Errors

The shape, and the codes.

PreviousBulk issuanceNextCredentials API

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 →

On this page

  • Base URL and version
  • Pagination
  • Idempotency
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.