How do I send Whatnot order webhooks to Slashbin?
Time: ~10 minutes | Difficulty: Beginner | Prerequisites: A Whatnot seller account with access to Seller Hub and its Seller API, an app that has the read:orders scope, and a Slashbin account
TL;DR: Whatnot sets up webhook subscriptions per client app, from your developer dashboard, and order events need the read:orders scope. Create a Whatnot data stream in Slashbin, add a webhook in Seller Hub pointing at its receiver URL, paste the wn_wh_ secret back into Slashbin, and watch the first order arrive in the Delivery Log.
The Problem
Whatnot’s webhook setup has three quiet traps, and each one fails without an error you can see:
- Subscriptions belong to a client app. Whatnot’s documentation says webhook subscriptions are configured per client app from your developer dashboard, and there is no REST endpoint for managing them today. If you cannot find the setting, you are probably looking in the wrong app. (Whatnot webhooks guide )
- Order events need
read:orders. Whatnot’sorders.createdreference says it requiresread:orders. An app without that scope never receives the events. (orders.created reference ) - Two secrets look alike. The webhook secret starts with
wn_wh_. A personal access token starts withwn_pat_tk_and is never the right value here.
The Solution
Point Whatnot at a Slashbin data stream. Slashbin verifies each webhook, stores the raw payload, and delivers it to your destination with retries and replay. Your part is the four steps below, once.
Read Golden Model for the canonical schema you keep, and Third-Party Model for the shape a destination expects.
Step 1: Create a Whatnot Data Stream in Slashbin
- In the Slashbin console, click Create New Data Stream and select Whatnot.
- Copy the stream’s receiver URL. The console shows the exact URL for your stream, so copy it from there rather than typing it.
Step 2: Add a Webhook in Whatnot Seller Hub
- In Whatnot Seller Hub, open Seller API.
- On the Webhooks tab, add a webhook pointing at the receiver URL from Step 1.
- Choose the order topics:
orders.createdandorders.updated.
Check the scope first. Order topics need read:orders. If your app does not have it, the webhook saves but no order events arrive.
Step 3: Rotate and Paste the Webhook Secret
- On the Settings tab, click Rotate Secret.
- Copy the new secret. It starts with
wn_wh_. - Paste it into your Whatnot data stream in Slashbin.
Rotating stops the old secret at once. Anything else still using the previous secret fails verification as soon as you rotate. Do not paste a personal access token (wn_pat_tk_): it is a different credential, and webhooks will fail verification until the wn_wh_ secret is in place.
Step 4: Confirm the First Event in the Delivery Log
Open your Whatnot stream in Slashbin and check the Delivery Log:
- A verified order event means the URL and secret match on both sides. You are done.
- A signature failure almost always means the pasted value is not the
wn_wh_secret, most often awn_pat_tk_token. Rotate the secret again and paste it fresh. - Nothing at all means no event has reached the URL. Check that the URL is copied exactly, that the order topics are selected, and that your app has
read:orders.
What an Order Event Contains
- An order summary, not the items bought. You get amounts, status, transaction type, the show, timestamps and a URL for the order. Line items are not in the webhook.
- The buyer is empty unless Whatnot approves customer data. Buyer fields arrive as
nulluntil Whatnot approves your app for customer data. - Order matters less than you think. An
orders.updatedevent can arrive before the matchingorders.created, so do not assume a creation event always comes first.
Why Slashbin vs a Raw Handler
- No signature code to write. Slashbin verifies each webhook at the gateway, before anything reaches your systems.
- Every event is kept. The raw payload is stored as Whatnot sent it, so “did Whatnot tell us about this order?” is one look at the Delivery Log.
- Out-of-order events are visible. Both topics land in the same log, so an early update is easy to spot and replay.
- Nothing is a silent drop. If your destination is down, Slashbin retries with backoff and replays on your schedule.
Next Steps
- Connect a provider that has no recipe yet: How do I receive webhooks from any provider?.
- Send one event to more than one system: see Fan-Out Routing.
- Browse every supported source and destination on Integrations.