Issuing API (v2) Migration Guide
Introduction
- There is a release (v2) of the Issuing API. The purpose of the migration guide is to point out the difference between
API (v1) and (v2).
- Reference to the specifications of the Issuing API versions are available on the TapConnect documentation by
visiting https://tapconnect.io or
https://documentation.tapconnect.io.
Changes
/v2/tickets/{ticketId}/customer-barcode is a new endpoint available on (v2). After a ticket has been created and
activated a personalized UIC918-3 or VDV compliant aztec barcode can be retrieved using this endpoint./v2/tickets/{ticketId}/info the response message now contains an array of planning information such as the operator,
start/end points, validity dates and activation status./v2/tickets/{ticketId}/full-info the response message now contains an array of planning information such as the
operator, start/end points, validity dates and activation status./v2/issued-tickets-export/{day} property name change. Property "issuedAt" (v1) changed to "occuredAt" on (v2).
