> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/v1/docti/use-cases-docti/boarding-pass.md).
# Boarding Pass
This section describes how to build your custom OCR API to extract data from Flight Boarding Passes using the API Builder. A Flight Boarding Pass is a document issued by an airline upon check-in that allows a passenger to access the restricted area of an airport and board an aircraft.\*\*\*\*
## Prerequisites
You’ll need at least one Boarding Pass image or pdf to test your model once created.
## Define Your Boarding Pass Use Case
Using the [Boarding Pass](https://files.readme.io/179518e-capture-decran-2021-01-20-a-143327.png) below, we’re going to define the fields we want to extract from it.
* **Passenger name**: The full name of the travelling passenger (John Doe)
* **Flight number**: The flight number for the boarding pass, including the airline's identification letters (AC 2505)
* **Date**: The date of departure in US format (10/12/2017)
* **Departure airport**: The airport of departure including the airport identification letters (New Delhi DEL)
* **Destination airport**: The airport of destination including the airport identification letters (Los Angeles LAX)
* **Boarding Time**: The boarding time (07:45)
That’s it for this example. Feel free to add any other relevant data that fits your requirement.
## Deploy your API
Once you have defined the list of fields you want to extract from your W9 Forms, head over to the platform and follow these steps:
1. Log into your [Mindee account](https://platform.mindee.com/login). You'll land on the My APIs page.
2. Click the docTI tab.
3. Click the **Create a new API** button.
On the\*\* Set up your API\*\* section, fill in the required information. Give the API a name, a description (optional), and a cover image(optional) and click on **Next**.
## Define Your Model
Click on the different fields to add them to your list
Using the interface, you can manually add each field for the data you are extracting. For this example, here are the different field configurations used:
| Field Name | Field Type | Example |
| ------------------- | ---------- | ---------------- |
| Passenger name | String | JOHN DOE |
| Flight Number | String | AC 2505 |
| Boarding Time | Date | 07:45 |
| Date | Date | 10/12/2017 |
| Departure Airport | String | New Dehli DEL |
| Destination Airport | String | Los Angeles KLAX |
Once you’re done setting up your data model, click the **Create API** button at the bottom of the screen.
You are now ready to test your API on the live interface.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.mindee.com/v1/docti/use-cases-docti/boarding-pass.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.