# RE/MAX

> RE/MAX Holdings, Inc. (NYSE: RMAX) is one of the world's largest real estate brokerage franchisors, licensing the RE/MAX brand across more than 110 countries. It is a consumer of MLS data rather than a publisher of it. RE/MAX Holdings publishes no developer portal, no API program and no machine-readable API contract in the United States. The only publicly documented RE/MAX APIs belong to RE/MAX Europe: a Datahub franchise-operations API and a Listings API, both documented as public Postman collections, both OAuth 2.0, and both credential-gated to RE/MAX regional master franchisees, offices and their vendors. Documented, but not self-serve.

This file was generated by API Evangelist from the RE/MAX provider repo. It describes what is verifiable as of 2026-07-26; the absences below are recorded findings, not omissions.

## APIs

- [RE/MAX Europe Datahub API](https://apidocs.datahub.remax.eu/): Franchise operations - offices, persons, RE/MAX Titles (role records), teams, regions and monthly GCI / transaction / volume reporting. Base URL https://api.datahub.remax.eu/external. OAuth 2.0 against https://oauth.datahub.remax.eu, token passed as an access_token query parameter. 52 documented operations.
- [RE/MAX Europe Listings API (staging)](https://listingsapi-test.datahub.remax.eu/): Property listings and listing images across RE/MAX European regions, plus listing entry logs and region/office/agent lookups. Only the STAGING environment is documented; base URL https://listing-api-remaxeu.bwscloud.tech/api/v1. Writes are queued and validated after the response. 35 documented operations.
- [RE/MAX Europe Site API (WordPress REST)](https://www.remax.eu/wp-json/): The remax.eu marketing site exposes the WordPress REST API anonymously - 42 namespaces, 791 routes, including public reads of posts, pages, media, events, regions and newsroom content. A platform default rather than a RE/MAX product, but the only anonymously callable, self-describing RE/MAX endpoint family.

## Access

- Credentials are issued by RE/MAX Europe to regional master franchisees, offices and their vendors. There is no signup form, no key request page and no published pricing. The Datahub documentation ships the client_id placeholder "Ask_REU", which is the entire onboarding process.
- The United States surface has nothing to apply for: no developer program exists. api.remax.com is a dangling CNAME to a decommissioned booj host; developer.remax.com, developers.remax.com and docs.remax.com are wildcard DNS entries pointing at the kvCORE agent-website platform.

## Specs and artifacts

- [Datahub Postman collection](collections/re-max-eu-datahub-api.postman_collection.json): the published contract, harvested verbatim.
- [Listings Postman collection](collections/re-max-eu-listings-api.postman_collection.json): the published staging contract, harvested verbatim with an embedded staging token redacted.
- [Authentication profile](authentication/re-max-authentication.yml): OAuth 2.0 authorization code, token in the query string, no OIDC discovery, no published scopes.
- [API conventions](conventions/re-max-conventions.yml): pagination, identifiers, versioning, deferred validation, and the absence of idempotency.
- [Error codes](errors/re-max-error-codes.yml): the live error envelope and the codes observed anonymously (4007 Login parameter Required, 4004 Invalid or expired Session/Token).
- [Data model](data-model/re-max-data-model.yml): Region, Office, Person, Title, Team, Listing, ListingImage, ListingEntryLog and how they relate.
- [Conformance](conformance/re-max-conformance.yml): what RE/MAX conforms to and, more importantly, what it does not - no RESO Web API, no Data Dictionary, no OData, no UPI, no RFC 9457.
- [Lifecycle](lifecycle/re-max-lifecycle.yml): no versioning policy on Datahub, no deprecation policy, no SLA, no status page.
- [Sandbox](sandbox/re-max-sandbox.yml): the staging Listings environment and the published test identifiers.
- [MCP](mcp/re-max-mcp.yml): an auth-gated WordPress MCP Adapter endpoint on remax.eu; no API-program MCP server.
- [Well-known](well-known/re-max-well-known.yml): every /.well-known probe and the WordPress route catalog.
- [Domain security](security/re-max-domain-security.yml): TLS, HSTS, DNSSEC, CAA, SPF and DMARC posture.

## No OpenAPI

There is no OpenAPI, Swagger, GraphQL schema, AsyncAPI document or OData $metadata anywhere in the RE/MAX estate. Every candidate path on both API hosts, both documentation hosts and the consumer portal was probed and returned 404, a 400 auth-gate response, or an nginx/WAF block. Do not assume a generated client exists; there is none.

## RESO posture

RE/MAX is a RESO Class D member (Brokers, Agents and Appraisers) with a seat on the RESO Board of Directors, and is NOT in the RESO certification directory of certified data providers. It publishes no RESO Web API, no Data Dictionary mapping and no Universal Property Identifier. The listing schema is proprietary: listingId, offerType, noOfBedrooms, buildingSize, energyRating where RESO would use ListingKey, PropertyType, BedroomsTotal, LivingArea.

## Company

- [RE/MAX (US)](https://www.remax.com/)
- [RE/MAX Europe](https://www.remax.eu/)
- [Newsroom](https://news.remax.com/)
- [Investor relations](https://investors.remaxholdings.com/)
- [RE/MAX Europe llms.txt](https://www.remax.eu/llms.txt): the provider's own llms.txt, saved verbatim at llms/re-max-eu-site-llms.txt.