Availability API

The Availability API tells you whether 1Checkin can check in on an airline and route before you submit a check-in request, and when check-in opens for a flight.

Endpoints

POST/v1/checkAvailable

Check route availability

Check if a specific airline and route combination is supported.

🔐Authentication required
POST/v1/checkMultipleAvailable

Check multiple routes

Check availability for multiple routes at once.

🔐Authentication required
POST/v1/checkTime

Check when check-in opens

Whether a flight's airline and route are available, and when check-in can start.

🔐Authentication required
GET/v1/routes.json

List known routes

Routes 1Checkin has already handled, each marked available or not.

🔐Authentication required

Check Availability

Checks one airline and route. The answer applies your account's route settings, destination-country restrictions, 1Checkin's record for the route and the airline's defaults.

Request Body

Request Body

NameTypeRequiredDescription
airline_codestringYesIATA airline code (e.g., "BA", "AA", "LH")
operating_carrier_codestringNoOperating carrier IATA code, for codeshare flights. An unknown code makes the answer false
departure_codestringNoDeparture airport IATA code (e.g., "LHR")
destination_codestringNoDestination airport IATA code (e.g., "JFK")
departure_datestringNoDeparture date (YYYY-MM-DD). Accepted, but does not change the answer; in a multiple check it marks connected flights
flight_numstringNoFlight number without airline prefix. Accepted, but does not change the answer
Check route availability
curl
curl -X POST "https://portal.1checkin.com/api/corp/v1/checkAvailable" \
  -H "X-API-KEY: YOUR_PRODUCTION_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "airline_code": "BA",
    "departure_code": "LHR",
    "destination_code": "JFK"
  }'

Response

200Availability check result
Route available
json
{
  "result": true,
  "is_free_try_available": false
}
Route not available
json
{
  "result": false,
  "is_free_try_available": false
}

Check Multiple Routes

Checks several routes in one request, each as a single check would. The routes come back in the order sent, each with every request field (missing ones as null) and three answers: is_route_available, is_free_try_available and is_connected. is_connected is true when a route continues the one before it (same airline and operating carrier, same date, departing from the previous destination), false when it does not, and null when either route lacks a date or an airport. The first route is always false.

Check multiple routes
curl
curl -X POST "https://portal.1checkin.com/api/corp/v1/checkMultipleAvailable" \
  -H "X-API-KEY: YOUR_PRODUCTION_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "routes": [
      {"airline_code": "BA", "departure_code": "LHR", "destination_code": "JFK"},
      {"airline_code": "LH", "departure_code": "FRA", "destination_code": "SFO"}
    ]
  }'
Response
json
{
  "result": [
    {
      "airline_code": "BA",
      "operating_carrier_code": null,
      "departure_code": "LHR",
      "destination_code": "JFK",
      "departure_date": null,
      "flight_num": null,
      "is_route_available": true,
      "is_free_try_available": false,
      "is_connected": false
    },
    {
      "airline_code": "LH",
      "operating_carrier_code": null,
      "departure_code": "FRA",
      "destination_code": "SFO",
      "departure_date": null,
      "flight_num": null,
      "is_route_available": true,
      "is_free_try_available": false,
      "is_connected": null
    }
  ]
}

Check When Check-in Opens

For one flight: whether its airline and route are available, and when 1Checkin can start the check-in. When the operating carrier differs from airline_code, a second entry answers for the operating carrier. This check uses 1Checkin's general record for the route, not your account's route settings.

Request Body

Request Body

NameTypeRequiredDescription
airline_codestringYesIATA airline code
flight_numstringYesFlight number without airline prefix
operating_carrier_codestringYesOperating carrier IATA code (the same as airline_code unless it is a codeshare)
departure_codestringYesDeparture airport IATA code
destination_codestringYesDestination airport IATA code
departure_datestringNoLocal departure date at the departure airport (YYYY-MM-DD). Send it with departure_time, or send the UTC pair
departure_timestringNoLocal departure time (HH:MM)
departure_date_utcstringNoDeparture date in UTC (YYYY-MM-DD); with departure_time_utc, used instead of the local pair
departure_time_utcstringNoDeparture time in UTC (HH:MM)
Check when check-in opens
curl
curl -X POST "https://portal.1checkin.com/api/corp/v1/checkTime" \
  -H "X-API-KEY: YOUR_PRODUCTION_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "airline_code": "BA",
    "flight_num": "117",
    "operating_carrier_code": "BA",
    "departure_code": "LHR",
    "destination_code": "JFK",
    "departure_date": "2026-10-02",
    "departure_time": "08:25"
  }'
Response
json
{
  "results": [
    {
      "airline_code": "BA",
      "checkin_info": "available",
      "checkin_open_time": "2026-10-01T07:25:00+00:00"
    }
  ]
}

checkin_info is available, not_available, or no_info when 1Checkin's record for the route is too thin or old for a firm answer. checkin_open_time is when 1Checkin can start the check-in, in UTC, from the airline's check-in window; it is null when the route is not available.

List Known Routes

Every airline, departure and destination that 1Checkin has already checked in on, each marked available or not. The list is built from past check-ins across all customers, so a route we have not handled yet is missing even when POST /checkAvailable accepts it, and the list does not apply your account's route settings. Use it for a local shortlist and confirm each sale with POST /checkAvailable. The optional query parameters airline_code, departure_code and destination_code narrow the list, and GET /v1/routes.csv returns the same rows as semicolon-separated CSV with the flags as 1 or 0.

Get all routes
curl
curl -X GET "https://portal.1checkin.com/api/corp/v1/routes.json" \
  -H "X-API-KEY: YOUR_PRODUCTION_API_KEY"
Routes response (excerpt)
json
{
  "routes": [
    {
      "airline_code": "BA",
      "departure_code": "LHR",
      "destination_code": "JFK",
      "is_route_available": true,
      "is_free_try_available": false
    },
    {
      "airline_code": "LH",
      "departure_code": "FRA",
      "destination_code": "JFK",
      "is_route_available": true,
      "is_free_try_available": false
    }
  ]
}

Interpreting the Response

The response is intentionally minimal: result is a boolean (the only signal you need to decide whether to call POST /checkins), and is_free_try_available is true when the answer is false but 1Checkin's record for the route is too thin or old to rule it out (few or no recent check-ins). You can still submit a check-in on such a route: 1Checkin attempts it, and it is billed like any other check-in. There is no machine-readable reason code. When both are false, treat the route as unsupported and either skip the booking or fall back to manual airport check-in.

routes.json (above) lists the routes we have already handled, not every route we support. Before each sale, POST /checkAvailable is the answer to rely on.

Related