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 el campo
source en los registros de claves de licencia para distinguir el inventario migrado y las claves cumplimentadas manualmente de las claves emitidas de forma orgánica al conciliarlas o auditarlas. Léelo del objeto license_key en las concesiones devueltas por List Grants; el endpoint antiguo GET /license_keys está obsoleto.
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 clave de licencia nueva o importa una existente.
List License Keys
Explora todas las claves con detalles sobre su estado y uso.
Get License Key
Recupera una clave específica y sus metadatos.
Update License Key
Modifica la caducidad, los límites de activación o habilita/deshabilita una clave.
Entitlement Management
Entitlement Management
Administra el entitlement de License Key: su límite de activación, duración e instrucciones.
Create Entitlement
Crea un entitlement de License Key.
Update Entitlement
Actualiza la configuración del entitlement.
List Grants
Enumera las claves emitidas para un entitlement.
Revoke Grant
Revoca manualmente la clave de un cliente.
Webhooks
La entrega y revocación de claves de licencia activan los cuatroentitlement_grant.* eventos de webhook. El payload de la concesión incluye un objeto license_key completo con la clave, la caducidad, las activaciones utilizadas y el límite.
Los eventos antiguos de license_key.* (license_key.created) siguen activándose para el ciclo de vida del registro de claves de licencia subyacente; consulta la página del payload de webhook de License Key.
Claves de licencia heredadas
Los productos creados con el indicador antiguo
license_key_enabled se han migrado automáticamente a un entitlement de License Key. La migración es transparente: las claves de los clientes existentes siguen funcionando sin cambios, los endpoints públicos /licenses/activate, /licenses/validate y /licenses/deactivate siguen funcionando, y los endpoints de API /license_keys/* siguen leyendo y escribiendo en el mismo almacén de claves.La sección independiente de License Keys del dashboard sigue disponible como una lista plana de todas las claves emitidas, útil para auditorías y búsquedas. La nueva configuración (cambiar los límites de activación, las duraciones o las instrucciones) debe hacerse editando el entitlement de License Key migrado en Entitlements.Prácticas recomendadas
- Mantén claros los límites de activación: Elige valores predeterminados razonables (1 para aplicaciones de un solo usuario, 3–5 para licencias de equipo) y documéntalos.
- Proporciona instrucciones de activación precisas: Los clientes las copian de su correo electrónico, por lo que las rutas y los comandos exactos reducen las solicitudes de soporte.
- Valida las claves en el servidor: Para productos conectados a la red, valida mediante
/licenses/validateen lugar de almacenar la activación localmente en caché. - Usa webhooks para la revocación: Escucha
entitlement_grant.revokedpara deshabilitar inmediatamente las funciones de la aplicación cuando un cliente cancela o solicita un reembolso. - Prueba con suscripciones y pagos únicos: El comportamiento de las claves de licencia difiere ligeramente entre ambos, así que prueba los dos casos antes de pasar a producción.