Wyndham URL to Hotel ID API
Resolve a public Wyndham hotel URL to its numeric property ID.
Copy for your AI agent
Paste into Claude, ChatGPT, Cursor or Copilot — endpoint, parameters, response fields and a curl example in Markdown.
Overview
Resolve a URL to a property ID
StayAPI reads the hotel slug from the URL and resolves it to Wyndham's numeric property ID.
Use this endpoint when you have a canonical wyndhamhotels.com
URL but need the numeric property_id accepted by
Wyndham Rooms.
Wyndham Search
also returns the same identifier.
Endpoint URL
Authenticate with X-API-Key: YOUR_API_KEY.
Query parameter
| Parameter | Type | Required | Rules |
|---|---|---|---|
| url | URL string | Yes |
HTTP or HTTPS URL on wyndhamhotels.com or a subdomain.
It must contain a hotel-specific slug, for example
/laquinta/forsyth-georgia/la-quinta-forsyth/overview.
|
Response schema
url: normalized input URL with a lowercase host and no query string or fragment.property_id: numeric Wyndham identifier used by Rooms.nameandbrand_code: nullable property metadata.
Errors and limitations
Errors follow RFC 7807 Problem Details with provider: "wyndham",
product: "url-to-id", the supplied provided_url,
and a correlation_id.
400 INVALID_URL: invalid scheme or non-Wyndham host.400 PROPERTY_SLUG_NOT_FOUND: valid Wyndham host without a hotel slug.404 PROPERTY_NOT_FOUND: Wyndham has no property matching the slug.502 UPSTREAM_ERROR: Wyndham could not complete the lookup or returned an ambiguous result.
This resolver accepts canonical Wyndham hotel URLs, not city pages or free-form hotel names. It is not paginated or cached.