RE/MAX website screenshot

RE/MAX

RE/MAX Holdings, Inc. (NYSE: RMAX, SIC 6531, Denver, Colorado) is one of the world's largest real estate brokerage franchisors, licensing the RE/MAX brand to independently owned and operated brokerages across more than 110 countries and territories, and franchising mortgage brokerages in the United States under the Motto Mortgage brand with loan processing through wemlo. Its home market is the United States, where it sits in the value chain as a franchisor and consumer portal operator rather than as a data owner: the listing content behind remax.com is licensed from roughly 500 local Multiple Listing Services under IDX and syndication agreements, so RE/MAX is a consumer of MLS data, not a publisher of it. Its API posture reflects that position honestly. RE/MAX is a RESO Class D member (Brokers, Agents and Appraisers) and holds a seat on the RESO Board of Directors, but it does not appear in the RESO certification directory of certified data providers and publishes no RESO Web API, no OData $metadata document and no Universal Property Identifier surface. In the United States there is no developer portal, no published API program and no machine-readable contract of any kind; developer.remax.com, developers.remax.com and docs.remax.com are only wildcard DNS entries pointing at the kvCORE agent website platform, and api.remax.com is a dangling CNAME to a decommissioned booj host that no longer resolves. The only real, publicly documented RE/MAX API surface belongs to RE/MAX Europe, whose Datahub franchise-operations API and Listings API are published as public Postman documentation with OAuth 2.0 authentication, but whose credentials are issued only to RE/MAX regional master franchisees, offices and their vendors — documented, but not self-serve. The only anonymously callable, self-describing RE/MAX endpoint family found anywhere in the estate is the WordPress REST API on the RE/MAX Europe marketing site (remax.eu/wp-json, 42 namespaces and 791 routes), which also exposes an auth-gated Model Context Protocol endpoint via the WordPress MCP Adapter — a CMS surface rather than an API product, but the closest thing to agent-accessible RE/MAX infrastructure that exists today.

RE/MAX publishes 2 APIs on the APIs.io network: Europe Datahub API and Europe Listings API. Tagged areas include Real-Estate, United States, Brokerage, Property Listings, and MLS.

RE/MAX’s developer surface includes authentication, sandbox, engineering blog, documentation, and 21 more developer resources.

18.7/100 emerging ▬ flat Agent 10/100 agent aware library Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
3 APIs 1 MCP Servers
Real-EstateUnited StatesBrokerageProperty ListingsMLSRESOIDXPropTechFranchisingMortgageRentals

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Securities & Market Data regime (on an ambiguous tag, where no other regime matched), 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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/re-max: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

RE/MAX Europe Datahub API

The RE/MAX Europe Datahub API is the franchise-operations API behind the RE/MAX EU Datahub application. It exposes offices, persons, RE/MAX Titles (the agent/broker role records...

RE/MAX Europe Listings API

The RE/MAX Europe Listings API is used in conjunction with the RE/MAX EU Datahub application to add, update, retrieve and delete property listing data and listing images across ...

RE/MAX Europe Site API (WordPress REST)

The RE/MAX Europe marketing site at remax.eu runs WordPress and exposes the WordPress REST API anonymously at /wp-json/. The route descriptor published there is the only self-de...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

RE/MAX MCP Server

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Re Max Authentication

oauth2 · 3 schemes

SECURITY

Re Max Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Commercial 1

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: re-max
url: https://raw.githubusercontent.com/api-evangelist/re-max/refs/heads/main/apis.yml
name: RE/MAX
kind: company
description: 'RE/MAX Holdings, Inc. (NYSE: RMAX, SIC 6531, Denver, Colorado) is one of the world''s largest real estate brokerage
  franchisors, licensing the RE/MAX brand to independently owned and operated brokerages across more than 110 countries and
  territories, and franchising mortgage brokerages in the United States under the Motto Mortgage brand with loan processing
  through wemlo. Its home market is the United States, where it sits in the value chain as a franchisor and consumer portal
  operator rather than as a data owner: the listing content behind remax.com is licensed from roughly 500 local Multiple Listing
  Services under IDX and syndication agreements, so RE/MAX is a consumer of MLS data, not a publisher of it. Its API posture
  reflects that position honestly. RE/MAX is a RESO Class D member (Brokers, Agents and Appraisers) and holds a seat on the
  RESO Board of Directors, but it does not appear in the RESO certification directory of certified data providers and publishes
  no RESO Web API, no OData $metadata document and no Universal Property Identifier surface. In the United States there is
  no developer portal, no published API program and no machine-readable contract of any kind; developer.remax.com, developers.remax.com
  and docs.remax.com are only wildcard DNS entries pointing at the kvCORE agent website platform, and api.remax.com is a dangling
  CNAME to a decommissioned booj host that no longer resolves. The only real, publicly documented RE/MAX API surface belongs
  to RE/MAX Europe, whose Datahub franchise-operations API and Listings API are published as public Postman documentation
  with OAuth 2.0 authentication, but whose credentials are issued only to RE/MAX regional master franchisees, offices and
  their vendors — documented, but not self-serve. The only anonymously callable, self-describing RE/MAX endpoint family found
  anywhere in the estate is the WordPress REST API on the RE/MAX Europe marketing site (remax.eu/wp-json, 42 namespaces and
  791 routes), which also exposes an auth-gated Model Context Protocol endpoint via the WordPress MCP Adapter — a CMS surface
  rather than an API product, but the closest thing to agent-accessible RE/MAX infrastructure that exists today.'
deliveryModel:
  model: library
  open_source: false
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: partner-only
  trial: false
  try_now: false
  public: false
  label: Partner-only · Franchise/vendor credentials required
  confidence: high
  source:
  - collections
  - authentication
  generated: '2026-07-26'
  method: manual
image: https://remax.eu/wp-content/uploads/2026/03/REMAX-Balloon-RGB.svg
tags:
- Real-Estate
- United States
- Brokerage
- Property Listings
- MLS
- RESO
- IDX
- PropTech
- Franchising
- Mortgage
- Rentals
tags_raw:
- Real Estate
- United States
- Brokerage
- Property Listings
- MLS
- RESO
- IDX
- PropTech
- Franchising
- Mortgage
- Rentals
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.23'
apis:
- aid: re-max:re-max-eu-datahub-api
  name: RE/MAX Europe Datahub API
  description: The RE/MAX Europe Datahub API is the franchise-operations API behind the RE/MAX EU Datahub application. It
    exposes offices, persons, RE/MAX Titles (the agent/broker role records), teams, regions and monthly GCI / transaction
    / volume reporting to RE/MAX regional master franchisees and their vendors. It is a proprietary REST contract — it carries
    no RESO Data Dictionary fields, no OData surface and no Universal Property Identifier. Authentication is OAuth 2.0 against
    https://oauth.datahub.remax.eu, with the resulting token passed as an access_token query parameter; the published Postman
    documentation carries the client_id placeholder "Ask_REU", confirming credentials are handed out by RE/MAX Europe rather
    than self-served. Documentation is public; access is not.
  humanURL: https://apidocs.datahub.remax.eu/
  baseURL: https://api.datahub.remax.eu/external
  tags:
  - Franchising
  - Offices
  - Agents
  - Team
  - Reporting
  - Europe
  tags_raw:
  - Franchising
  - Offices
  - Agents
  - Teams
  - Reporting
  - Europe
  properties:
  - type: Documentation
    url: https://apidocs.datahub.remax.eu/
  - type: PostmanCollection
    url: collections/re-max-eu-datahub-api.postman_collection.json
  - type: Authentication
    url: https://oauth.datahub.remax.eu/authorize
- aid: re-max:re-max-eu-listings-api
  name: RE/MAX Europe Listings API
  description: The RE/MAX Europe Listings API is used in conjunction with the RE/MAX EU Datahub application to add, update,
    retrieve and delete property listing data and listing images across RE/MAX European regions. It exposes listings, listing
    images, listing entry logs, regions, offices and agents, plus unauthenticated-looking convenience reads for listing countries
    and cities by country. Writes go through a queue with deferred validation. Like the Datahub API it is a proprietary REST
    schema with no RESO Data Dictionary alignment, no OData $metadata and no UPI. Authentication is OAuth 2.0 with the token
    supplied as an access_token query parameter. The only public documentation RE/MAX Europe publishes is for the STAGING
    environment, whose endpoints run on a third-party host (bwscloud.tech); no production base URL is published.
  humanURL: https://listingsapi-test.datahub.remax.eu/
  baseURL: https://listing-api-remaxeu.bwscloud.tech/api/v1
  tags:
  - Property Listings
  - Image
  - Regions
  - Agents
  - Europe
  - Staging
  tags_raw:
  - Property Listings
  - Images
  - Regions
  - Agents
  - Europe
  - Staging
  properties:
  - type: Documentation
    url: https://listingsapi-test.datahub.remax.eu/
  - type: PostmanCollection
    url: collections/re-max-eu-listings-api.postman_collection.json
  - type: Sandbox
    url: sandbox/re-max-sandbox.yml
- aid: re-max:re-max-eu-site-api
  name: RE/MAX Europe Site API (WordPress REST)
  description: 'The RE/MAX Europe marketing site at remax.eu runs WordPress and exposes the WordPress REST API anonymously
    at /wp-json/. The route descriptor published there is the only self-describing, machine-readable, publicly callable contract
    found anywhere in the RE/MAX estate: 42 namespaces and 791 routes, each with its methods and argument definitions. Public
    content reads (posts, pages, media, search, events, regions, newsroom and people custom post types) return 200 to an anonymous
    caller; everything privileged returns 401 rest_forbidden, including the WordPress Abilities registry and the two MCP tool
    surfaces installed on the site. This is a content-management platform default rather than a RE/MAX API product, and it
    is catalogued as such — but it is real, it is reachable, and it is where RE/MAX''s only Model Context Protocol endpoint
    lives.'
  humanURL: https://www.remax.eu/wp-json/
  baseURL: https://www.remax.eu/wp-json/wp/v2
  tags:
  - Content
  - WordPress
  - MCP
  - Europe
  - Marketing
  properties:
  - type: APICatalog
    url: well-known/re-max-eu-wp-json.json
  - type: MCPServer
    url: mcp/re-max-mcp.yml
common:
- type: DomainSecurity
  url: security/re-max-domain-security.yml
- type: DeveloperPortal
  url: https://apidocs.datahub.remax.eu/
- type: Postman
  url: https://apidocs.datahub.remax.eu/
- type: PrivacyPolicy
  url: https://www.remax.eu/privacy-policy/
- type: Authentication
  url: authentication/re-max-authentication.yml
- type: Conventions
  url: conventions/re-max-conventions.yml
- type: ErrorCatalog
  url: errors/re-max-error-codes.yml
- type: Lifecycle
  url: lifecycle/re-max-lifecycle.yml
- type: Conformance
  url: conformance/re-max-conformance.yml
- type: DataModel
  url: data-model/re-max-data-model.yml
- type: Packages
  url: packages/re-max-packages.yml
- type: Sandbox
  url: sandbox/re-max-sandbox.yml
- type: MCPServer
  url: mcp/re-max-mcp.yml
- type: WellKnown
  url: well-known/re-max-well-known.yml
- type: APICatalog
  url: well-known/re-max-eu-wp-json.json
- type: LLMsTxt
  url: llms/re-max-llms.txt
- type: LLMsTxt
  url: llms/re-max-eu-site-llms.txt
- type: AgentSkill
  url: skills/_index.yml
- type: Website
  url: https://www.remax.com/
- type: Website
  url: https://www.remax.eu/
- type: Blog
  url: https://news.remax.com/
- type: InvestorRelations
  url: https://investors.remaxholdings.com/
- type: LinkedIn
  url: https://www.linkedin.com/company/remax
- type: Documentation
  url: https://apidocs.datahub.remax.eu/
- type: Authentication
  url: https://oauth.datahub.remax.eu/token
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/re-max"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/re-max/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/re-max/evidence"

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.

A second provider on the same verified email joins the account you already have.