Sell license key access to your service, software or APIs with ease
You can easily sell software license keys with Polar without having to deal with sales tax or hosting an API to validate them in real-time. License keys with Polar come with a lot of powerful features built-in.
POLAR_*****
N
days, months or yearsBenefits
in the sidebar+ New Benefit
to create a new benefitLicense Keys
as the Type
Make your license keys standout with brandable prefixes, e.g MYAPP_<AUTO_GENERATED_UUID4>
Want license keys to expire automatically after a certain time period from when the customer bought them? No problem.
You can require license keys to be activated before future validation. A great feature in case you want to limit license key usage to a certain number of devices, IPs or other conditions.
Enable user to deactivate instances via Polar. Instead of building your own custom admin for customers to manage their activation instances - leave it to Polar instead.
Offering OpenAI tokens or anything else with a variable usage cost? You can set a custom usage quota per license key and increment usage upon validation.
Once customers buy your product or subscribes to your tier, they will automatically receive a unique license key. It’s easily accessible to them under their purchases page.
Customers can:
It’s super easy and straightforward to integrate Polar license keys into your application, library or API.
In case you’ve setup license keys to have a maximum amount of activation instances, e.g user devices. You’ll then need to create an activation instance prior to validating license keys / activation.
No activation limit? You can skip this step.
Replace with the users license key (from input in your app).
Replace with your organization ID here found in your settings.
Set a label to associate with this specific activation.
JSON object with custom conditions to validate against in the future, e.g IP, mac address, major version etc.
JSON object with metadata to store for the users activation.
For each session of your premium app, library or API, we recommend you validate the users license key via the
/v1/customer-portal/license-keys/validate
endpoint.
Replace with the users license key (from input in your app).
Replace with your organization ID here found in your settings.
The activation ID to validate - required in case activations limit is enabled and used (above).
In case of activation instances. Same exact JSON object as upon registration of the activation.
In case you want to increment usage upon validation.
Validate benefit_id
in case of multiple license keys
We require organization_id
to be provided to avoid cases of Polar license keys being used across Polar organizations erroneously. Otherwise, a valid license key for one organization could be used on another.However, you are required to validate and scope license keys more narrowly within your organization if necessary. Offering more than one type of license key? Be sure to validate their unique benefit_id in the responses.