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. Credentials
  4. /
  5. Revoke a credential

Revoke a credential

Ending a credential permanently, and what happens to the copy already on a phone.

POST/v1/credentials/{id}/revoke

Ends the credential permanently and records who did it.

Request

curl -X POST https://api.nomi-tech.com/v1/credentials/cred_…/revoke \
  -H "Authorization: Bearer nomi_sk_live_EXAMPLE" \
  -H "Content-Type: application/json" \
  -d '{ "reason": "membership_cancelled" }'

The response is the credential, now in revoked, with revokedAt and revocationReason set. Verification refuses it from that moment — including the public page a third party had already bookmarked, and, for a signed academic credential, the status list a verifier checks without calling us at all.

Revocation cannot be undone. If the relationship might resume — a member who is late paying, a contractor between assignments — suspend is the call, and resume puts it back.

Revoking many at once

POST /v1/credentials/bulk

curl -X POST https://api.nomi-tech.com/v1/credentials/bulk \
  -H "Authorization: Bearer nomi_sk_live_EXAMPLE" \
  -H "Content-Type: application/json" \
  -d '{
    "credentialIds": ["cred_…", "cred_…"],
    "action": "revoke",
    "reason": "programme_ended"
  }'

The response says how many were applied and lists the ones that failed, each with its reason — so a run of four hundred does not stop on the first bad row.

Verify a credential

What a verifier sees afterwards.

Revocation API

The endpoints, exactly.

PreviousCredential lifecycleNextVerify a credential

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.