Skip to content
REST and Postman

Inspect a request before you build it into an application.

REST is a valid request-first route when it fits your tools or workflow. The official Postman collection is the quickest way to copy an environment, use your account credentials and inspect request and response behaviour.

Explore with Postman Open Developer Tools View API Reference
PassKit Postman collection showing expanded request groups and getting-started guidance
Before your first request

Set up the account, credentials and API settings.

You need a PassKit account before credentials are available. In Developer Tools, request the account credentials and find the account-specific API region or host.

1. Account

Create or sign in to the account that owns the implementation.

2. Credentials

Request your developer credentials in the PassKit Portal and receive them securely at your registered email address.

3. Postman settings

Create a Postman environment with the right account API settings.

4. Validate

Send one documented request, inspect the response, then move the proven flow into code.

Read the Postman guide
After the request works

Use the API contract and choose the implementation depth deliberately.

Use the API Reference for the exact endpoint and payload. Move to an SDK or gRPC if that is the better fit for your service; add webhooks only when another system needs to react to lifecycle events.

SDKs

Use a supported client library.

Move a proven flow into your own service.

Explore SDKs
Events

Add webhooks when needed.

React to lifecycle events after the core flow is working.

When to use webhooks
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.

Create an account Open Developer Tools Browse QuickStarts Explore with Postman