Type: Apple Wallet Pass Response. Type: Google Pay Pass Response. A pass response for Google Pay. A pass is a populated template. Therefore, the pass includes all headers and fields from the template, along with identifiers for the pass and URLs to access it. The fieldType corresponds to the template field module an object that the field belongs to.
Update the specified pass. You need only include the fields that you want to update for the pass. Optionally, you can also Schedule an update if you want to update a pass at a later date and time.
How to Save Coupons to Passbook - thegoodstuff
Within the headers and fields objects, these are the changeMessage, value, and label fields. You can update locations on a pass, but doing so will replace all locations on the pass. See the Location Object for more about the fields you should provide in the locations array.
You can also update a pass to include an expiration date using the expirationDate key. You can optionally assign an externalId to the pass or generate the pass from templates with externalId s. See the appropriate endpoints to assign or use external IDs.
- pendleton black friday deals.
- brook taverner deals.
- dishwasher tablets deals.
- great clips coupon 47906.
- Local Discounts for Restaurants, Family Fun, Spas, Home Improvement & Automotive?
Type: Any. Returns passLocationId for each location on the pass. Use this value to identify locations in other location-based operations.
- rex goliath coupon?
- amphetamine coupon card.
- coupon code express smile atlanta;
These endpoints support passes incorporating external IDs for the template, the pass, or both. Returns a complete pass using an externalId , including headers, fields on the pass, and metadata about the pass. Include an array of templates IDs, required to identify individual passes if there are multiple passes for the externalId in the path. If there are multiple passes for the externalId and you do not specify the templates corresponding to the passes you want to update, your request will return a A response returns one or more ticketId values, each referencing the pass update operation.
If your request does not include the templates array, the response includes a single ticketId. If your request includes the templates array, the response is an array of of ticket objects, corresponding to the order of templates in the array. Create a pass from the specified template and give it a custom identifier. You can use this custom ID to perform oprations against the pass in addition to the standard, unique id given by Wallet.
Update a pass. You can provide any of the fields or headers used when creating a pass to update the pass. You can use this custom ID to perform oprations against the pass like you would use the standard, unique id given by Wallet. This endpoint supports more methods, simplifying your integration. Tags are plain-text identifiers for passes. Use tags to identify passes for segmentation purposes, or to target an audience of passes for updates. A tag id or name. The request returns a paginated list of passes associated with the specified tag.
These endpoints support passes using external IDs. Tags are limited to 15 per pass.
Specifying a Version
Use segments to group and target passes for subsequent updates. Contains and , or , or not operators for tags that identify your segment. Boolean tag selectors specifying a group of passes. An identifier for the operation. Use this value to reference the operation for troubleshooting purposes.
Use this ID to reference the operation for troubleshooting purposes. Delete a segment by ID. This operation just deletes the segment criteria; the passes previously selected by this criteria are unchanged. Create and store flight information for use with boarding passes. When creating boarding passes, you can reference a flight, automatically populating flight information on the pass. By storing and referencing flight information independently of your passes, you can update a single flight, automatically pushing an update to all passes referencing that flight.
Type: Flight Object.
The presence or absence of fields in the flight object may slightly affect the design of boarding passes. A successful request returns the flightId and flightExternalId if applicable values, so you can reference the flight in later operations. Type: Flight Response. A complete flight response, including identifiers to reference the flight and the fields defined within the flight. Update any of the keys provided in the fields object when creating a flight. Provide only the fields you want to update; any fields that you omit from the payload remain unchanged.
A successful request returns the complete, updated flight object and the flightId and flightExternalId if applicable values, so you can reference the updated flight in later operations. These endpoints support flight objects created using external IDs. Create and store event information for use with event tickets. When creating event tickets, you can reference an event, automatically populating event information on the pass.
By storing and referencing event information independently of your passes, you can update a single event, automatically pushing an update to all passes referencing it. If your request uses an eventExternalId already associated with an existing event, the call is treated as a PUT , and updates the existing event. As with the PUT method, any fields not contained in the request are unchanged.
em client coupon 12222
Type: Event Request. The event was successfully created. A successful request returns the eventId and eventExternalId if applicable values, so you can reference the event in later operations. Type: Event Response. An event response returns identifiers that you can use to reference the event in other endpoints, along with the complete event request body.
Update any of the keys provided in the fields object of an Event Request. A successful request returns the complete, updated event object and the eventId and eventExternalId if applicable values, so you can reference the updated event in later operations.
Wallet callbacks provide a pass event notification, e. Update a callback specification. The payload to update a callback is identical to the payload to create a callback. Delete a registered callback specification. Because a project only uses a single callback specification, you specify the projectId only. Return status information about tickets or the server itself.
For operations that cannot complete immediately, the system returns a ticketId. You can look up this ticketId to determine the true status of the operation. Get the status of a ticket. Some operations can't complete immediately and return a ticketId ; use this item to determine the true status of the operation. For example, if the same user installs, removes, and then adds the same pass again, a response will show two passes installed and one pass removed.
How to delete expired coupons from passbook
Returns pass activity per day for a given project by id. This endpoint represents net activity, including repeated actions by the same user. For example, if the same user installs, removes, and then adds the same pass again, the report shows two passes installed and one pass removed. Returns a per-day activity for all days in the time range.
If your request did not specify a date range, the response includes all activity, organized by day, since the projects's createdAt date. Each object in this array represents pass activity for a single day. Each object represents net activity, including repeated actions by the same user. For example, if the same user installs, removes, and then adds the same pass again, the object shows two passes installed and one pass removed. In addition to the major version, all requests must include an Api-Revision header, with a more specific version number e. HTTP Authentication basic master.
Api-Revision header String Required. The particular API revision you want to use. In general, this is 1. Possible values: 1. Determines the order of results. The direction of the result set, ascending or descending.