Skip to main content
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
Inside Dodo Payments, license keys are managed through the Entitlements system, meaning the lifecycle of every key (creation, expiry, revocation, regrant) is driven by the same payment and subscription events as your other deliverables.

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., 1 for single-user, 5 for 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 → License or Run: mycli activate <key>.
New License Key entitlement form with name, fulfillment mode, license length, activations limit, and activation message
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.
Product entitlements panel with License Key selected

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 a fulfillment_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 when fulfillment_mode is omitted.
  • manual: The purchase creates a Pending grant 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 a Pending 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

Set fulfillment_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 in Pending 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 to Delivered 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.
License keys created or updated through the API do not trigger email notifications to customers. If you need to notify customers about an imported key, handle that separately in your application.

How keys differ by source

Använd fältet source i licensnyckelposter för att skilja migrerat lager och manuellt uppfyllda nycklar från organiskt utfärdade nycklar vid avstämning eller granskning. Läs det från objektet license_key i tilldelningar som returneras av List Grants; den äldre slutpunkten GET /license_keys är föråldrad.
Migrating from Polar.sh or Lemon Squeezy? The dodo-migrate CLI automates bulk imports of products, customers, discounts, and license keys in a single command and maps external IDs to Dodo IDs automatically.

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 your return_url as a query parameter. This lets you display the key immediately on your success page without making an extra API call.
If the purchase generates multiple keys (quantity > 1), they are comma-separated:
For subscriptions, subscription_id is used instead of payment_id:
Parse the license_key parameter on your return page to show the key immediately, improving the post-purchase experience.

API Management

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.
Create, list, retrieve, and update individual license key records. Use these to import existing keys or fetch usage details.
GET /license_keys, GET /license_keys/{id} och PATCH /license_keys/{id} är föråldrade. Använd slutpunkterna för rättighetstilldelningar (List Grants, List Customer Grants) för läsning. POST /license_keys stöds fortfarande för import av befintliga nycklar.

Create License Key

Skapa en ny licensnyckel eller importera en befintlig.

List License Keys

Bläddra bland alla nycklar med information om status och användning.

Get License Key

Hämta en specifik nyckel och dess metadata.

Update License Key

Ändra utgångsdatum, aktiveringsgränser eller aktivera/inaktivera en nyckel.
Hantera själva rättigheten för licensnyckeln: dess aktiveringsgräns, varaktighet och instruktioner.

Create Entitlement

Skapa en rättighet för en licensnyckel.

Update Entitlement

Uppdatera rättighetens konfiguration.

List Grants

Visa nycklarna som utfärdats för en rättighet.

Revoke Grant

Återkalla en kunds nyckel manuellt.

Webhooks

Leverans och återkallelse av licensnycklar utlöser de fyra entitlement_grant.* webhook-händelserna. Tilldelningspayloaden innehåller ett ifyllt objekt license_key med nyckeln, utgångsdatumet, använda aktiveringar och gränsen. De äldre händelserna license_key.* (license_key.created) fortsätter att utlösas för livscykeln för den underliggande licensnyckelposten. Se sidan Webhook-payload för licensnyckel.
För nya integrationer ska du lyssna på entitlement_grant.delivered i stället för license_key.created. Rättighetshändelsen visar att leveransen är slutförd för alla integrationer på produkten, inte bara för licensnyckeln.

Äldre licensnycklar

Produkter som skapats med den äldre flaggan license_key_enabled har migrerats automatiskt till en rättighet för en licensnyckel. Migreringen är transparent: befintliga kunders nycklar fortsätter att fungera oförändrat, de offentliga slutpunkterna /licenses/activate, /licenses/validate och /licenses/deactivate fortsätter att fungera, och API-slutpunkterna /license_keys/* fortsätter att läsa från och skriva till samma nyckellager.Det fristående dashboard-avsnittet Licensnycklar finns fortfarande kvar som en platt lista över alla utfärdade nycklar och är användbart för granskning och sökning. Ny konfiguration (ändring av aktiveringsgränser, varaktigheter eller instruktioner) bör göras genom att redigera den migrerade rättigheten för licensnyckeln under Rättigheter.

Bästa praxis

  • Håll aktiveringsgränserna tydliga: Välj rimliga standardvärden (1 för appar för enskilda användare, 3–5 för teamlicenser) och dokumentera dem.
  • Ge exakta aktiveringsinstruktioner: Kunder klistrar in dessa från sitt e-postmeddelande, så exakta sökvägar och kommandon minskar antalet supportärenden.
  • Validera nycklar på serversidan: För nätverksanslutna produkter ska du validera via /licenses/validate i stället för att cacha aktiveringen lokalt.
  • Använd webhooks för återkallelse: Lyssna på entitlement_grant.revoked för att omedelbart inaktivera funktioner i appen när en kund avslutar eller återbetalas.
  • Testa med prenumerationer och engångsbetalningar: Licensnycklarnas beteende skiljer sig subtilt mellan dessa, så testa båda innan du går live.
Senast ändrad 21 augusti 2026