Passengers API
The Passengers API lets you manage standalone passenger records by their remote_id (the identifier you supplied when creating them). Passenger records you create and update here are reused across multiple check-ins for the same person, useful for recurring travellers where you don't want to re-send their passport every time.
Boarding passes are delivered via files[] on GET /checkin/{id} once status transitions to success. There is no per-passenger boarding-pass endpoint. See the First Check-in guide for the download flow.
Endpoints
/v1/passengerCreate a passenger
Create a standalone passenger record with a remote_id you choose.
/v1/passenger/{remote_id}Get passenger details
Retrieve a passenger by the remote_id you supplied at creation.
/v1/passenger/{remote_id}Update passenger
Update passenger fields by remote_id.
/v1/passenger/{remote_id}Delete passenger
Delete a passenger record by remote_id.
Create Passenger
Create a passenger record. The body is wrapped in passengerInfo and includes optional seatStrategies for that passenger's default seat preferences when reused on a later check-in.
Request Body
{
"passengerInfo": {
"remote_id": "pax_p1q2r3",
"first_name": "John",
"last_name": "Smith",
"date_of_birth": "1985-03-15",
"age_class": "adult",
"citizenship": "GB",
"residence": "GB",
"email": "john@example.com"
},
"seatStrategies": ["one_psg_window"]
}curl -X POST "https://portal.1checkin.com/api/corp/v1/passenger" \
-H "X-API-KEY: YOUR_PRODUCTION_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"passengerInfo": {
"remote_id": "pax_p1q2r3",
"first_name": "John",
"last_name": "Smith"
},
"seatStrategies": ["one_psg_window"]
}'Get Passenger
Retrieve a passenger by the remote_id you supplied at creation. The path is singular (/passenger/) and the identifier is your remote_id, NOT an internal numeric id, and there is no internal id exposed on this API.
curl -X GET "https://portal.1checkin.com/api/corp/v1/passenger/{remote_id}" \
-H "X-API-KEY: YOUR_PRODUCTION_API_KEY"Response
{
"passengerInfo": {
"remote_id": "pax_p1q2r3",
"first_name": "John",
"last_name": "Smith",
"date_of_birth": "1985-03-15",
"age_class": "adult",
"citizenship": "GB",
"residence": "GB",
"email": "john@example.com",
"boarding_seat": null,
"boarding_info": null
},
"seatStrategies": ["one_psg_window"]
}After this passenger is checked in via POST /checkins and that check-in transitions to success, boarding_seat and boarding_info populate on subsequent GETs.
Update Passenger
Update passenger fields. The body uses the same {passengerInfo: {...}} envelope as create. Only provided fields are updated.
Request Body
Request Body
| Name | Type | Required | Description |
|---|---|---|---|
passengerInfo | object | Yes | Wrapper for the passenger fields to update (see below). |
seatStrategies | array | No | Updated default seat preferences for this passenger. |
passengerInfo fields
Request Body
| Name | Type | Required | Description |
|---|---|---|---|
first_name | string | No | Updated first name |
last_name | string | No | Updated last name |
date_of_birth | string | No | YYYY-MM-DD |
age_class | string | No | "adult", "child", or "infant" |
citizenship | string | No | ISO 3166-1 alpha-2 |
residence | string | No | ISO 3166-1 alpha-2 |
gender | string | No | "M" or "F" |
email | string | No | Email address |
curl -X PUT "https://portal.1checkin.com/api/corp/v1/passenger/{remote_id}" \
-H "X-API-KEY: YOUR_PRODUCTION_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"passengerInfo": {
"citizenship": "GB",
"residence": "GB"
}
}'Delete Passenger
Permanently delete a passenger record. Existing check-ins that already reference this passenger keep their snapshot of the data; only future references are affected.
curl -X DELETE "https://portal.1checkin.com/api/corp/v1/passenger/{remote_id}" \
-H "X-API-KEY: YOUR_PRODUCTION_API_KEY"{"result": "success"}Where do boarding passes come from?
Boarding passes are part of the check-in lifecycle, not the passenger lifecycle. After a check-in transitions to success, the GET /checkin/{id} response carries one entry per passenger in files[], each with a presigned URL that downloads the PDF directly:
{
"url": "https://files.example.com/boarding-pass.pdf?SIGNED_QUERY",
"filetype": "boardingPass",
"file_type": "boardingPass",
"content_type": "application/pdf",
"expires": 1809849600
}The file host can differ from the API host. Download the exact files[].url, including its query string, without your API key. The hostname above is illustrative, not a production hostname or an allowlist; sandbox file URLs are sandbox-only.
See the First Check-in guide for the full download flow.
Error Responses
{
"status": "error",
"message_code": "FormError",
"status_code": 422,
"message": "Form error",
"message_human": "Form error",
"data": {
"passengerInfo": {"date_of_birth": ["Not a valid date."]}
}
}{
"status": "error",
"message_code": "NotFound",
"status_code": 404,
"message": "Passenger with id pax_p1q2r3 does not exist",
"message_human": "Not found",
"data": null
}Related
- Checkins API (create check-in requests, where boarding passes appear)
- Guide: Your First Check-in