Skip to main content
Poster designs are in closed beta. The payload shape may still change. Contact PassEntry for access.
Apple’s poster designs replace the standard pass face with a full-bleed image, your fields laid over it, and an information panel underneath. PassEntry supports two of them, set on the pass template through appleEnhancedDesign.type: This guide covers the generic design. For the event ticket design, see the enhancedData.eventTicket fields on Create Pass.

One pass, every device

The generic poster renders on iOS 27 and later. Older versions of iOS cannot read the poster layout at all, so every pass carries a second copy of the same fields in its template’s standard layout. An iPhone on iOS 26 shows the standard pass, an iPhone on iOS 27 shows the poster, and you issue one pass either way. The layout a device falls back to follows the template type: a generic template falls back to a generic pass, a loyalty template to a store card, an event ticket template to an event ticket.

Prerequisites

  • Your organisation has poster designs enabled. Contact PassEntry if you need access.
  • Your template is an event ticket, generic or loyalty template. Stamp card and transit templates cannot use a poster design.
  • You have artwork ready for the poster background. Artwork is required, including when all you want is the action buttons.

Enabling the design

Set the design type and upload the artwork on the pass template.
Enable the generic poster
Passes already issued from the template are rebuilt with the new design and pushed to the wallet. The secondaryLogo and venueMap images belong to the event ticket design. The generic poster has no event guide to show a venue map in, and takes its chin logo from the template’s standard logo image.

What the poster shows

The poster face has fewer slots than the standard layout, so PassEntry maps your existing fields into it rather than asking you to author them twice. Nothing is dropped. A field that overflows the poster face moves into the information panel underneath it, and the same fields keep their usual places on devices that render the standard layout. The template’s colours apply to the poster as you set them. Featured actions are up to two buttons under the poster. Each one opens a URL, and Apple renders the button from the action type you choose. Author them on the template, in the one and two slots:
Add featured actions
Rules:
  • Filling an empty slot needs both a type and a url. Sending one without the other is rejected.
  • url must be an https:// URL.
  • The two slots must use different types.
  • featuredActions is only accepted when type is generic. Sending it on the event ticket design returns a 422.

Action types

Apple defines the full set and renders each one its own way. Pick the one that matches where the button leads. Every action takes an https:// URL, so call points at a web page rather than a tel: link.

Changing a slot later

Send only the slot you want to change. An omitted slot keeps whatever it holds.
Repoint slot two
To remove a slot, send it as null:
Remove slot two

Per-pass artwork

The poster background comes from the template, and every pass inherits it. To give one pass its own poster, send artworkImage under templateOverride when you create or update the pass.
Give one pass its own poster
Send an HTTPS URL or a base64 data URI, or point at an image you have already uploaded with {"imageAssetId": "YOUR_IMAGE_ASSET_ID"}. The 1074x1344 px limit still applies. Send null to drop the override and go back to the template’s artwork.

Per-pass actions

A pass takes a copy of the template’s featured actions when it is created, so most passes need nothing extra. To point one pass somewhere else, send the slot under enhancedData.generic on the pass.
Override an action for one pass
The same body works on Update Pass. Slot rules match the template: send both keys to fill an empty slot, send one key to change one value, send null to remove the slot, and omit the slot to leave it alone. Types must still differ across the two slots once your change is applied.
After a pass is created, its own actions win. Editing the template’s featured actions changes new passes, not existing ones, so a per-pass override is never overwritten later.

What’s next