Bluetooth Transfer Specs

The SDK formats ticket data internally before transmitting to the EBT over BLE. The host app does not construct the ticket directly; it is derived from Journey/BaggageRecord response data.

Ticket formatting

Field mapping and limits

Ticket field Max length Notes

Passenger name

20

From journey.passengers[*].surname, givenName, title. Format: SURNAME/GIVENNAME TITLE

Record locator

12

Passenger-level pnr / record locator

Class of travel

16

Travel plan / journey class

Destination flight number

8

From journey.flights[*].flightNumber

Destination date

5

From journey.flights[*].departureAt / arrival-related timestamp. Rendered as ddMMM

Destination airport

3

From journey.flights[*].destinationAirport (IATA code)

Destination city

20

Destination city from journey/travel plan

1st transfer flight

8

Transfer flight 1 in journey response

1st transfer date

5

Transfer flight 1 datetime. Rendered as ddMMM

1st transfer airport

3

Transfer flight 1 airport (IATA code)

2nd transfer flight

8

Transfer flight 2 in journey response

2nd transfer date

5

Transfer flight 2 datetime. Rendered as ddMMM

2nd transfer airport

3

Transfer flight 2 airport (IATA code)

Departure airport

3

From journey.flights[*].departureAirport (IATA code)

License plate

10

From journey.baggage[*].baggageTagNumber / backend baggage identifier

Bag tag readable

15

From journey.baggage[*].baggageTagNumber. Human-readable format if available

Date field parsing

Date fields are rendered as ddMMM (e.g. 21JAN). The SDK accepts:

  • ISO-8601 offset datetime: 2024-01-15T14:30:00+01:00

  • ISO-8601 datetime with zone: 2024-01-15T14:30:00+01:00[Europe/Oslo]

  • Naive datetime: 2024-01-15T14:30:00

  • dd/MM/yyyy: 15/01/2024

  • ISO date: 2024-01-15

When timezone information is available, it is applied during rendering.

Visual indicators

  • greenstrip = true displays transfer strips on the tag

  • priority = true displays a priority marker on the tag