Wyndham Hotels & Resorts, Inc. (NYSE: WH) is the world's largest hotel franchising company by number of properties, with over 8,300 affiliated hotels and approximately 869,000 rooms across roughly 25 brands in 95+ countries, licensed to more than 6,200 franchisees. Headquartered in Parsippany, New Jersey, its home market is the United States. Wyndham does not operate most of its hotels — it franchises brands (Days Inn, Super 8, Ramada, La Quinta, Microtel, Baymont, Howard Johnson, Travelodge, Wingate, Wyndham, Wyndham Grand, Trademark Collection, TRYP, Dolce, ECHO Suites and others) and sells the demand that flows through them. It sits in the distribution chain as a franchisor and demand aggregator rather than as a distribution platform: inventory reaches buyers through Wyndham's own brand.com sites and Wyndham Rewards, through GDS chain codes under master chain code WR, and through third-party online travel agents, with the central reservation layer supplied by Sabre Hospitality's SynXis CRS under a relationship Sabre publicly renewed in July 2024. There is no travel API: no developer portal, no API documentation, no OpenAPI, and no property, rate, availability, reservation, loyalty or folio surface is machine-readable anywhere. developer., developers., docs. and api. subdomains do not resolve; /developers, /api, /docs, /openapi.json, /swagger.json and /api-docs all return 404, and mcp.wyndhamhotels.com resolves with a valid certificate but serves an Akamai 503 on every path. The Terms of Use (effective 2026-03-12) affirmatively prohibit robots, spiders, meta-searching and automated access, and separately prohibit automated access to Wyndham's AI Search. What a second enrichment round did find on 2026-07-28 is undocumented CMS infrastructure that is nonetheless genuinely live: www.wyndhambusiness.com and development.wyndhamhotels.com both run WordPress on WP Engine and leave the WordPress REST API anonymously readable (309 and 403 registered routes, with JSON Schema available by HTTP OPTIONS), and three WordPress MCP adapter routes are registered across the two estates — one of them, on www.wyndhambusiness.com, bound to a real OAuth 2.1 authorization server with RFC 8414 and RFC 9728 discovery metadata, mandatory PKCE S256 and a single `mcp` scope, returning a standards-correct 401 bearer challenge to anonymous callers. None of it is documented, supported, or usable without a credential Wyndham issues to no third party, and none of it carries hotel data. The integration surface that matters is still reached only through a franchise agreement, a commercial distribution agreement, or Sabre.
Wyndham Hotels & Resorts publishes 3 APIs on the APIs.io network. Tagged areas include Travel, United States, Hospitality, Hotels, and Booking.
Wyndham Hotels & Resorts’ developer surface includes authentication, support, engineering blog, and 33 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
The public WordPress REST API (wp-json) of the Wyndham Hotels & Resorts website at www.wyndhambusiness.com: the route index of the site's content management system, catalogued a...
The public WordPress REST API (wp-json) of the Wyndham Hotels & Resorts website at development.wyndhamhotels.com: the route index of the site's content management system, catalo...
A WordPress MCP adapter is registered on www.wyndhambusiness.com in the `mcp` namespace alongside wp-abilities/v1, and — unlike most WordPress MCP installs — it is bound to a wo...
aid: wyndham-hotels
name: Wyndham Hotels & Resorts
kind: company
description: 'Wyndham Hotels & Resorts, Inc. (NYSE: WH) is the world''s largest hotel franchising company by number of properties,
with over 8,300 affiliated hotels and approximately 869,000 rooms across roughly 25 brands in 95+ countries, licensed to
more than 6,200 franchisees. Headquartered in Parsippany, New Jersey, its home market is the United States. Wyndham does
not operate most of its hotels — it franchises brands (Days Inn, Super 8, Ramada, La Quinta, Microtel, Baymont, Howard Johnson,
Travelodge, Wingate, Wyndham, Wyndham Grand, Trademark Collection, TRYP, Dolce, ECHO Suites and others) and sells the demand
that flows through them. It sits in the distribution chain as a franchisor and demand aggregator rather than as a distribution
platform: inventory reaches buyers through Wyndham''s own brand.com sites and Wyndham Rewards, through GDS chain codes under
master chain code WR, and through third-party online travel agents, with the central reservation layer supplied by Sabre
Hospitality''s SynXis CRS under a relationship Sabre publicly renewed in July 2024. There is no travel API: no developer
portal, no API documentation, no OpenAPI, and no property, rate, availability, reservation, loyalty or folio surface is
machine-readable anywhere. developer., developers., docs. and api. subdomains do not resolve; /developers, /api, /docs,
/openapi.json, /swagger.json and /api-docs all return 404, and mcp.wyndhamhotels.com resolves with a valid certificate but
serves an Akamai 503 on every path. The Terms of Use (effective 2026-03-12) affirmatively prohibit robots, spiders, meta-searching
and automated access, and separately prohibit automated access to Wyndham''s AI Search. What a second enrichment round did
find on 2026-07-28 is undocumented CMS infrastructure that is nonetheless genuinely live: www.wyndhambusiness.com and development.wyndhamhotels.com
both run WordPress on WP Engine and leave the WordPress REST API anonymously readable (309 and 403 registered routes, with
JSON Schema available by HTTP OPTIONS), and three WordPress MCP adapter routes are registered across the two estates — one
of them, on www.wyndhambusiness.com, bound to a real OAuth 2.1 authorization server with RFC 8414 and RFC 9728 discovery
metadata, mandatory PKCE S256 and a single `mcp` scope, returning a standards-correct 401 bearer challenge to anonymous
callers. None of it is documented, supported, or usable without a credential Wyndham issues to no third party, and none
of it carries hotel data. The integration surface that matters is still reached only through a franchise agreement, a commercial
distribution agreement, or Sabre.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: self-serve
trial: false
try_now: false
public: false
label: Self-serve signup
confidence: medium
source:
- authentication
- scopes
- security
generated: '2026-09-02'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/wyndham-hotels.png
url: https://raw.githubusercontent.com/api-evangelist/wyndham-hotels/refs/heads/main/apis.yml
tags:
- Travel
- United States
- Hospitality
- Hotels
- Booking
- Franchising
- Distribution
- Loyalty
- GDS
created: '2026-07-28'
modified: '2026-07-28'
specificationVersion: '0.23'
apis:
- aid: wyndham-hotels:wyndhambusiness-com-website-wordpress-rest
name: Wyndham Hotels & Resorts Website (WordPress REST, www.wyndhambusiness.com)
description: 'The public WordPress REST API (wp-json) of the Wyndham Hotels & Resorts website at www.wyndhambusiness.com:
the route index of the site''s content management system, catalogued as one site surface rather than as separate APIs.'
baseURL: https://www.wyndhambusiness.com/wp-json
tags:
- WordPress
x-surface: platform-generated
properties:
- type: Documentation
url: https://www.wyndhambusiness.com/wp-json
x-platform: wordpress
x-platform-surface: rest
- aid: wyndham-hotels:development-wyndhamhotels-com-website-wordpress-rest
name: Wyndham Hotels & Resorts Website (WordPress REST, development.wyndhamhotels.com)
description: 'The public WordPress REST API (wp-json) of the Wyndham Hotels & Resorts website at development.wyndhamhotels.com:
the route index of the site''s content management system, catalogued as one site surface rather than as separate APIs.'
baseURL: https://development.wyndhamhotels.com/wp-json
tags:
- WordPress
x-surface: platform-generated
properties:
- type: Documentation
url: https://development.wyndhamhotels.com/wp-json
x-platform: wordpress
x-platform-surface: rest
- aid: wyndham-hotels:wyndham-business-mcp-server
name: Wyndham Business WordPress MCP Server (OAuth-gated)
description: A WordPress MCP adapter is registered on www.wyndhambusiness.com in the `mcp` namespace alongside wp-abilities/v1,
and — unlike most WordPress MCP installs — it is bound to a working OAuth 2.1 authorization server. /.well-known/oauth-authorization-server
(RFC 8414) and /.well-known/oauth-protected-resource (RFC 9728) both return HTTP 200 anonymously; the protected resource
names the MCP endpoint explicitly, PKCE S256 is the only code-challenge method, the token endpoint accepts no client authentication,
client_id_metadata_document_supported is true, and the single advertised scope is `mcp`. An anonymous JSON-RPC tools/list
returns 401 mcp_unauthorized with a correct WWW-Authenticate bearer challenge carrying resource_metadata. The surface
genuinely exists and is genuinely not publicly usable — no tool names, descriptions or input schemas can be read without
a credential Wyndham issues to no third party, and no registration endpoint is published. Recorded as a gated surface
rather than a product.
humanURL: https://www.wyndhambusiness.com/wp-json/mcp
baseURL: https://www.wyndhambusiness.com/wp-json/mcp/mcp-oauth-server
tags:
- MCP
- Agents
- WordPress
- Authentication
- Gated
tags_raw:
- MCP
- Agents
- WordPress
- OAuth
- Gated
properties:
- type: MCPServer
url: mcp/wyndham-hotels-mcp.yml
- type: Discovery
url: https://www.wyndhambusiness.com/wp-json/mcp
- type: Authentication
url: authentication/wyndham-hotels-authentication.yml
- type: OAuthScopes
url: scopes/wyndham-hotels-scopes.yml
- type: WellKnown
url: well-known/wyndham-hotels-well-known.yml
x-surface: platform-generated
x-platform: wordpress
x-platform-surface: mcp-plugin
common:
- type: DomainSecurity
url: security/wyndham-hotels-domain-security.yml
- type: Authentication
url: authentication/wyndham-hotels-authentication.yml
- type: OAuthScopes
url: scopes/wyndham-hotels-scopes.yml
- type: WellKnown
url: well-known/wyndham-hotels-well-known.yml
- type: MCPServer
url: mcp/wyndham-hotels-mcp.yml
- type: Conventions
url: conventions/wyndham-hotels-conventions.yml
- type: ErrorCatalog
url: errors/wyndham-hotels-problem-types.yml
- type: DataModel
url: data-model/wyndham-hotels-data-model.yml
- type: Conformance
url: conformance/wyndham-hotels-conformance.yml
- type: Lifecycle
url: lifecycle/wyndham-hotels-lifecycle.yml
- type: DiscoveryDocument
name: Wyndham Business WordPress REST route index
url: discovery/wyndham-hotels-wyndhambusiness-wp-json-root.json
- type: DiscoveryDocument
name: Wyndham Hotel Development WordPress REST route index
url: discovery/wyndham-hotels-development-wp-json-root.json
- type: LLMsTxt
name: wyndhamhotels.com llms.txt (harvested)
url: llms/wyndham-hotels-llms.txt
- type: LLMsTxt
name: wyndhambusiness.com llms.txt (harvested)
url: llms/wyndham-hotels-wyndhambusiness-llms.txt
- type: LLMsTxt
name: development.wyndhamhotels.com llms.txt (harvested)
url: llms/wyndham-hotels-development-llms.txt
- type: Website
url: https://www.wyndhamhotels.com/
- type: CorporateWebsite
url: https://corporate.wyndhamhotels.com/
- type: LinkedIn
url: https://www.linkedin.com/company/wyndhamhotels
- type: Wikipedia
url: https://en.wikipedia.org/wiki/Wyndham_Hotels_%26_Resorts
- type: TermsOfService
url: https://www.wyndhamhotels.com/about-us/terms-of-use-more-info
- type: PrivacyPolicy
url: https://www.wyndhamhotels.com/about-us/privacy-notice-more-info
- type: Support
name: Wyndham Customer Care
url: https://www.wyndhamhotels.com/contact-us
description: Consumer customer-care contact routes and a reservations phone line. There is no developer support channel
and no partner support desk published.
- type: Blog
name: Wyndham Newsroom
url: https://corporate.wyndhamhotels.com/news-media/
- type: LLMSTxt
url: https://www.wyndhamhotels.com/llms.txt
- type: Robots
url: https://www.wyndhamhotels.com/robots.txt
- type: Sitemap
url: https://www.wyndhamhotels.com/sitemap.xml
- type: InvestorRelations
url: https://investor.wyndhamhotels.com/
- type: AnnualReport
name: Wyndham Hotels & Resorts FY2025 Form 10-K
url: https://www.sec.gov/Archives/edgar/data/1722684/000172268426000007/wh-20251231.htm
description: SEC Form 10-K filed 2026-02-19. Source of the franchise-term, royalty and distribution-channel language recorded
in review.yml. Requires a declared User-Agent; returns 403 to a generic browser UA.
- type: Franchising
name: Wyndham Hotel Development
url: https://development.wyndhamhotels.com/
- type: Suppliers
name: Wyndham Supplier Portal
url: https://wyndham.supplierone.co/
description: suppliers.wyndham.com redirects here (third-party SupplierOne platform); procurement onboarding, not an API
surface.
- type: TravelProfessionals
name: Wyndham Hotel Travel Advisors Program
url: https://www.wyndhamhotels.com/content/whg-ecomm-responsive/en-us/whg/about-us/travel-professionals.html
description: Travel-agent program; commission is earned by entering an IATA number on the booking page. No GDS chain codes
or connectivity docs published here.
- type: BusinessTravel
name: Wyndham Business
url: https://www.wyndhambusiness.com/
description: Corporate travel program, including Wyndham Direct centralized booking and billing. Approval-gated; no API
or booking-tool integration published. Also the host of the only live machine-readable surfaces on the estate.
- type: Loyalty
name: Wyndham Rewards
url: https://www.wyndhamhotels.com/wyndham-rewards
- type: GitHubOrganization
url: https://github.com/Wyndham-Hotels-Resorts
description: One public repository (next_gen_hotel_engagement, Python, created 2026-01-08). Loose analysis scripts, no SDK,
no spec, no API client.
- type: Predecessor
name: Wyndham Worldwide
url: https://raw.githubusercontent.com/api-evangelist/wyndham-worldwide/refs/heads/main/apis.yml
description: Wyndham Hotels & Resorts was spun off from Wyndham Worldwide on 2018-05-31; the remaining vacation-ownership
business became Travel + Leisure Co.
- type: Review
url: review.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.