Lemon Squeezy integration
Credentials, webhook verification and supported setup for Lemon Squeezy.
On this page
1. Open the connection
Choose the correct site, open Integrations, find Lemon Squeezy and choose Connect. Site administrator access is required. Use your provider's dashboard to obtain the fields below; never place these secrets in public website code.
2. Configure credentials
| Setting | Value / behavior |
|---|---|
| Provider ID | lemonsqueezy |
| API credential input | API key (Settings → API) |
| Webhook signing secret | The secret you set on the webhook |
| Automatic webhook registration | Supported |
| History synchronization | Supported through Sync |
| Verification | Provider-specific signature / token verification |
| Signing secret required | Yes |
Test-mode keys are detected automatically. Weeveo adds a webhook to each of your stores.
3. Set up the webhook
Use Weeveo's automatic registration with a valid provider credential. It registers the callback and stores returned signing material. Check the resulting delivery status after setup.
The callback format is https://weeveo.com/api/v1/webhooks/lemonsqueezy?projectId=YOUR_PROJECT_UUID. Use your actual generated URL, including its site ID. The registered event list for this provider is:
- order_created
- order_refunded
- subscription_created
- subscription_payment_success
- subscription_payment_recovered
- subscription_payment_refunded
4. Test and review
Complete a provider-supported test payment with matching test/live credentials. Inspect sanitized webhook status and the Revenue report for the selected site, dates and currency. A verified connection is not evidence that a payment event has arrived. Use Sync to import bounded recent history, then review any sync errors.
5. Link permitted visits
To attribute a payment, use supported checkout context from an opted-in persistent visitor. The browser SDK exposes getSession().visitorId when available; it does not expose an SDK sessionId. Provider metadata mappings differ. Review the identity guide and confirm the resulting journey.
Troubleshooting
Check the callback's project ID, webhook delivery status, exact verification secret, provider environment and site reporting window. API-verified providers also need reachable provider APIs and a valid stored credential. Do not weaken signature validation to force ingestion. Rotate compromised credentials at the provider and update the connection.
Related references
See integration setup, connect_integration, list_webhook_events, revenue reporting and the provider directory.
Still looking for an answer? Try troubleshooting or get in touch.