Airbnb Scraper API

# Integrate HasData Airbnb Scraper API

## Task

Add the requested Airbnb search or property-data workflow to this project using HasData Airbnb Scraper API.
Inspect project instructions, the server-side runtime, existing HTTP client, and tests first.
Follow the project's conventions and preserve unrelated code. No new SDK is required.
Implement only the endpoint or workflow needed for the user's task; do not add a full travel platform.
If the task is unclear, ask whether they need search results, property details, or both.
Do not replace the REST integration with an MCP connection or a custom Airbnb scraper.

## References

Read the endpoint documentation before implementing:

- Listing search: https://docs.hasdata.com/apis/airbnb/listing.md
- Property details: https://docs.hasdata.com/apis/airbnb/property.md
- Error handling: https://docs.hasdata.com/api-codes.md
- Documentation index: https://docs.hasdata.com/llms.txt
- Full documentation (fallback): https://docs.hasdata.com/llms-full.txt

Start with the endpoint references. Use `llms.txt` to find additional pages.
Use `llms-full.txt` only when needed; extract relevant sections instead of loading everything into context.
If a `.md` reference is unavailable, try its HTML URL without `.md`.
If it is still unavailable, ask for the missing documentation rather than guessing.

## Optional agent skill

If the official `hasdata` skill is already available, use its relevant guidance.
Otherwise, if this agent supports skills, ask before installing it in this project:

```sh
npx skills add hasdata/agent-skills --skill hasdata
```

Run from the project directory and select the coding agent in use.
The `hasdata-cli` skill is not required. If installation is declined or unsupported, continue with the docs.
Flag conflicts between skill guidance and current API docs rather than guessing.

## Implementation

- Listing search: `GET https://api.hasdata.com/scrape/airbnb/listing`.
- Accept required `checkIn` and a `location`, unless using all four map bounds: `neLat`, `neLng`, `swLat`, and `swLng`. Do not send a partial bounding box.
- Accept `checkOut`, `adults`, `children`, `infants`, and `pets` when relevant. Use agreed future dates and preserve these inputs with saved results.
- Property details: `GET https://api.hasdata.com/scrape/airbnb/property`, with the required Airbnb listing `url`. Do not assume it accepts search dates or guest filters.
- Encode query parameters correctly. Preserve returned JSON: listing `properties` and `pagination`, or the detail `property` object, including available amenities, host details, and disclosures.
- If pagination is needed, accept the returned `nextPageToken`; do not automatically fetch every page.
- Keep price qualifiers and breakdowns intact. Do not infer booked nights, occupancy, rental income, or current availability from a saved listing response.
- Handle timeouts, documented errors, empty searches, and missing optional fields. Do not invent absent prices or amenity values.
- Keep requests server-side. If there is no suitable server-side runtime, discuss options before changing the architecture.

## Credentials

- Implement the integration and mocked tests without requiring a live API key.
- Read `HASDATA_API_KEY` from the project's existing environment or secret store and send it as `x-api-key`.
- If the key is missing before live verification, ask the user to configure it from https://app.hasdata.com/api-keys.
- Never ask the user to paste the key into chat. Check only that it is configured, without printing its value.
- Never put the key in browser code, logs, or version control. Add only a placeholder to the project's example configuration.
- If using a local `.env` file, make sure it is gitignored.
- Send the key only to `https://api.hasdata.com`. Never forward it to documentation, result URLs, or redirects to another origin.

## Verification

- Add mocked tests for parameter validation, query encoding, success, empty searches, missing optional fields, and documented errors. Include a usage example and run local checks.
- Only after explicit user approval and with a configured key, make one live verification request with agreed inputs and valid dates where required. Successful requests consume credits.
- Validate the HTTP status, documented API status, and response structure. An empty result set can be valid.
- Do not automatically repeat paid requests to obtain a nonempty response.
- Report changed files, setup commands, and test results. State separately whether live verification passed, failed, or was skipped.
- Ask before deploying.