> For the complete documentation index, see [llms.txt](https://docs.globalalerting.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.globalalerting.com/administration/travel/itinerary-parsing-overview.md).

# Itinerary Parsing Overview

GAP has the ability to capture itineraries sent via e-mail.

## Finding Your E-Mail Address

Each tenant has a unique e-mail address to which itineraries should be sent.

1. From the GAP Admin home page, click "Itineraries" under the "Travel" section.
2. The e-mail address for the tenant in scope can be found under the "Itinerary Email Parsing" section at the top of the screen.

## Required Information

### Flight Segments

* Airline name
* Flight number
* Departure location
* Arrival location
* Departure time
* Arrival time

### Hotel Segments

* Hotel name
* Address
* City
* Check-in date
* Check-out date

### Car Hire Segments

* Car company
* Pick-up address
* Pick-up city
* Pick-up date
* Pick-up time
* Drop-off address
* Drop-off city
* Drop-off date
* Drop-off time

### Rail Segments

* Rail line
* Train number
* Departure station
* Departure date
* Departure time
* Arrival station
* Arrival date
* Arrival time

## Best Practices

* E-mail content should be the original booking confirmation e-mail provided by the point of sale.
* Do not write out your travel itinerary manually. Instead, send the original booking itinerary from the supplier that is e-mailed to you after booking.
* Refrain from sending e-mails with a lot of forwards or e-mail conversations in the message body as this may cause the parse operation to fail.
* Photos or scans of bookings / itineraries will not be parsed.
* Do not send in scans or screenshots of your e-mail account.  Instead, forward the original booking e-mail or PDF attachment from the supplier.
* Boarding passes will likely not be parsed.
* Include only one itinerary per e-mail.  Multiple bookings are not supported on a single e-mail.
* Booking format can be an HTML e-mail or a PDF attachment (if that is what the point of sale provided).  Please note that PDF files must be able to be copied and pasted.  Encrypted PDF files and scans / images will not be parsed.
* Booking e-mails must contain all required information in order to parse. If an e-mail is missing a [required piece of information](#required-information), the parse operation will fail.
* Only information provided in the e-mail can be parsed.  Additional lookups are not generally undertaken except in the case of airport codes (for example, if the e-mail contains “London Heathrow” as a departure airport, “LHR” will be added to the finalized data).