Help › Keys, CLI and automation

Keys, CLI and automation

Licence keys, API keys, the command line and webhooks.

• Licence keys

  What a licence key is, how it ties a WordPress site to your plan, how to replace it, and what happens offline.

• API keys

  Site keys and secret keys, what each is for, scopes, rotation, and how to keep a secret key out of the wrong place.

• The command-line tool

  Use the rl command to push text, translate, publish, pull and export from a terminal or a build job.

• Webhooks and the audit log

  Get a signed message on your server when a site is published, a job fails or your allowance is reached, and review who did what.

• Webhook events reference

  Every event you can receive, when it fires, and what its data holds. Payloads never contain text or secrets.

• Run translations from CI

  Push new text, translate and publish from GitHub Actions, GitLab CI or Bitbucket Pipelines, with a safe dry run on pull requests.

• Catch untranslatable text before you commit

  A lint tool that warns about text the translator cannot reach, such as text built in code or words split by markup.

• Check your setup with rl doctor

  A read-only command that checks your key, address, site, plan and published files, and explains each failure in plain words.