back
loading skill details...
Collect Booking hotel information through Dataify Scraper API. Use when the user asks to gather, scrape, crawl, fetch, extract, or collect Booking hotel info...
---
name: dataify-booking-hotellist
description: Collect Booking hotel information through Dataify Scraper API. Use when the user asks to gather, scrape, crawl, fetch, extract, or collect Booking hotel information, Booking hotel details, Booking hotel listings, Booking hotel URLs, or data from a Booking URL, including noun-plus-verb combinations such as Booking hotel information plus collect/scrape/crawl/fetch/extract, "Booking hotel info scrape", "Booking hotel URL collect", "Booking hotel information extract", "Booking 酒店信息采集", "Booking 酒店信息抓取", "Booking 酒店信息爬取", "Booking 酒店信息获取", "Booking URL 提取", or requests using spider ID booking_hotellist_by-url.
---
# Dataify Booking Hotel Info
Use this skill to create Booking hotel information collection tasks through Dataify's builder endpoint.
## Required Workflow
1. Use the `booking_hotellist_by-url` spider when the user wants to collect Booking hotel information from one or more Booking URLs.
2. Check the local Python runtime before calling scripts. Prefer `python`; use `python3` if that is the available Python command. Require Python 3 or newer. Do not use version-specific commands such as `py -3.10`.
3. Tell the user which parameters are required and what the defaults are. Ask whether any values should be changed.
4. Ask whether the user wants to collect multiple parameter sets. If yes, collect multiple `spider_parameters` objects for the same spider ID. If the user already supplied multiple Booking URLs, treat that as a multiple-set request.
5. Before every real API call, show a Markdown confirmation table with the exact parameters that will be submitted. The table must use these columns: `Parameter`, `Current value`, `Default value`, `Required`, `Description`.
6. If any dropdown fields are added in the future, show all available dropdown values in Markdown tables with exactly these columns: `Label`, `Value`. This tool currently has no dropdown fields.
7. Ask the user whether any value should be changed. Do not call the API until the user explicitly confirms the table.
8. Check for the Dataify API token only after parameter confirmation. Prefer a token explicitly provided by the user, then `DATAIFY_API_TOKEN` from the environment.
9. If no token is available, tell the user: `Missing Dataify API token. Provide a token, or log in/register at` [Dataify](https://dashboard.dataify.com/login?utm_source=skill) `If you already have one, open` [Dataify](https://dashboard.dataify.com?utm_source=skill) `and copy the API TOKEN from the top-right area.`
10. If the user provides a token and `DATAIFY_API_TOKEN` is not already saved locally, ask whether to save it as `DATAIFY_API_TOKEN`. Save it only after explicit consent and never echo the token back.
11. After the API call, report the collection task ID and status. Look for common response fields such as `task_id`, `taskId`, `id`, `status`, `data.task_id`, `data.id`, or `data.status`. Then remind the user to view task details in the official dashboard: [Dataify](https://dashboard.dataify.com?utm_source=skill)
## Parameter Preview
Use the preview helper whenever possible:
```bash
python scripts/preview_params.py --url "https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"
```
For multiple parameter sets, pass the exact JSON array:
```bash
python scripts/preview_params.py --parameters-json '[{"url":"https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"},{"url":"https://www.booking.com/hotel/us/example.en-gb.html"}]'
```
## API Call
Use the call helper after confirmation and token handling:
```bash
python scripts/booking_hotellist.py --url "https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"
python scripts/booking_hotellist.py --parameters-json '[{"url":"https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"},{"url":"https://www.booking.com/hotel/us/example.en-gb.html"}]'
```
If the token was provided in the conversation instead of the environment, pass it with `--token` and do not expose it in user-facing output:
```bash
python scripts/booking_hotellist.py --token "USER_TOKEN" --url "https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"
```
## Tool
| Mode | Spider ID | Required parameters | Default spider_parameters |
|---|---|---|---|
| `by-url` | `booking_hotellist_by-url` | `url` | `[{"url":"https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"}]` |
Every request also accepts `file_name`. If omitted, use `{{TasksID}}`.
## Fixed Request Fields
Always submit to `https://scraperapi.dataify.com/builder?platform=1` with:
| Field | Value |
|---|---|
| `spider_name` | `booking.com` |
| `spider_id` | `booking_hotellist_by-url` |
| `spider_parameters` | JSON array of one or more parameter objects |
| `spider_errors` | `true` |
| `file_name` | User value, otherwise `{{TasksID}}` |
Send parameters as form data. Keep `spider_parameters` as a JSON string inside the form body.
don't have the plugin yet? install it then click "run inline in claude" again.
restructured into implexa's six-part format, made decision logic explicit (single vs batch URLs, token sources, error handling), added network and auth edge cases (401/403/429/500+, rate limits, token expiry), documented environment setup and parameter confirmation flow with explicit user approval gates.
use this skill to scrape Booking.com hotel data via Dataify's builder endpoint. trigger it when a user asks to gather, scrape, crawl, fetch, extract, or collect Booking hotel information, listings, details, or URLs. the skill handles single or batch hotel URL submissions and returns a collection task ID for tracking in the Dataify dashboard.
https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-mainDATAIFY_API_TOKEN or provided directly by user (required for API call){{TasksID}} if omittedhttps://scraperapi.dataify.com/builderExternal connection setup: register at https://dataify.com/login. retrieve your API token from https://dataify.com/dashboard/ (top-right area). store it as environment variable DATAIFY_API_TOKEN or provide it inline during the skill run.
ask the user for one or more Booking hotel URLs. confirm whether they want to submit a single URL or multiple URLs in one batch request.
display a markdown confirmation table with these columns: Parameter, Current value, Default value, Required, Description. populate it with:
url: the Booking URL(s) providedfile_name: user value or {{TasksID}}spider_name: always booking.com (informational, not user-editable)spider_id: always booking_hotellist_by-url (informational, not user-editable)spider_errors: always true (informational, not user-editable)ask the user to review the table and confirm any parameter changes. do not proceed until the user explicitly approves.
check for the Dataify API token in this order: (a) token explicitly provided by user in conversation, (b) DATAIFY_API_TOKEN environment variable. if neither exists, output: Missing Dataify API token. Provide a token, or log in/register at https://dataify.com/login. If you already have one, open https://dataify.com/dashboard/ and copy the API TOKEN from the top-right area. then stop.
if the user provided a token and DATAIFY_API_TOKEN is not in the environment, ask: save this token as DATAIFY_API_TOKEN for future use? save only after explicit user consent. never echo or display the token in output.
determine the Python command available locally: check python --version first; fall back to python3 --version if python fails. require Python 3.6 or newer. do not use version-specific commands like py -3.10.
(optional) run the parameter preview helper before the API call:
python scripts/preview_params.py --url "https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"
for multiple URLs:
python scripts/preview_params.py --parameters-json '[{"url":"https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"},{"url":"https://www.booking.com/hotel/us/example.en-gb.html"}]'
execute the API call script. for a single URL:
python scripts/booking_hotellist.py --url "https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"
for multiple URLs:
python scripts/booking_hotellist.py --parameters-json '[{"url":"https://www.booking.com/hotel/gb/westlands-of-pitlochry.en-gb.html#tab-main"},{"url":"https://www.booking.com/hotel/us/example.en-gb.html"}]'
if the token was provided in conversation (not environment):
python scripts/booking_hotellist.py --token "USER_TOKEN" --url "..."
do not expose the token in user-facing output.
parse the API response. look for task identifiers in this order: task_id, taskId, id, data.task_id, data.id. also extract status or data.status.
report the task ID and status to the user. remind them to view full task details at https://dataify.com/dashboard/.
if single URL vs. multiple URLs: user provides one URL, proceed with single parameter object. user provides or requests multiple URLs, collect all URLs first, confirm batch submission, then submit as JSON array in spider_parameters.
if token not found: stop and guide user to retrieve token from Dataify dashboard. do not retry or assume a default token.
if token provided in conversation: use it for this API call only. separately ask whether to save it for future use (step 5). only save after explicit consent.
if Python not available: output error: Python 3.6+ not found. Install Python or ensure it is in PATH. then stop.
if API call fails with 401/403: token is invalid or expired. ask user to refresh it from https://dataify.com/dashboard/.
if API call fails with 429: rate limit hit. advise user to wait before retrying.
if API call fails with 500+: Dataify backend error. advise user to retry in a few moments or contact Dataify support.
if API response lacks task_id or status: attempt to extract from nested fields (data object). if still missing, output raw response and ask user to check dashboard manually.
if file_name omitted by user: use default {{TasksID}} in the API request.
task_id (or taskId, id, data.task_id, data.id) and status field.task_id (or variant): unique identifier for the scraping taskstatus: task state (e.g., pending, running, completed, failed)data (optional): nested object containing task detailsTask ID: abc123def456)Status: pending)