Skip to main content
Site Store Pro exposes webhook endpoints for external integrations. All webhook routes are CSRF-exempt — they do not require a CSRF token and can be called directly from external services.

Overview


Inventory Update Webhook

Endpoint: POST /webhooks/inventory-update Allows external warehouse management systems (WMS), ERP platforms, or custom scripts to push inventory level updates to Site Store Pro without requiring an admin login.

Authentication

The webhook verifies the request using a shared secret. Include your secret using any one of the following methods:

Setting Your Secret

Add your chosen secret to .env:
Requests with a missing or invalid secret are rejected with a 401 Unauthorized response. Set a long, randomly generated string as your secret.

Request Payload

All fields except sku are optional. Any field that is omitted is left unchanged — only explicitly provided fields are updated.

Response

A successful update returns a 200 OK response with a JSON body containing the updated inventory record and the new calculated total stock.

Inbound Email Webhook

Endpoint: POST /webhooks/inbound-email Enables customers and staff to reply to support tickets by simply replying to a notification email — without logging into the dashboard.

How It Works

Every ticket notification email is sent with a unique reply-to address:
When a recipient replies, the email provider routes the message to this webhook. Site Store Pro then:
  1. Extracts the {token} from the recipient address
  2. Verifies the token against the tickets table
  3. Appends the email body as a new reply on the matched ticket thread

Supported Email Providers

Cloudflare Email Workers

Configure Cloudflare Email Routing rules to forward reply+*@yourdomain.com addresses to your webhook endpoint via an Email Worker.

Mailgun

Set up a Mailgun inbound routing rule to POST the parsed email payload to https://yourdomain.com/webhooks/inbound-email.

Postmark

Use Postmark’s inbound email processing to forward structured JSON email payloads to your webhook endpoint.
Add a DNS catch-all or wildcard MX record for reply+*@yourdomain.com so all tokenized reply addresses are routed to your configured email provider.

Stripe Webhook

Endpoint: POST /webhooks/stripe Handles Stripe payment events including successful charges, failed payments, refunds, and subscription updates. See the Stripe payment processor documentation for webhook registration instructions and a full list of handled events.

Paddle Webhook

Endpoint: POST /webhooks/paddle Handles Paddle payment events for order fulfillment and subscription management. See the Paddle payment processor documentation for webhook registration instructions and event handling details.