License keys are the License Key entitlement type. Create a License Key entitlement once with the activation limit, expiry, and instructions you want, attach it to any product, and Dodo Payments generates and delivers a key per purchase or subscription seat, automatically.
What are License Keys?
License keys are unique tokens that authorize access to your product. They’re ideal for:- Software licensing: Desktop apps, plugins, and CLIs
- Per-seat controls: Limit activations per user or device
- Digital goods: Gate downloads, updates, or premium features
Create a License Key Entitlement
1
Open Entitlements
Go to Entitlements in your Dodo Payments dashboard and click + to create a new entitlement.
2
Choose License Key
Select License Key as the integration. Configure how each issued key behaves:
- Activations Limit: Maximum concurrent activations per key (e.g.,
1for single-user,5for team licenses, leave blank for unlimited). - Duration: How long the key stays valid after issuance (e.g., 30 days, 1 year). For subscription-issued keys, leave blank; keys remain valid as long as the subscription is active.
- Activation Instructions: Customer-facing instructions emailed with the key. Examples:
Paste the key in Settings → LicenseorRun: mycli activate <key>.

3
Save the entitlement
Save. The entitlement is now available to attach to any product.
Attach to Products
Open a product, expand Advanced Settings → Entitlements & Credits, and select your License Key entitlement. A single product can deliver a license key alongside other entitlements (Discord access, file downloads, GitHub repo access, etc.) on the same purchase.
Selecting the License Key entitlement in the product entitlements panel.
How Keys Are Issued
Key issuance follows the standard grant lifecycle:Quantity behavior
- Subscription products issue one key per seat (
subscriptions.quantity). - One-time products issue one key per cart line item (
product_cart.quantity). - Manual API grants issue exactly one key.
Fulfillment mode
Every License Key entitlement has afulfillment_mode that controls who supplies the key:
auto(default): Dodo Payments generates and emails the key automatically on payment or subscription. This is the behavior described above and applies whenfulfillment_modeis omitted.manual: The purchase creates aPendinggrant with no key, and you supply each key value yourself. See Manual Fulfillment below.
Manual Fulfillment
By default, Dodo Payments generates and emails a license key the moment a customer pays. With manual fulfillment you supply the key yourself: the purchase creates aPending grant with no key, notifies you, and waits for you to submit the key value. Use it when keys come from your own system, a third-party vendor, or a finite pool of pre-printed codes.
Looking for a step-by-step build? See the Manual License Key Fulfillment Integration Guide for an end-to-end walkthrough from product creation to delivering the key.
When to use it
Auto fulfillment is the right default for most software licensing. Choose manual fulfillment when Dodo Payments cannot mint the key itself:- Bring-your-own-keys: The key is generated by your application, a desktop product, or your own license server.
- Third-party vendors: You resell keys issued by an upstream provider (a game key, an API credential, a partner platform).
- Finite inventory: You hand out codes from a pre-allocated pool and want to assign them one at a time.
- Human review: You want to vet a purchase before releasing access.
Enable manual fulfillment
Setfulfillment_mode: "manual" on the License Key entitlement’s integration config:
fulfillment_mode is backward compatible. Entitlements created before this setting existed have no fulfillment_mode and continue to behave as auto. Switching to manual only affects grants created after the change; keys already delivered are untouched.Find grants awaiting fulfillment
When a customer buys a manual-mode product, the grant is created inPending status with no key and an entitlement_grant.created webhook fires with integration_type: "license_key" and status: "Pending". You can react to that webhook, or poll the List Customer Grants endpoint with the integration_type and status filters:
Deliver the key
Submit the key with the Fulfill License Key Grant endpoint. The grant moves toDelivered and the customer is sent the key automatically — the same email they would receive under auto fulfillment.
cURL
activations_limit and expires_at are optional and fall back to the entitlement config when omitted. Each grant can be fulfilled once; retrying an already-fulfilled grant returns 409 rather than issuing a second key.
You do not need to email the key yourself — delivery happens automatically when the grant is fulfilled. This differs from importing keys via
POST /license_keys, which intentionally does not notify the customer.Activation, Validation, Deactivation
The activation/validation/deactivation API endpoints are public and require no API key. Use them directly from desktop software, CLIs, or browser-based clients to verify keys at runtime.Public Endpoints: The activate, deactivate, and validate license endpoints are public and do not require an API key. Call them directly from your client applications without exposing your API credentials.
Activate a license
Validate a license
Deactivate an activation instance
Manage Keys
Open the License Key entitlement from your dashboard to see every grant (one row per customer key) with delivery date, activation count, and a revoke action. Each grant detail surfaces the underlying license key, expiry, activations used, and the activations limit. You can also list grants programmatically:Import Existing License Keys via API
Already have license keys in another system? Use the Create License Key API to import them into Dodo Payments. This lets you migrate existing keys without disrupting your customers — they continue to activate, validate, and deactivate against the same key strings without re-issuance.How keys differ by source
Usa il campo
source nei record delle license key per distinguere l’inventario migrato e le chiavi assegnate manualmente dalle chiavi emesse automaticamente durante la riconciliazione o l’audit. Leggilo dall’oggetto license_key nei grant restituiti da List Grants; l’endpoint legacy GET /license_keys è deprecato.
License Keys in Return URL
When a customer completes a purchase for a product with a License Key entitlement, the generated key is automatically appended to yourreturn_url as a query parameter. This lets you display the key immediately on your success page without making an extra API call.
subscription_id is used instead of payment_id:
API Management
Lifecycle Operations (Public Endpoints)
Lifecycle Operations (Public Endpoints)
Activation, deactivation, and validation are public; no API key required.
Activate License
Create or record an activation instance for a license key.
Deactivate License
Revoke a prior activation to free up capacity.
Validate License
Check authenticity, status, and constraints before granting access.
License Key Management
License Key Management
Create, list, retrieve, and update individual license key records. Use these to import existing keys or fetch usage details.
Create License Key
Crea una nuova license key o importane una esistente.
List License Keys
Visualizza tutte le chiavi con i dettagli sullo stato e sull’utilizzo.
Get License Key
Recupera una chiave specifica e i relativi metadati.
Update License Key
Modifica la scadenza, i limiti di attivazione oppure abilita/disabilita una chiave.
Entitlement Management
Entitlement Management
Gestisci l’entitlement License Key stesso: il relativo limite di attivazione, la durata e le istruzioni.
Create Entitlement
Crea un entitlement License Key.
Update Entitlement
Aggiorna la configurazione dell’entitlement.
List Grants
Elenca le chiavi emesse per un entitlement.
Revoke Grant
Revoca manualmente la chiave di un cliente.
Webhook
La consegna e la revoca delle license key attivano i quattroentitlement_grant.* eventi webhook. Il payload del grant include un oggetto license_key compilato con la chiave, la scadenza, le attivazioni utilizzate e il limite.
Gli eventi legacy license_key.* (license_key.created) continuano ad attivarsi per il ciclo di vita del record della license key sottostante; consulta la pagina del payload webhook della License Key.
License Key legacy
I prodotti creati con il flag
license_key_enabled precedente sono stati migrati automaticamente a un entitlement License Key. La migrazione è trasparente: le chiavi dei clienti esistenti continuano a funzionare senza modifiche, gli endpoint pubblici /licenses/activate, /licenses/validate, /licenses/deactivate continuano a funzionare e gli endpoint API /license_keys/* continuano a leggere e scrivere nello stesso archivio di chiavi.La sezione autonoma License Keys della dashboard resta disponibile come elenco piatto di ogni chiave emessa, utile per audit e ricerche. La nuova configurazione (modifica dei limiti di attivazione, delle durate o delle istruzioni) deve essere eseguita modificando l’entitlement License Key migrato in Entitlements.Best practice
- Mantieni chiari i limiti di attivazione: scegli valori predefiniti appropriati (1 per le app per singolo utente, 3–5 per le licenze di team) e documentali.
- Fornisci istruzioni precise per l’attivazione: i clienti le copiano dalla loro email, quindi percorsi e comandi esatti riducono le richieste all’assistenza.
- Convalida le chiavi lato server: per i prodotti connessi alla rete, convalida tramite
/licenses/validateinvece di memorizzare localmente nella cache l’attivazione. - Usa i webhook per la revoca: ascolta
entitlement_grant.revokedper disabilitare immediatamente le funzionalità in-app quando un cliente annulla o richiede un rimborso. - Esegui test con sottoscrizioni e acquisti una tantum: il comportamento delle license key differisce leggermente tra i due casi, quindi testali entrambi prima di andare in produzione.