License API

A Lemon Squeezy License API alternative your app already speaks

Same activate, validate and deactivate endpoints, same params, same JSON and error messages. Change the base URL in your next release and keep selling on Stripe.

Endpoints

Drop-in compatible

Form-encoded or JSON bodies, the same status codes (404 for an unknown key, 422 for a missing field, 400 at the activation limit) and the same error strings.

EndpointParamsWhat it does
POST /v1/licenses/activatelicense_key, instance_nameCreates an activation and returns instance.id. Enforces the activation limit atomically.
POST /v1/licenses/validatelicense_key, instance_id (optional)Returns valid, license_key, instance and meta, like Lemon Squeezy.
POST /v1/licenses/deactivatelicense_key, instance_idFrees the seat. Customers can also do it themselves in the portal.
The change in your app

One URL

No SDK to adopt. Public endpoints with open CORS, so desktop apps, plugins and extensions can call them directly without shipping a secret key.

// before
POST https://api.lemonsqueezy.com/v1/licenses/validate
// after: same body, same response
POST https://rindkey.com/v1/licenses/validate
✓ { "valid": true, "license_key": {…}, "instance": {…} }
Beyond compatibility

What you get on top

  • Existing activations keep working. The import keeps the original Lemon Squeezy instance IDs your app stored.
  • Offline grace. Validate and activate can return an Ed25519-signed token (1 to 30 days) your app checks locally when it's offline. See the docs.
  • Keys issued on Stripe sales. Checkout, Payment Links and Stripe Managed Payments, with refunds and cancellations revoking access.
  • A customer portal for keys, seat resets and signed file downloads.

Rindkey isn't affiliated with Lemon Squeezy. "Compatible" means the License API endpoints above, not the rest of the Lemon Squeezy API.

See what your store needs before you move

The readiness check is free and read-only. Your Lemon Squeezy API key is used in memory for one request and never stored.