Docs

Webhooks ​

A webhook sends selected KPIs from sellerfox as JSON to a public HTTPS address once a day. Use Automations → Webhooks to create, test, and monitor your webhooks. See the Webhook API for the receiver's technical requirements.

Access and allowance

Only Owners and Admins can view or manage webhooks.

You can create a webhook when:

  • the workspace has completed onboarding,
  • the workspace has an active trial or subscription, and
  • at least one webhook slot is available.

Above the list, you can see how many slots are in use. If no slot is available, delete a webhook you no longer need. See the permissions matrix.

What a webhook can monitor ​

For each webhook, you choose one category and between one and 20 compatible KPIs.

CategoryData
“All workspace data”Combined KPIs from all marketplaces in the workspace.
“Marketplace”KPIs for one marketplace.
“Parent ASIN”KPIs for one parent ASIN and its child ASINs on one marketplace.
“Child ASIN”KPIs for one child ASIN on one marketplace.
“Product List”Combined KPIs for one product list.
“Keyword”Ranking KPIs for one keyword label on one marketplace.

You cannot change the category after creating the webhook. Create a new webhook to use a different category.

Create and test a webhook ​

  1. 1

    Open the form

    Open Automations → Webhooks → Create Webhook. On an empty Webhooks page, the button is “Create Your First Webhook”.

  2. 2

    Choose the target

    Under “What do you want to monitor?”, choose a category. Then choose a target if one is displayed.

  3. 3

    Choose KPIs

    Select between one and 20 compatible KPIs.

  4. 4

    Configure the endpoint

    Enter a public HTTPS address with a domain name under “Webhook URL”. Under “Authentication”, choose “None”, “Bearer Token”, or “Basic Auth”. Enter the credentials when required.

  5. 5

    Name the webhook

    Enter a name of at most 100 characters under “Webhook Details”.

  6. 6

    Test and create

    Select “Test Connection”. When the endpoint returns the expected response, select “Create Webhook”.

The test view shows the request, response, status code, and response time. A test uses current data. Its data array may be empty. The view displays at most the first 5,000 characters of the response.

Configure the receiver and authentication ​

Use a public HTTPS URL with a domain name. Local and internal addresses and IP addresses are not supported. Use “Test Connection” to check whether your endpoint responds.

Choose “Bearer Token” or “Basic Auth” if your endpoint expects credentials. Otherwise, choose “None”.

See the Webhook API for requirements covering headers, payloads, timeouts, and size limits.

Manage webhooks ​

Above the list, show all webhooks or filter by “Active”, “Paused”, “Failed”, or “Disabled”. Each filter shows the number of matching webhooks. These filters describe the webhook; check individual delivery statuses in the delivery history.

A webhook's three-dot menu contains “Pause”, “Resume”, “Test Webhook”, “View History”, “Edit Settings”, and “delete”.

You can change the name, URL, authentication, and KPIs. For “Marketplace”, “Parent ASIN”, “Child ASIN”, “Product List”, and “Keyword”, you can also change the target.

If the selected ASIN, keyword, or product list no longer exists, sellerfox shows “Missing target”. Open “Edit Settings” and choose another ASIN, keyword, or product list in the same category.

When you deactivate a marketplace in the workspace, the webhook's category determines what happens:

  • “Marketplace”, “Parent ASIN”, “Child ASIN”, or “Keyword”: If the selected target belongs to that marketplace, the webhook is deleted. Recreate the webhook if needed after reactivating the marketplace.
  • “Product List”: The webhook and the product list remain in place, even if the list contains products from the deactivated marketplace.

See Deactivate and reactivate a marketplace.

Monitor deliveries ​

Select “View History” from the three-dot menu. “Webhook Delivery History” loads more entries as you scroll. Each row shows the status, time, HTTP status, response duration, and attempt count. Select “Details” to expand the “Delivery ID” and any error message. You can copy the delivery ID.

You can filter by “Delivered”, “Failed”, or “Pending”. This status belongs to the delivery, not the webhook. An “Active” webhook can therefore have a “Pending” delivery.

Use the status filters to find failures and pending retries.

Retries and disabling ​

sellerfox sends the webhook once a day. Each delivery contains data for the 31 days ending yesterday. If an attempt fails, sellerfox tries the delivery up to two more times. A failed delivery can be sent again during the next hourly check. Wait a few hours before treating it as lost. After ten failed attempts in a row, sellerfox disables the webhook.

StatusWhat to do
“Active”No action unless history shows failures.
“Paused”Select “Resume” when delivery should continue.
“Disabled”Fix the endpoint, then delete the configuration and create a replacement. A successful test does not reactivate the webhook.

Delivered entries disappear from the history after 30 days. This period does not apply to Pending and Failed entries. Do not use the history as an archive.