Apple Wallet Enhanced Event Tickets: Developer Guide

By · Published · Last updated · 12 min read

The "enhanced" event ticket in Apple Wallet is what Apple's documentation calls a poster event ticket. Instead of the small card layout of a classic event ticket, Wallet shows large event artwork, the date across the top, seat or entry details in a footer, and an event guide below the pass with a map tile, weather, venue details and quick actions. You switch it on in pass.json with a preferred style scheme and a set of semantic tags, and you keep the classic fields in the same pass so older phones still show a working ticket. Every technical claim below links to an Apple page. Where Apple is silent or inconsistent, we say so.

Shakewell Wallet issues standard Apple Wallet and Google Wallet event tickets today. It does not issue poster event tickets yet. There is more on that near the end.

What an enhanced event ticket is

Apple introduced the new ticket design in its WWDC24 session "What's new in Wallet and Apple Pay" (Apple: WWDC24 session 10108). Apple described a richer ticketing experience with visual upgrades, a new event guide and stronger integration with apps such as weather and calendar.

The layout Apple describes:

  • Top: the event logo or logo text, and the date and time, which can be an interval for a multi-day event.
  • Middle: your event artwork, given more space than on a classic ticket.
  • Footer: the primary seating or entry information (up to four elements from the seats dictionary) and the secondary logo. With no assigned seat, an admission level such as general admission can show instead.
  • Below the pass: a maps tile and an entry to the event guide, which holds quick action buttons (food, merchandise, bag policy and similar), weather, venue details, a venue map and a playlist link.
  • Lock Screen: Apple says the pass also starts a Live Activity on iPhone and Apple Watch when Wallet judges it most relevant.

In pass.json terms, a poster event ticket is still an event ticket. Apple's article says poster event tickets are considered event tickets and the scheme is posterEventTicket (Apple: Creating a poster event pass using semantic tags).

Requirements and eligibility

Apple lists two minimum requirements: add posterEventTicket to preferredStyleSchemes, and provide the required semantic tags. If you omit a required tag, the pass falls back to the legacy event pass style (Apple: Creating a poster event pass).

Apple's Pass reference describes preferredStyleSchemes as an array of schemes the system validates the pass with, "falling back to the designed type if validation fails for all the provided schemes" (Apple: Pass).

The required semantic tags depend on the kind of event:

Event kindRequired tagsSource note
Every eventeventName, venueName, venueRegionName, venueRoomApple lists these as required for all event passes
SportAlso awayTeamAbbreviation and homeTeamAbbreviationSport tickets only
Live performanceAlso performerNames, an array in decreasing order of significanceLive performance tickets

Apple recommends eventStartDate or eventStartDateInfo, and lists eventEndDate, venueLocation, admissionLevel and attendeeName as optional (Apple: Creating a poster event pass).

NFC and barcodes

Apple's documentation is not explicit about whether NFC is mandatory, so read it carefully:

  • The WWDC24 session focused on "NFC event tickets" and said you need the NFC entitlement for contactless entry (Apple: WWDC24 session 10108). Apple's Pass.NFC page says NFC "requires a special entitlement issued by Apple" (Apple: Pass.NFC).
  • Apple's poster event ticket article says: "Poster event tickets aren't compatible with tickets that require a QR code or barcode for entry." The same article says that when a pass uses NFC, it does not need a barcode (Apple: Creating a poster event pass).

So poster tickets are designed for NFC entry. Apple does not document the exact validation rule, such as whether a pass without an nfc block is rejected as a poster ticket. Test it on a device.

Which iOS version

Apple's sources disagree, so we report each:

Treat iOS 18 as the earliest version Apple has mentioned, iOS 26 as the one its current documentation states, and test on both.

Who can issue one

Apple documents the same basics as for any pass: a Pass Type ID registered in your Apple Developer account and a matching signing certificate (Apple: Building a pass). Our post on certificates and Pass Type IDs covers that setup. Apple's pages do not say you must be a major ticketing company. The extra step is the NFC entitlement, and we found no published approval criteria, so we cannot say how a small organiser will fare.

A minimal annotated pass.json

This example uses only keys that appear in Apple's pages above. Placeholder values are marked. It is a sketch to show the structure, not a pass you can sign as is.

{
  "formatVersion": 1,
  "passTypeIdentifier": "pass.com.example.events",
  "serialNumber": "TICKET-0001",
  "teamIdentifier": "ABCD1234",
  "organizationName": "Example Events",
  "description": "Ticket for Example Live",
  "webServiceURL": "https://example.com/passes/",
  "authenticationToken": "replace-with-a-long-random-token",

  "preferredStyleSchemes": ["posterEventTicket", "eventTicket"],

  "eventTicket": {
    "primaryFields": [
      { "key": "event", "label": "Event", "value": "Example Live" }
    ],
    "secondaryFields": [
      { "key": "venue", "label": "Venue", "value": "Example Hall" }
    ],
    "auxiliaryFields": [
      { "key": "seat", "label": "Seat", "value": "Row 7, Seat 4" }
    ]
  },

  "semantics": {
    "eventName": "Example Live",
    "venueName": "Example Hall",
    "venueRegionName": "Melbourne",
    "venueRoom": "Main Room",
    "performerNames": ["Example Band", "Opening Act"],
    "eventStartDate": "2027-03-12T19:30+11:00",
    "eventEndDate": "2027-03-12T22:30+11:00",
    "venueLocation": { "latitude": -37.8136, "longitude": 144.9631 },
    "seats": [
      { "seatSection": "B", "seatRow": "7", "seatNumber": "4" }
    ]
  },

  "orderFoodURL": "https://example.com/order",
  "bagPolicyURL": "https://example.com/bag-policy",

  "nfc": {
    "message": "replace-with-your-payload",
    "encryptionPublicKey": "replace-with-your-base64-key"
  }
}

What each part does:

  • preferredStyleSchemes lists schemes in the order Wallet should try them. Apple's own example is ["posterEventTicket", "eventTicket"].
  • eventTicket holds the classic fields. Apple says to keep providing primary, secondary and auxiliary fields so older systems can show the legacy ticket (Apple: Creating a poster event pass).
  • semantics carries the machine-readable tags that build the poster layout. The performerNames tag is there because this example is a live performance. venueLocation drives the maps tile and weather, and if you omit it, Apple says Wallet uses the venue name to find the map location (Apple: WWDC24 session 10108).
  • orderFoodURL and bagPolicyURL are top-level keys that Apple's Pass reference says work only for poster event tickets. They become the quick action tiles in the event guide. The same page lists others, including merchandiseURL, parkingInformationURL, directionsInformationURL, sellURL and transferURL (Apple: Pass). Apple says you can show a minimum of one and up to four quick action buttons.
  • nfc needs the Apple entitlement. The message is limited to 64 bytes and the system truncates longer ones (Apple: Pass.NFC).
  • seats entries can also hold seatIdentifier, seatLevel, seatAisle, seatType and more (Apple: SemanticTagType.Seat).

For the eventType tag, Apple's semantic tags article shows PKEventTypeMovie in an example, and its reference describes the key only as "the type of event". We did not find a complete list of values, so check the current reference before you choose one.

Image assets

Apple's pages describe the images in terms of sizes in pixels and ask for PNGs at 2x and 3x (Apple: Creating a pass with Pass Designer). From that page:

AssetApple's stated sizeWhere it appears
Icon38 by 38 pixels, squareEvery pass, Lock Screen banners, Mail
Logo50 pixels tall, 50 to 160 wideEvent passes before iOS 18 and other older styles
Primary logo30 pixels tall, 30 to 126 wideTop left of an event pass from iOS 18
Secondary logo12 pixels tall, from 12 by 12 up to 12 by 135Bottom right of an event pass from iOS 18
Thumbnail90 pixels tall, 60 to 90 wideClassic event tickets only, not poster tickets
BackgroundSize not stated in the pages we readBlurred on classic event tickets, unblurred on poster tickets
Background artworkSize not stated in the pages we readListed for event tickets from iOS 27

Apple's WWDC24 session says the new tickets add an artwork asset and a secondary logo. Use the artwork asset if you want earlier OS versions to keep rendering a strip image, or the background asset if you want the same background on every OS version (Apple: WWDC24 session 10108).

What Apple does not document in the pages we read: the exact pixel dimensions of the poster background or artwork, and the exact file names for the new assets. Apple's Pass Designer app lists the needed images for each template, so the practical way to get the sizes is to open an event ticket template there. Apple also says to keep important artwork clear of the pass overlays and not to put barcodes in images.

What older iPhones and Android users see

Older iOS. Apple says to keep the legacy fields so the ticket shows on all devices. In its WWDC24 session: if the primary, secondary and auxiliary fields are absent, "your pass will fail to validate or will appear empty on older OS versions." For a device that does not support semantic tags, Apple's article gives three cases: no legacy fields means no content, invalid legacy fields means ingestion fails on all devices, and valid legacy fields mean a fully populated legacy ticket (Apple: Creating a poster event pass).

Android and Google Wallet. A .pkpass file is an Apple format. Google Wallet event tickets are a separate system: you create an event ticket class and then ticket objects through Google's API. Google's class reference lists eventName, id, issuerName and reviewStatus as required, with optional venue and dateTime details (Google: EventTicketClass). Nothing in Apple's poster keys carries across, so plan a separate Google Wallet ticket for Android customers.

Multi-event passes

At WWDC25 Apple said poster event tickets support upcoming events, so one ticket can give access to several events, such as a season pass (Apple: WWDC25 session 202). Apple's Wallet page says each event has its own event guide, seating and ticket management links, and can be updated, added or removed remotely (Apple: What's new in Wallet).

In pass.json, the events live in an upcomingPassInformation array. Each entry has a type of event, a unique identifier, a name and date information, and then follows the poster event structure: semantics, additionalInfoFields or backFields, a URLs object and an images object (Apple: WWDC25 session 202, Apple: UpcomingPassInformationEntry). Two details from the session: an upcoming event does not reuse the pass's own properties, so repeat any URLs you want in its event guide (the venue map is reused only if you set reuseExisting to true); and you can add events later by sending a pass update.

For a multi-day festival that is one event, Apple's article shows a relevantDates array with a start and end for each day (Apple).

How updates work

Updates use the same web service as any pass. Add webServiceURL and authenticationToken; the device registers the pass and a push token with your server; when information changes your server sends a push notification, and the device fetches the changed pass (Apple: Adding a web service to update passes). Apple notes the web service must use HTTPS in production. Gate times, seat changes and new upcoming events all go through this path. Our post on how pass updates and push notifications work explains the flow.

Testing checklist

  1. Validate the structure and manifest with the free pkpass validator. It cannot verify the signature, so a device test is still the final check.
  2. Confirm passTypeIdentifier and teamIdentifier match your certificate, and that the signature includes Apple's WWDR intermediate certificate. Apple lists mismatches here among common errors.
  3. Add the pass to a device on the newest iOS and check the poster layout, the footer, the maps tile and the event guide.
  4. Add the same pass to a device on an older iOS version and check that the classic ticket shows with all its fields.
  5. Remove one required tag and confirm the pass falls back to the classic style rather than failing.
  6. Test NFC entry at a real reader with a real entitlement. Apple's debugging guidance covers logs, not contactless entry.
  7. Send an update, including adding or removing an upcoming event, and confirm it appears.
  8. Read the device log. Apple suggests dragging the .pkpass into the Simulator and watching the Console app, or filtering device logs by pass type ID or serial number.

Common mistakes

  • Dropping the classic fields. The most expensive mistake, because the pass can then be empty or rejected on older systems.
  • Missing one required tag. The pass quietly becomes a classic ticket. Check all four common tags, plus the sport or performer tags.
  • Relying on a barcode. Apple says poster tickets are not compatible with tickets that require a QR code or barcode for entry.
  • Forgetting Android. The same event needs a separate Google Wallet ticket.

What Shakewell Wallet offers today

We issue standard Apple Wallet and Google Wallet event tickets, with hosted signup forms, live updates to passes already in a customer's wallet and an API for creating and updating passes. We do not issue poster event tickets yet, and we have not shipped the semantic tag set or the upcoming events structure described here. If you need the classic ticket on both wallets, see event tickets in Apple Wallet and Google Wallet and the pkpass format reference.

Frequently asked questions

Does an enhanced event ticket need NFC? Apple's pages do not state a validation rule. Apple's WWDC24 session focused on NFC event tickets, which need Apple's NFC entitlement, and its article says poster tickets are not compatible with tickets that require a QR code or barcode for entry. Test your own pass on a device.

Which iOS version do I need? Apple's WWDC24 and WWDC25 sessions place poster event semantics in iOS 18, while its current documentation article says iOS 26 and later. Multi-event tickets are footnoted as iOS 18 and later on Apple's What's new page but listed as iOS 26 in the API reference.

What do older iPhones see? A classic event ticket, built from the primary, secondary and auxiliary fields you keep in the pass. If those fields are missing, Apple says the pass fails to validate or appears empty.

Can a small organiser issue one without a major ticketing company? Apple documents a Pass Type ID, a signing certificate and, for contactless entry, an NFC entitlement it issues. Apple's pages do not say you must be a large company, and they do not publish approval criteria for the entitlement.

How do updates work? Through the pass web service: the device registers, your server sends a push notification, and the device fetches the updated pass. Apple says you can add upcoming events to a multi-event ticket later by sending an update.

Does Shakewell Wallet issue poster event tickets? Not yet. We issue standard Apple Wallet and Google Wallet event tickets.

Sources

All Apple pages were checked on 18 November 2026.

All guides

Guides + product

Ready to ship your first wallet card?

Set up takes minutes. 60-day free trial. No card needed.