Source type

Lemon Squeezy Source Configuration

Lemon Squeezy sources receive order, subscription, license, and payment lifecycle events with x-signature verification.

LEMON_SQUEEZYPOST, PUT, PATCH, DELETEWebhook Signing SecretPayments

Lemon Squeezy webhooks documentation All source types

Lemon Squeezy configuration

Create a Lemon Squeezy source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each Lemon Squeezy delivery before it enters the routing workflow.

Source Type

LEMON_SQUEEZY

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Webhook Signing Secret

Lemon Squeezy source config

{
  "type": "LEMON_SQUEEZY",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "LEMON_SQUEEZY",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Lemon Squeezy request contract

FastHook computes HMAC-SHA256 hex over the raw body and compares it with x-signature.

POSTPUTPATCHDELETE

Lemon Squeezy headers

Preserve x-signature when sending Lemon Squeezy test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

x-signature

HMAC-SHA256 hex signature over the raw body.

Lemon Squeezy setup

Create a Lemon Squeezy webhook using the FastHook Source URL.
Paste the signing secret into FastHook.
Use event name and store id fields to route billing and license traffic.

Lemon Squeezy routing hints

Lemon Squeezy commerce events can separate orders, subscriptions, license keys, refunds, and payment failures into different fulfillment or customer-success routes.
Keep store, customer, order, and subscription identifiers with the event so billing changes can be reconciled without relying on email addresses alone.