Skip to content
Webhooks

Add events after the core wallet flow works.

Webhooks become relevant when your systems need to react to supported pass lifecycle events. They complement a working integration; they are not a first-run prerequisite.

A PassKit
pass.updated event sends a JSON payload to a customer webhook URL, which returns
200 OK.
Use webhooks when

A lifecycle event must trigger work elsewhere.

For example, use them when your CRM, commerce, ticketing or automation workflow needs to receive and process supported event information rather than waiting for a manual check or a synchronous request.

Core flow first

First prove you can create or manage the relevant wallet resource.

Event consumer

Decide which service receives, validates and owns event processing.

Source of truth

Keep the relationship between PassKit events and your customer or operational data explicit.

Operational design

Plan retries, monitoring and rollout before event handling becomes business-critical.

Workflow

Integrations.

Choose between a connector, automation or custom implementation.

Explore integrations
Getting help

Help Centre.

Use guided documentation when you need setup or troubleshooting support.

Open Help Centre
Choose your next action

New to PassKit or ready to build?

Create an account, then request credentials in Developer Tools. If you already have account credentials, continue with a QuickStart or the official Postman collection.