For the latest version of this document go to the Developer Hub
We're thrilled to have you start using the Badge API! Follow hese simple steps to get started:
Step 1: Log In to Your Badge Workspace
The Workspace is the user interface for managing all things Badge. If you don't have a Workspace or are not sure if you have access, contact your Account Manager to receive an email invite.
Step 2: Set Up Your API Key
Once you're logged in to a Workspace
Navigate to Settings > API Management.
Create an API key—this key can be used with Bearer authentication.
Step 3: Create a Pass Template
A Pass Template is a boilerplate design for passes. Passes that are issued under a specific Pass Template will inherit its type (e.g., Membership/Loyalty, Gift Card, Event Ticket) and general layout.
You have two options for creating a Pass Template:
Manually Create a Pass Template: You can do this directly within the Workspace.
You can also add Custom Attributes wherever you see a lightning bolt icon ⚡. Values that get shown to passholders in these fields can be set an updated using the API.
Programmatically Create a Pass Template: Use our API endpoints to configure an Apple Pass Identifier and for Pass Template creation and updating:
Custom Attributes allow you to vary each pass by having the values shown be dynamic for each pass. Custom Attributes on a Pass Template have support for attributes from two entities, Pass and User. These attributes can be set in the UI or API when creating passes. User Attributes are shared between all passes that are assigned to a user. Pass Attributes are only used for a specific pass.
Step 4: Issue and Update Passes
Use the userPassUpsert API endpoint to issue and update passes based on the Pass Template you’ve created. The unique Pass Download Link included in the response can be shared with your user to install the pass. The Pass Download Link adapts to the user's device type and installs an Apple Wallet or Google Wallet pass accordingly.
To update user attributes in your template, ensure they are passed within the User data. Pass-specific attributes come into play when managing multiple passes per user (e.g., ticket numbers, expiration dates).
Here’s an example combining both User and Pass attributes:
curl --request POST \
--url https://api.trybadge.com/v0/rpc/userPassUpsert \
--header 'accept: application/json' \
--header 'authorization: Bearer 6Q3F2K8bbYYfNn1X1N55hJGgFEzzKmqaRWolLT2a' \
--header 'content-type: application/json' \
--data '
{
"user": {
"attributes": {
"memberBalance": "1000"
},
"id": "123456789012",
"email": "[email protected]"
},
"pass": {
"attributes": {
"ticketNumber": "ABC123",
"ticketExpiration": "New Value"
},
"id": "00000000001"
},
"passTemplateId": "a84f890a-2478-925f-38ba-673e833e526c"
}
'
Step 5: Send Push Notifications
When users have installed your passes, they become passholders who can receive campaigns from you.
Use passSendPushNotification to programmatically send push notifications to specific passes. Targeting logic, such as determining which passes should receive notifications, is typically managed on your side. Ensure you track the passId that you set for each pass when issuing them via the userPassUpsert endpoint, as this identifier will be needed to send notifications to the correct passholders.
To mirror the Campaign functionality that is available in the Badge Workspace, you can combine a push notification with pass changes using userPassUpsert.