dodopayments/skills
Overview
This skill guides implementation of license key management with Dodo Payments, covering activation, validation, deactivation, and access control for software products. It explains dashboard setup, public and authenticated API usage, and integrations for desktop apps, CLIs, webhooks, and server-side validation. The content focuses on practical flows to gate features, limit activations, and link licenses to purchases or subscriptions.
How this skill works
License keys are unique tokens that authorize access, limit concurrent activations, and optionally expire. Public endpoints (no API key) let clients activate, deactivate, and validate keys; authenticated endpoints let your backend list and manage keys and activation instances. Use webhooks to persist created keys and monitor events, and perform server-side checks with an API key for sensitive operations and feature gating.
When to use it
- Gating premium features in desktop, web, or CLI products
- Enforcing per-seat or per-device activation limits
- Issuing keys automatically on purchase and emailing customers
- Validating access on the server for critical operations
- Allowing offline grace periods for desktop or CLI apps
Best practices
- Set sensible defaults for expiry and activation limits based on product and pricing
- Provide clear activation instructions and self-serve documentation to users
- Validate licenses server-side for any sensitive or premium endpoints
- Implement an offline grace period and fallbacks for transient connectivity
- Use webhooks to record license creation, detect abuse, and automate revocations
Example use cases
- Electron app: store activation instance locally, validate periodically, allow 30-day offline grace
- CLI tool: save license and machine id in config, require license before premium commands
- Server endpoint: verify license status and activations before granting API access
- Webhook handler: capture license_key.created to persist keys and email activation steps
- Feature gating: map license tiers to features and check tier membership via validated details
FAQ
Yes. Public endpoints (activate, deactivate, validate) require no API key and are safe for client use; reserve authenticated endpoints for server-side management.
How should I handle offline users?
Trust a recent successful activation locally with a defined grace period (for example 30 days), and re-validate when connectivity is restored.
7 skills
This skill helps you manage license keys for software products, validating, activating, and enforcing usage limits across devices.
This skill helps you implement usage-based billing with Dodo Payments, converting events into meters, products, and automated charges for precise usage.
This skill helps you integrate BillingSDK quickly by guiding you through React components, CLI setup, and Dodo Payments configuration.
This skill guides you through creating checkout sessions and overlay flows with Dodo Payments to streamline payments.
This skill helps you implement and manage subscription billing with Dodo Payments, including trials, plan changes, and on-demand usage.
This skill helps you integrate Dodo Payments for seamless payments, subscriptions, and billing across SaaS products with clear API usage.
This skill helps you implement and secure Dodo Payments webhooks in real time, including verification, idempotency, and event handling guidance.
