Search for transfers Beta

Use the /transfers/search endpoint to search for available airport transfers and point-to-point rides. Display the returned options to travellers and redirect them to Booking.com to complete the booking.

The /transfers/search endpoint returns resolved journey details, available vehicle options, capacity, prices, cancellation information, an expiry time, and a Booking.com URL for each vehicle option.

Use the following operation to search for transfers:

1. Collect the traveller’s journey, passenger, currency, language, and booker-country details.
2. Send a request to /transfers/search.
3. Display the returned resolved route, vehicle options, prices, capacity, and cancellation policy.
4. Check that the results have not expired before displaying them.
5. Let the traveller select a vehicle option.
6. Redirect the traveller using the url returned for that selected option.
7. The traveller completes the reservation on Booking.com.

The request body is JSON and must contain:

• route
• passengers
• currency
• booker.country

The optional language field defaults to en-gb.

{
  "route": {
    "legs": [
      {
        "pickup": {
          "location": {
            "airport": "AMS"
          },
          "datetime": "2026-09-27T14:30:00"
        },
        "dropoff": {
          "location": {
            "coordinates": {
              "latitude": 52.3676,
              "longitude": 4.9041
            }
          }
        }
      }
    ]
  },
  "passengers": 3,
  "currency": "EUR",
  "booker": {
    "country": "ro"
  }
}

Use route.legs to define the journey.

• A one-way journey contains one leg.
• A return journey contains two legs.
• Legs must be in travel order.
• Every leg must include its own pickup location, pickup datetime, and drop-off location.

The first leg must include:

• The pick-up location.
• The local pick-up date and time.
• The drop-off location.

{
  "route": {
    "legs": [
      {
        "pickup": {
          "location": {
            "airport": "AMS"
          },
          "datetime": "2026-12-12T14:30:00"
        },
        "dropoff": {
          "location": {
            "coordinates": {
              "latitude": 52.3676,
              "longitude": 4.9041
            }
          }
        }
      }
    ]
  }
}

A return journey contains two legs:

• The outbound leg.
• The return leg.

Both legs must include their own pick-up location, pick-up date and time, and drop-off location.

For a standard return journey, the second leg’s locations must match the outbound leg in reverse:

• Return pickup = outbound drop-off.
• Return drop-off = outbound pickup.

Example:

{
  "route": {
    "legs": [
      {
        "pickup": {
          "location": {
            "airport": "MAN"
          },
          "datetime": "2026-12-12T10:00:00"
        },
        "dropoff": {
          "location": {
            "google_place_id": "ChIJVYR0dR3hxUcRwz_xGKN6B_s"
          }
        }
      },
      {
        "pickup": {
          "location": {
            "google_place_id": "ChIJVYR0dR3hxUcRwz_xGKN6B_s"
          },
          "datetime": "2026-12-15T16:15:00"
        },
        "dropoff": {
          "location": {
            "airport": "MAN"
          }
        }
      }
    ]
  }
}

Each pick-up or drop-off location must contain exactly one of the following properties:

Do not combine location types. For example, a location must not contain both airport and google_place_id or coordinates.

Use airport to identify a location by its IATA airport code.

{
  "location": {
    "airport": "AMS"
  }
}

Use google_place_id to identify a location by its Google Place ID.

{
  "location": {
    "google_place_id": "ChIJVYR0dR3hxUcRwz_xGKN6B_s"
  }
}

Use coordinates to identify a location by latitude and longitude.

{
  "location": {
    "coordinates": {
      "latitude": 52.3676,
      "longitude": 4.9041
    }
  }
}

Use pickup.datetime for the local pickup date and time of each leg.

Use the following format:

YYYY-MM-DDTHH:mm:ss

For example:

{
  "datetime": "2026-12-12T14:30:00"
}

For a return journey, provide a separate pickup.datetime for each leg.

Use passengers to specify the number of travellers requiring the transfer.

{
  "passengers": 3
}

The value must be at least 1.

The response contains vehicle options with sufficient passenger capacity for the requested number of passengers. Use the returned max_passengers value when displaying each option.

Use currency to specify the currency used for prices in the response.

The current schema lists these ISO 4217 currency codes:

AED, AUD, CAD, CHF, CLP, CNY, CZK, DKK, EGP, EUR, GBP, HKD, HUF, IDR, ILS, INR, ISK, JPY, KRW, MAD, MXN, NOK, NZD, PLN, QAR, RON, RSD, SAR, SEK, SGD, THB, TRY, TWD, UAH, USD and ZAR.

Example:

{
  "currency": "EUR"
}

• If you provide an unsupported currency, the API returns a 400 Bad Request response with an invalid_parameter error.

Use language to specify the language used for the search results and Booking.com redirect URL.

{
  "language": "es"
}

If you omit language, the API defaults to en-gb.

Use booker.country to provide the booker’s two-letter country code.

{
  "booker": {
    "country": "ro"
  }
}

The booker country provides context for pricing and for displaying applicable taxes and fees.

A successful response contains a request_id and a data object.

{
  "request_id": "01fr9ez700exycb98w90w5r9sh",
  "data": {
    "currency": "EUR",
    "expires_at": "2026-12-12T10:30:00Z",
    "route": {
      "legs": [
        {
          "pickup": {
            "datetime": "2026-12-12T14:30:00",
            "location": {
              "name": "Amsterdam Airport Schiphol (AMS)",
              "address": "Evert van de Beekstraat 202, 1118 CP Schiphol, Netherlands",
              "city": "Schiphol",
              "country": "nl",
              "coordinates": {
                "latitude": 52.3105,
                "longitude": 4.7683
              },
              "iata": "AMS"
            }
          },
          "dropoff": {
            "location": {
              "name": "Booking.com HQ",
              "address": "Herengracht 597, 1017 CE Amsterdam, Netherlands",
              "city": "Amsterdam",
              "country": "nl",
              "coordinates": {
                "latitude": 52.3676,
                "longitude": 4.9041
              },
              "iata": null
            }
          },
          "duration": null,
          "distance": null
        }
      ]
    },
    "vehicle_options": [
      {
        "name": "Standard",
        "max_passengers": 4,
        "max_luggage": 3,
        "price": 45.50,
        "url": "https://taxis.booking.com/search/..."
      }
    ],
    "cancellation_policy": {
      "type": "free_cancellation",
      "details": {
        "context": "before_pickup",
        "duration": "PT48H"
      }
    }
  }
}

expires_at is the expiry timestamp for the search results. It uses a timezone-aware date-time, for example:

{
  "expires_at": "2026-09-20T10:30:00Z"
}

After expiry, prices and availability may change. Run a new search before showing stale results or relying on a previously returned option.

The response contains the resolved route and its journey legs.

Each leg includes:

• The pickup datetime and resolved pickup location.
• The resolved drop-off location.
• duration, an estimated travel time in minutes, or null.
• distance, an estimated distance in kilometres, or null.

Resolved pickup and drop-off locations include:

• name
• address
• country
• coordinates
• city, which may be null
• iata, which contains a three-letter airport code for airports and is null for non-airport locations

The pickup datetime is expressed in the local time of the pickup location and does not include a timezone or UTC offset.

The response does not include a separate drop-off datetime. The current transfer search returns null for both duration and distance, so a drop-off time cannot currently be derived from the response. If a future response provides a duration, any derived drop-off time must be presented as an estimate.

The vehicle_options array contains the available vehicle options for the journey. Options are sorted by price, cheapest first.

Each option includes:

The vehicle_options array contains the available vehicle options for the journey.

Each option includes:

The cancellation_policy.type value is one of:

• free_cancellation - Free cancellation is available under the conditions in details.
• non_refundable - The transfer is non-refundable.

For free cancellation, details contains the cancellation context and an ISO 8601 duration. For example:

{
  "cancellation_policy": {
    "type": "free_cancellation",
    "details": {
      "context": "before_pickup",
      "duration": "PT48H"
    }
  }
}

In this example, PT48H means that free cancellation is available up to 48 hours before pick-up.

For a return journey, the cancellation policy applies to both legs.

Each vehicle option includes a url that redirects the traveller to Booking.com with that vehicle option selected.

{
  "name": "Standard",
  "max_passengers": 4,
  "max_luggage": 3,
  "price": 45.50,
  "url": "https://taxis.booking.com/search/..."
}

Use the returned URL to redirect the traveller to Booking.com and continue with the selected vehicle option.

✅ Use accurate location data

• Use the most appropriate supported location type for each pick-up and drop-off point.
• Specify exactly one of airport, google_place_id or coordinates for each location.
• Provide locations for both legs of a return journey.
• For a standard return journey, provide the outbound locations in reverse for the return leg.

✅ Use local pick-up times

• Provide pickup.datetime in the local time of the pick-up location.
• Do not include a time zone or UTC offset.
• Provide a separate pick-up date and time for each journey leg.

✅ Keep availability and prices up to date

• Check expires_at before displaying previously retrieved search results.
• Run a new search after the results expire.
• Do not assume that prices or availability remain unchanged.

✅ Display vehicle capacity accurately

• Use max_passengers and max_luggage when displaying vehicle options to travellers.
• Do not infer vehicle capacity from the vehicle category or display name.

✅ Use the returned redirect URL

• Redirect travellers using the url returned for their selected vehicle option.
• Do not construct or modify Booking.com transfers booking URLs.