Pass created Hook

Receive information about a pass that has been created

Event

pass_created

HTTP-Method

POST

Purpose

Pushes information about a Wallet pass that has been created to the target-url.

Submitted values

JSON-Array containing the following information: • uniqueIdentifier - the unique identifier of the pass that can be e.g. shown in the barcode and used for ticket validation. • createdOn - the date when the pass was created. • passTemplate - the name of the pass-template of this pass. • linkToPassPage - link to the download page for this pass that detects the operating system of the Smartphone that is used and provides device specific help. You are encouraged to always use this link when providing the pass to users because it provides the best user experience on all devices. • userProvidedId - if it was specified, the user provided id of the pass that can be used to create download URLs is returned. • buyerEmail - if the pass was sold with Passcreator the E-Mail of the buyer is returned here. Otherwhise the field is empty. • buyerFirstName - if the pass was sold with Passcreator the firstname of the buyer is returned here. Otherwhise the field is empty. • buyerLastName - if the pass was sold with Passcreator the lastname of the buyer is returned here. Otherwhise the field is empty. • buyerStreet - if the pass was sold with Passcreator the street of the buyer is returned here. Otherwhise the field is empty. • buyerZipCode - if the pass was sold with Passcreator the zip code of the buyer is returned here. Otherwhise the field is empty. • buyerCity - if the pass was sold with Passcreator the city of the buyer is returned here. Otherwhise the field is empty. • bulkCreationId - if the pass was created via a bulk creation job the ID of the line in the bulk creation jobs' import file that defined the pass is returne. Otherwhise the field is empty. • dynamic fields: additionally to the fields above which are always submitted we'll also submit all data that is personalized. This means that the fields will differ based on the passes pass-template. To get a list of personalized fields that will be submitted, use the endpoint that describe a pass-template. This means you need to first call the endpoint that describes the dynamic field in order to know what fields are contained in the payload. • passTemplateGuid: the GUID of the template that has been used to create this pass. • genericProperties - an array containing the values that you can specify in the extended properties of a pass template