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. Integrations
  4. /
  5. WordPress

WordPress

The state of a WordPress plugin today, and what to use in the meantime.

Coming soon

There is no Nomi plugin for WordPress yet. Nothing on this page should be planned against as if there were.

A WordPress or WooCommerce site can still issue credentials today, because everything a plugin would do is an ordinary HTTP call. The shape is the same as any other integration:

  1. 1

    Upsert the member

    On registration or on a successful order, PUT /v1/subjects with your site's user id as externalId.

  2. 2

    Issue

    POST /v1/credentials with the template key for that membership level.

  3. 3

    Deliver

    POST /v1/distributions with channel: "email", or show the link in the member's account area.

  4. 4

    End it

    On cancellation or refund, POST /v1/credentials/{id}/revoke — or suspend while a payment is being retried.

Issuing from PHP

$response = wp_remote_post( 'https://api.nomi-tech.com/v1/credentials', array(
    'headers' => array(
        'Authorization'   => 'Bearer ' . NOMI_API_KEY,
        'Content-Type'    => 'application/json',
        'Idempotency-Key' => 'order-' . $order_id,
    ),
    'body'    => wp_json_encode( array(
        'subjectId'   => $subject_id,
        'templateKey' => 'membership_platinum',
        'channels'    => array( 'apple_wallet', 'google_wallet' ),
    ) ),
) );
The key belongs on the server, in your site's configuration — never in a theme, a page template or anything that reaches a browser.

REST API

The general pattern.

API keys

Where to keep it.

PreviousMoodleNextREST 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 →
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.