Skip to main content

Overview

SellAuth allows you to receive shop notifications via an HTTP webhook. These notifications inform you about important events such as invoices, stock changes, feedback, tickets, and system errors. HTTP notifications are designed to be lightweight: only minimal data (usually IDs) is sent. You are expected to fetch full details using the SellAuth API.

How It Works

  1. An event occurs on your shop.
  2. SellAuth sends a POST request to your configured webhook URL.
  3. Your server validates the request signature.
  4. You use the provided IDs to fetch full data via the API.
Each notification is sent as a single request per event.

Webhook Request

HTTP Details

  • Method: POST
  • Content-Type: application/json
  • Connect timeout: 5 seconds
  • Request timeout: 10 seconds
  • Retries: 3 total attempts
  • Retry interval: 5 seconds between each attempt
  • Redirects: not followed. A 3xx response is treated as a failed delivery.

Example Request Body

The data object usually contains only IDs relevant to the event.

Signature Verification

HTTP notifications use the same headers and signature logic as Dynamic Delivery webhooks.

Headers

Webhook Secret

The webhook secret is listed per shop under Developers > Overview: dash.sellauth.com/api. If the secret is not visible, click Regenerate to create one.

Signature Logic

Fetching Full Data

Because notifications only contain IDs, you must retrieve the full data using the SellAuth API.

Example

If you receive:
You can fetch the invoice details using the Get Invoice endpoint.
This design keeps notifications fast and reliable while giving you full control over what data you load.

Event Types

Below is a list of all HTTP notification events and their payload structure.

Invoice Events

SHOP_INVOICE_LATE_PAYMENT fires when a payment provider confirms money for an invoice that no longer accepts it. reason is closed (the invoice expired, was cancelled or failed), switched (the buyer moved to another payment method) or duplicate (the invoice was already paid). The payment is not credited and nothing is delivered until you resolve it from the dashboard or with the Resolve Late Payment endpoint.

Product & Stock Events

Feedback Events

Dispute Events

Sent on the Scale plan only. See Disputes for what each stage, status and reason value means. OPENED is sent each time a dispute needs a response, so a dispute that reaches pre-arbitration sends it again with a new stage and evidence_due_at. evidence_due_at is an ISO 8601 timestamp, or null when the processor gives no deadline. Fetch the full dispute with the Get Dispute endpoint.

Ticket Events

Subscription Events

System Events

Error Handling

If your webhook fails, times out, or returns a non-200 status:
  • The notification will be retried automatically
  • Delivery errors may appear in your shop dashboard
  • Additional notification channels will be used if configured
Your webhook must return HTTP 200 to acknowledge successful receipt.