What are DataDoe Webhooks?

DataDoe Webhooks let your systems receive HTTPS callbacks when selected events happen for your Sellers and Vendors. Instead of polling DataDoe or the Selling Partner API (SP API) for changes, DataDoe POSTs a JSON payload to an endpoint you control as soon as matching events are ready.

Use Webhooks to trigger automations, sync Amazon events into your enterprise resource planning (ERP) or warehouse management system (WMS), or wake up downstream jobs when new notification data becomes available.

How do I set up a webhook?

1. Open Integrations > Webhooks (opens in a new tab) in DataDoe.
2. Click New webhook and fill in:
   • Name — a label you recognize later
   • Target URL — your HTTPS endpoint that accepts POST requests
   • Message types — which events to subscribe to
   • Sellers and Vendors — which DataDoe accounts should be included
   • Secret header (optional) — a custom header name and value DataDoe sends on every delivery so you can verify requests
3. Save the subscription. It starts in the Active state.

You can create multiple subscriptions per Organization, for example one endpoint for your ERP and another for an internal queue. When a single event matches more than one active subscription, DataDoe delivers it to each matching subscription separately.

What do webhook deliveries cost?

Each delivered message costs 0.05 AI Tokens and can pause the subscription if the AI Token balance runs out. See Subscription and pricing.

High-volume message types can deliver many events. The catalog marks those types as high volume. The token cost applies to every message type.

How to secure my webhooks?

A secret HTTP header helps your endpoint reject forged webhook requests. In Integrations > Webhooks (opens in a new tab), set a header name and a long, random value when you create or edit a webhook. Store the value securely on your server. Compare the incoming header with the stored value before processing the payload, and reject requests if the header is missing or incorrect.

Which message types are available?

What does DataDoe send to my endpoint?

DataDoe sends an HTTPS POST with Content-Type: application/json. The body has this shape:

1{
2    "deliveryId": "550e8400-e29b-41d4-a716-446655440000",
3    "organizationId": "11111111-1111-4111-8111-111111111111",
4    "webhookId": "33333333-3333-4333-8333-333333333333",
5    "messages": [
6        {
7            "organizationId": "11111111-1111-4111-8111-111111111111",
8            "sellerOrVendorId": "22222222-2222-4222-8222-222222222222",
9            "messageId": "44444444-4444-4444-8444-444444444444",
10            "messageType": "AMAZON_ORDER_UPDATE",
11            "messageSummary": {},
12            "messageData": {}
13        }
14    ]
15}

Each body field is described below:

Detailed webhook message schemas are in the interactive Webhooks Messages Schemas page.

The 16 SP-API notification message types share a stable contract. Their messageSummary always includes marketplaceId, sellerOrVendorId, spApiNotificationId, spApiNotificationType, and eventTimeUtc. It can also include marketplaceCountryCode, marketplaceCountryName, sellerOrVendorName, and marketplaceSellerId. Their messageData includes the Amazon notificationMetadata and the payload routed to the selected Seller or Vendor connection. The two order message types retain their order-specific schemas.

How do I subscribe to shipment tracking updates?

DataDoe does not subscribe to shipment tracking automatically. Before you can receive AMAZON_SHIPMENT_TRACKING_MILESTONE_CHANGED events, start an AMAZON_SHIPMENT_TRACKING_SUBSCRIBE Action for each tracking identifier. This Action is available to Sellers and Vendors on the US Tracking API only.

In MCP, use actions_details_schema_get to load the Action details, then call actions_start. Each entry in trackingIdentifiers must contain exactly one identifier field. For example:

1{
2    "type": "AMAZON_SHIPMENT_TRACKING_SUBSCRIBE",
3    "sellerOrVendorId": "YOUR_SELLER_OR_VENDOR_ID",
4    "details": {
5        "trackingIdentifiers": [
6            {
7                "carrierTracking": {
8                    "trackingNumber": "YOUR_TRACKING_NUMBER"
9                }
10            }
11        ]
12    }
13}

After Amazon accepts the subscription, create a DataDoe webhook and select AMAZON_SHIPMENT_TRACKING_MILESTONE_CHANGED as a message type. See Actions for the full Action workflow and the REST API option.

If you configured a secret header, DataDoe includes it on every request using the header name you chose.

What should my endpoint return?

Return any 2xx HTTP status to acknowledge successful processing. Non-2xx responses or network errors are treated as delivery failures.

What happens when a delivery fails?

If your endpoint returns a non-2xx status or the request cannot be completed, DataDoe:

1. Pauses the subscription automatically.
2. Emails Organization members.

After you fix the endpoint, open Integrations > Webhooks (opens in a new tab) and select Resume.

If you believe an invalid delivery is an error on DataDoe's side, please use the contact form (opens in a new tab).

What are the target URL requirements?

Target URLs must:

• use HTTPS
• use a domain name (not a raw IP address)
• not use localhost or *.localhost
• accept POST requests

How is this related to real-time data?

Webhooks complement DataDoe's scheduled and real-time data pipelines described in Data Fetch Periods. Webhooks are the recommended way to get real-time data updates.

Where can I get help?

Use the contact form (opens in a new tab).