Help › Keys, CLI and automation
Licence keys
A licence key links one WordPress site to your plan. It looks like rl_lic_live_.... You enter it in the licensed build of the plugin.
A licence key is not an API key. A secret API key (rl_sec_...) is for servers and tools. A site key (rl_site_...) is public. See API keys.
How it works#
- The key belongs to your account and your plan.
- You activate it on each site by its domain name. The plan sets how many sites can be active at once.
- Development sites are marked and do not use a slot.
- The plugin receives a signed licence token. It checks the token itself, so it keeps working if it cannot reach us.
- Activation can be undone, which frees the slot.
See your licence#
Open Licence in the dashboard. Every member can see the plan, the state (active, grace, lapsed, revoked or free), the paid-until date and grace days, a booked downgrade, the limits for sites, languages and AI words, the start of the current key only, and a table of activated sites.
Create a new key#
Only the account owner can. Choose Create a new licence key.
- The new key is shown once, on the page that creates it. Copy it then. Reloading the page shows only the start of the key.
- The old key keeps working for new activations for 60 minutes. Sites that are already active stay active.
- You can create at most 5 keys per hour.
- Refreshing or double-clicking the button does not create a second key.
If the page says "No active plan", you have no paid plan to attach a key to. If licence management is not set up in your environment, the page says it is not available.
When a licence lapses#
Your translations keep working. New work is blocked and plugin updates stop. See Cancel, lapse and grace.
Keep it private#
Do not send a licence key in an email or a support ticket. Our support never needs it.
Builds#
There are planned to be two plugin builds: one for WordPress.org without licensing, and a licensed one. Whether WordPress.org accepts a plugin that needs a paid service is OPEN.