pass.json reference with working examples

The required identity keys establish the format version, issuer, certificate relationship, and unique pass instance. formatVersion is numeric and normally 1. passTypeIdentifier belongs to the Pass Type ID certificate, teamIdentifier is the Apple Developer Team ID, and serialNumber distinguishes this pass from every other pass issued under that Pass Type ID.

organizationName and description are user-facing metadata. Write a useful description because accessibility features and system surfaces can expose it even when it is not prominent on the pass face.

Declare exactly one classic style dictionary: boardingPass, coupon, eventTicket, storeCard, or generic. Boarding passes also require a transitType. Within that dictionary, arrange content into headerFields, primaryFields, secondaryFields, auxiliaryFields, and backFields.

Every field needs a stable key and a value. Labels are optional in some contexts but are usually helpful. Use dateStyle, timeStyle, numberStyle, currencyCode, and other formatting properties instead of pre-formatting machine-readable values into display-only strings.

Wallet colors use CSS-style rgb(r, g, b) strings. foregroundColor controls primary text, labelColor controls labels, and backgroundColor sets the base. Always check contrast on an actual pass because artwork, translucency, and system rendering affect the result.

Use the barcodes array for modern passes and order formats by preference. A legacy barcode dictionary can support older consumers. Each barcode entry needs a supported format, message, and messageEncoding; altText is useful when staff may need to read or type the value.

relevantDate, locations, and beacons help Wallet decide when a pass may be useful. They are relevance hints, not guaranteed notifications. Keep location entries precise, use valid latitude and longitude ranges, and include short relevanceText where it clarifies why the pass is appearing.

A web service can register devices and deliver pass updates. webServiceURL must use HTTPS and is paired with a sufficiently long authenticationToken. If the pass connects to an iOS app, associatedStoreIdentifiers and appLaunchURL can provide the relationship and launch context.