# National Association of REALTORS (NAR) > The largest trade association in the United States, representing roughly one million members across > residential and commercial real estate. NAR is the industry body that sits above the roughly 500 local > Multiple Listing Services and, through MLS Policy Statement 7.90, requires association-owned MLSs to > implement the RESO Data Dictionary and the RESO Web API. NAR mandates that standard rather than > operating it. Its own production API is REALTORS M1 - the members-first engagement system replacing > NRDS - whose external gateway is a live, HTTP-Basic-authenticated REST API over member, office, > association and data-extract records. NAR publishes the Swagger 2.0 definition and a Postman collection > openly on GitHub, but issues credentials only under a partner relationship. Generated by API Evangelist from https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/apis.yml No /llms.txt is published on any NAR host (probed 2026-07-26, HTTP 404). ## Key facts for agents - Access is partner-only. There is no self-serve sign-up, no developer portal, no pricing page and no public credential issuance on any NAR host. NAR supplies HTTP Basic credentials directly to external association management system (AMS) vendors and NAR partners, separately for test and production. - The API host is live: https://m1gateway.realtor redirects to https://nar.m1gateway.realtor and answers 401 with an empty body for every path, including /.well-known/*. - The data NAR mandates be exposed over the RESO Web API - MLS listing data - is not NAR's to grant. Access runs through an individual MLS via membership, an IDX or VOW agreement, a broker or agent sponsorship, or a reseller (Bridge, Trestle, MLS Grid, Spark). - NAR holds no RESO certification of its own; it operates no MLS. - M1 Gateway records are membership PII. Write operations move real REALTOR membership, dues, education and Code of Ethics state. ## APIs - [REALTORS M1 Gateway External API](https://github.com/NationalAssociationOfRealtors/M1-Developer-Guide-Supplemental-Docs): 64 paths, 88 operations under /ext/ over Association, Member (and ~20 member sub-record types), Office and Data Extract resources. Base URL https://m1gateway.realtor. HTTP Basic auth. ## Specs - [OpenAPI (Swagger 2.0)](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/openapi/nar-m1-gateway-external-openapi.json): harvested verbatim from NAR's public repository. - [Postman collection](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/collections/nar-m1-gateway-external.postman_collection.json): NAR's own AMS reference collection, 88 requests, with the published error table and PATCH rules. ## Artifacts - [Authentication](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/authentication/nar-authentication.yml): HTTP Basic, single global scheme. - [Conventions](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/conventions/nar-conventions.yml): test/replace JSON Patch pattern, no pagination, no idempotency key, null vs empty string rules. - [Error codes](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/errors/nar-error-codes.yml): 400/401/403/404/500 with the FieldValidationErrors envelope. - [Rate limits](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/rate-limits/nar-rate-limits.yml): undocumented but live X-Rate-Limit-* headers. - [Data model](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/data-model/nar-data-model.yml): member-centric entity graph derived from the 99 Swagger definitions. - [Examples](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/examples/nar-m1-gateway-external-examples.yml): request payloads from NAR's collection (fake sample data by NAR's own statement). - [Lifecycle](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/lifecycle/nar-lifecycle.yml): v1, no deprecation policy, no status page, no changelog. - [Sandbox](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/sandbox/nar-sandbox.yml): separate test environment exists but is not published or self-serve. - [Conformance](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/conformance/nar-conformance.yml): Swagger 2.0, RFC 6902 JSON Patch, HTTP Basic; not OData, not RESO, no RFC 9457. - [Agentic access](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/agentic-access/nar-agentic-access.yml): recommended x-agentic-access contracts for all 88 operations. - [Agent skills](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/skills/_index.yml): packaged operating instructions for the marquee M1 flows. - [MCP candidate](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/mcp/nar-mcp.yml): derived candidate tool list - no MCP server is published by NAR. - [Packages](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/packages/nar-packages.yml): no current SDK; only 2015-era CRT RETS packages. - [Domain security](https://raw.githubusercontent.com/api-evangelist/nar/refs/heads/main/security/nar-domain-security.yml): TLS/HSTS/SPF/DMARC probe results. ## Docs - [REALTORS M1 (association executives)](https://www.nar.realtor/ae/manage-your-association/realtors-m1-members-first-engagement-system) - [M1 Developer Guide Supplemental Docs (GitHub)](https://github.com/NationalAssociationOfRealtors/M1-Developer-Guide-Supplemental-Docs) - [MLS Policy Statement 7.90 - RESO mandate](https://www.nar.realtor/handbook-on-multiple-listing-policy/operational-issues-section-12-real-estate-transaction-standards-rets-policy-statement-790) - [Real Estate Transaction Standards (RETS) Web API policy](https://www.nar.realtor/about-nar/policies/mls-policy/real-estate-transaction-standards-rets-web-api) - [Real Estate Transaction Standards overview](https://www.nar.realtor/real-estate-transaction-standards-rets) - [Research and Statistics](https://www.nar.realtor/research-and-statistics) ## Not available - No AsyncAPI, webhooks, callbacks or event surface. Change delivery is pull-based through DataExtractRequest and DataExtractSchedule. - No GraphQL. No gRPC. No MCP server. No CLI. No embeddable components. No client SDKs. - No status page, changelog, deprecation policy, SLA, security.txt, vulnerability disclosure programme, trust centre, pricing or open data API.