Webhooks: what Shakewell sends and receives

The Shakewell Wallet API does not yet push webhooks to your endpoint. See how to track installs by polling, and how inbound integration webhooks are verified.

Last updated 2026-11-05

Outbound webhooks to your own endpoint are not available yet, so there are no event types, signatures or retry schedule to document. We would rather say that than describe something that does not exist.

Track installs without webhooks

Poll GET /wallet-passes/{passId} and read is_installed and installed_at. For many passes, list with GET /wallet-passes?template_id=... and compare. Keep polling modest: the API allows 60 requests a minute per IP address (see rate limits).

Inbound webhooks from connected platforms

Integrations such as Shopify and point-of-sale systems call Shakewell at POST /api/v2/integrations/{slug}/webhooks/{topic}. Each integration verifies the vendor's own signature (for example an HMAC header) before anything is processed.

An unknown slug returns 404 with an empty body.
A request that fails verification returns 401 with an empty body.
A verified request is acknowledged with 2xx, including when the event is skipped, so the vendor does not retry needlessly.

These endpoints are for the connected platforms, not for your own code.

Need event delivery for your build? Email support@shakewellwallet.com with the events you need.