Get Hotels detail · Hotels API
Run one live Hotels detail lookup for a hotel id from /hotels/search and receive the full profile, including class rating, address, phone, description, guest reviews, images, and prices.
Using ChatGPT, Claude Code or another client? See the setup steps
curl -X POST https://api.unifapi.com/hotels/info \ -H "Authorization: Bearer $UNIFAPI_KEY" \ -H "Content-Type: application/json"
This operation is part of the Hotels API in the travel category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Hotels public data alongside maps, local listings or events, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Track what is moving on Hotels for trend-discovery and content-planning agents.
- Compare live Hotels signals with other public social data sources available through the same MCP and HTTP surface.
- Give an AI agent a stable Hotels data source without building a per-platform integration.
- Normalize Hotels responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
- The operation has a 10 credits ($0.01) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 10 credits ($0.01) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields in the data object
A successful Get Hotels detail call returns one data object with these fields (12 of 15 shown — the docs list the full schema).
- hotel_identifierstring
- locationstring
- Search location echoed from the request.
- languagestring
- observed_atstring
- search_urlstring
- titlestring
- starsinteger
- Hotel class rating, 1-5.
- stars_descriptionstring
- addressstring
- phonestring
- aboutobject
- Hotel description, address, website, and amenities when present.
- placeobject
- Hotel location details when present.
More Hotels operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.