Skip to content
looot docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

SearchAPI.io - Booking.com Property API

SearchAPI.io tool searchapi-io-booking-property on looot: input fields, $0.004 per call, output shape, and code to run it with curl, JavaScript or Python.

The Booking.com Property API returns the full detail for a single property page: property information (name, address, review score and breakdown, images, GPS), bookable rooms with bed configuration and prices, amenities, review topics and featured reviews, an AI review summary, house rules, FAQs, and nearby places: restaurants, attractions, public transport, beaches and airports with distances. Cross-linking: The required url parameter is the link field of a property returned by the Booking.com API.

  • Tool id: searchapi-io-booking-property
  • Provider: SearchAPI.io
  • Job: Booking property search (search.booking-property)
  • Price: $0.004 per call. A call that fails at the provider costs $0.

Inputs

Name Type Required Description
adults integer no
check_in_date string no
check_out_date string no
children_ages string no
currency string no
engine string no Fixed to “booking_property” for this endpoint. Example: “booking_property”
language string no
rooms integer no
url string yes

Output

Shape of the run’s result, checked against 1 real answer:

{ faqs: { answer, question, asked_date, answered_date }[], rooms: { name, price, currency, position, bathrooms, room_size, max_guests, bed_options: { type, count }[][], room_size_unit, extracted_price, bed_configuration }[], amenities: { name, slug, value }[], fine_print, house_rules: { pets: { charges }, parties, smoking, check_in, children: { minimum_age, are_children_allowed }, check_out, age_restriction, minimum_check_in_age }, nearby_places: { places: { name, type, distance, gps_coordinates: { ... }, transportations: { ... }[] }[], category }[], review_topics: string[], search_metadata: {... ...

The shape is cut here. Signed in, looot inspect searchapi-io-booking-property prints all of it.

Run it

Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.

Example input with placeholder values:

curl -X POST "https://api.looot.ai/v1/runs" \
  -H "Authorization: Bearer $LOOOT_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"endpointId":"searchapi-io-booking-property","input":{"url":"https://example.com","engine":"booking_property"},"wait":30}'
const response = await fetch("https://api.looot.ai/v1/runs", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
    "Content-Type": "application/json",
    "Idempotency-Key": crypto.randomUUID(),
  },
  body: JSON.stringify({
    endpointId: "searchapi-io-booking-property",
    input: {
      url: "https://example.com",
      engine: "booking_property",
    },
    wait: 30,
  }),
});
const run = await response.json();
console.log(run.status, run.result);
import os
import uuid

import requests

response = requests.post(
    "https://api.looot.ai/v1/runs",
    headers={
        "Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "endpointId": "searchapi-io-booking-property",
        "input": {
            "url": "https://example.com",
            "engine": "booking_property",
        },
        "wait": 30,
    },
    timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))

To let looot pick among every provider of this job instead, send job:search.booking-property as endpointId; see the job page.

Was this page helpful?