Skip to main content
POST
Create Webhook
POST /v1/webhooks
v1.0 schema lock. The response shape on this page, the webhook envelope, the per-event data payload, and the HMAC signature algorithm are all part of the locked v1.0 contract. We will never remove a documented field, never rename a field, and never change a field’s type without bumping to v2 (see Versioning). New event types may be added additively; your receiver must tolerate unknown event types and unknown keys.
Register a webhook endpoint to receive real-time event notifications via HTTP POST. Each delivery includes an X-Autosnap-Signature header for verification. Failed deliveries are retried with exponential backoff.

Request Body

Event Types

All event names use period as the segment separator: <scope>.<event> or <scope>.<subscope>.<event>. Underscores appear only inside multi-word event names (e.g. dealer.config.auto_updated).

Website Inventory Events

IMS Feed Events

Dealer Health Check Events

You can subscribe to one or more event types per webhook.

Example

Response

The API creates one webhook record per event type. If you subscribe to 6 event types, the created array will have 6 entries, each with its own webhook_id.

Signature Verification

Every webhook delivery includes an X-Autosnap-Signature header. Verify it by computing an HMAC-SHA256 of the raw request body using the secret you provided:

Error Codes

See Handling Webhooks for a full end-to-end integration guide.

Body

application/json
api_key
string
required
url
string
required
event_types
string[]
required
secret
string
required
dealership_id
integer | null
max_failures
integer | null
default:10

Response

Successful Response