Deployments
Deploy a template
Moves the passes already issued from a template onto its latest design.
POST
Updating a template with a new
definition only changes passes you issue afterwards. A deployment moves the active passes already issued from it, in your API key’s environment, onto its latest revision and pushes the new design to every wallet that has them.
It takes one call. TapAce first works out which passes change, with status: "preparing", then starts the deployment on its own. Follow it with Get a deployment until status is completed or completed_with_errors. If it can’t be prepared or started, for example because the template changed again or another deployment of it is still running, status becomes failed and error says why.
Calling this again while a deployment is still being prepared returns the same deployment, using the options from the latest call.
string
required
The template ID.
string
required
A unique value, such as a UUID, so a retry never starts a second deployment.
string
default:"silent"
silent updates the passes quietly. notify also alerts holders: on Apple Wallet, passes whose field values change announce those changes, and the rest show appleText in their Message for you field. On Google Wallet, passes get googleTitle and googleBody as a message. A wallet’s text is only used when the template’s issuePlatforms offers it or an active pass in your API key’s environment uses it. A deployment that changes barcodes can only be silent.string
With
notify, the Apple Wallet message, up to 120 characters. Defaults to “Your pass has been updated with new details.”string
With
notify, the Google Wallet message title, up to 60 characters. Defaults to “Pass updated”.string
With
notify, the Google Wallet message body, up to 500 characters. Defaults to “Your pass has been updated with new details.”Response
Returns the deployment with status201. Its status is usually preparing, or pending when it could start straight away.