receive bidjs webhook events for auction status, item status, and registration changes via svix
domain: docs.bidjs.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Svix account and generate a Svix API Access Key (shown only once at creation).
Use the Svix API key to create a Consumer App (POST https://api.eu.svix.com/api/v1/app/), then supply the resulting Consumer App ID and API key to BidJS support to link it.
Define eventType schemas (e.g. AUCTION_STATUS_CHANGE, ITEM_STATUS_CHANGE, REGISTRATION) via the Svix event-type API or dashboard.
Add an endpoint URL in the Svix Consumer App portal and select which eventTypes should be delivered to it.
Verify incoming payloads match the documented schema (e.g. auctionUuid, auctioneerUuid, status for AUCTION_STATUS_CHANGE) before processing.
Known gotchas
BidJS webhooks are delivered through a third-party provider (Svix), not a native BidJS endpoint - you must provision and manage a Svix account separately.
The Svix API key is displayed only once at generation time; losing it means regenerating and re-linking your Consumer App with BidJS support.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?