# Get property details

Returns one hotel or restaurant. Requires `geo_id`, `location_id` and `name_slug` from a `/tripadvisor/list` row — do not build these by hand. `data` is null when no property page was served.

- Platform: TripAdvisor
- Request: `GET https://api.toolzerhub.com/v1/tripadvisor/detail`
- Auth: `x-api-key` header
- Cost: 1 credit per successful request. Failed requests are not billed.
- Page: https://docs.toolzerhub.com/reference/tripadvisor/detail/get-trip-advisor-detail

| Parameter | In | Required | Type | Description |
| --- | --- | --- | --- | --- |
| `geo_id` | query | yes | integer | The g id from a /tripadvisor/list row, not invented. |
| `location_id` | query | yes | integer | The d id from the same list row. |
| `kind` | query | no | enum: hotels, restaurants | Must match the kind the list row came from. Default: hotels. |
| `name_slug` | query | yes | string | The segment after -Reviews- in a list row's url, e.g. from HotelHighlight-g60713-d115623-Reviews-Chancellor_Hotel_on_Union_Square-San_Francisco_California.html. Take it from a /tripadvisor/list row rather than building one — a hand-built id redirects to an unrelated property. |

## Example request

```bash
curl "https://api.toolzerhub.com/v1/tripadvisor/detail?geo_id=<geo_id>&location_id=<location_id>&name_slug=<name_slug>" \
  -H "x-api-key: $TOOLZERHUB_API_KEY"
```

Success responses are wrapped as `{ "data": ... }`. Errors return `{ "error": { "code", "status", "message", "retryable", "details" } }`. See https://docs.toolzerhub.com/docs/responses-and-errors.