Templates
Save event details
Changes an event ticket template’s event details and pushes them to every pass issued from it.
PUT
Use this when the event itself changes, such as a new start time or venue. You don’t need a new revision or a deployment: TapAce updates every active pass of the template on its own, after the response.
How it reaches each wallet:
- Apple Wallet: each active pass gets a pass update whose
changes.eventnames this save. - Google Wallet: the event details are shared by all of a template’s passes, so TapAce updates them once per environment and Google issuer.
googleClassesreports each one.
string
required
The template ID. The template must be an active event ticket.
string
The SDK sends a key, but this PUT route does not currently provide stored-response replay. Read the current event state before repeating a change. See Idempotency.
object
required
The complete event details, with the properties described in Get event details. They replace the current ones, so include everything you want to keep. Send
{} to clear them all.string
default:"silent"
silent updates the passes quietly. notify also alerts holders: on Apple Wallet, passes that show a changed detail announce it on the lock screen. On Google Wallet, Google decides whether to alert, and does so only for some details and close to the event’s start.Response
Returns the new event update with status200. Its status starts as pending. Follow it with Get event details, which lists the latest saves.
The event update object
string
Unique ID, starting with
tevu_.string
pending, running (passes are being updated), completed or failed. error explains a failed save.string
silent or notify.object | null
The event details before the save.
to holds the details after it. Either is null when there were none.object | null
Who saved it:
id, name and email. For the API, id is the API key’s ID and the other two are null.integer
How many Apple Wallet passes have been sent an update so far.
object
Apple Wallet progress:
pending, delivered, notInstalled and failed passes. See delivery status.array
One entry per environment and Google issuer the template’s passes use:
environment, nullable issuerId, and status, which is updated or failed. A failed entry has an error.string
When it was saved.
finishedAt records when every pass was updated.