generated: '2026-09-17'
method: searched
source: https://docs.mlsgrid.com/api-documentation/api-version-2.0.md
versioning:
  scheme: uri-path
  current: v2
  base_url: https://api.mlsgrid.com/v2/
  docs: https://docs.mlsgrid.com/api-documentation/api-version-2.0.md
  note: >-
    Version 2.0 is described as "the main location of the API Service for now and the future". No
    prior-version sunset schedule and no version negotiation header are documented.
deprecation:
  policy_url: null
  policy_published: false
  sunset_header: false
  deprecation_header: false
  practice: >-
    Deprecation is handled per originating MLS through dated release notices published on
    docs.mlsgrid.com ahead of the effective date — e.g. "NWMLS: Upcoming Changes to Fields"
    (2025-03-05) announced legacy fields deprecated. There is no written deprecation policy page,
    no RFC 8594 Sunset/Deprecation header support, and no stated minimum notice period.
  evidence: https://docs.mlsgrid.com/recent-releases/nwmls-upcoming-changes-to-fields.md
data_retention:
  deleted_records: >-
    Records flagged MlgCanView false must be deleted from the consumer's data store and are removed
    from the feed entirely after 7 days.
  source: https://docs.mlsgrid.com/api-documentation/api-version-2.0.md
sla:
  url: null
  uptime_target: null
  published: false
status_page:
  public: false
  url: null
  probed:
  - {url: 'https://status.mlsgrid.com/', status: 0, note: does not resolve, checked: '2026-09-17'}
  - {url: 'https://www.mlsgrid.com/status', status: 404, checked: '2026-09-17'}
  - {url: 'https://mlsgrid.statuspage.io/', status: 302, note: 'unclaimed subdomain - redirects to the statuspage.io marketing site, not an MLS Grid status page', checked: '2026-09-17'}
  member_only_equivalent: >-
    An "MLS Import Status" screen inside the MLS Grid web application (app.mlsgrid.com) shows the
    latest import status and freshness metric for each MLS. It is behind the member login, so there
    is no publicly reachable status page.
freshness:
  import_policy: >-
    MLS Grid checks each member MLS for changes every minute unless the MLS restricts it, and tracks
    time-to-availability per MLS.
  real_time: false
  note: >-
    "We do not support real time data access at this time. Our service provides the data through a
    data replication process." Consumers poll on a ModificationTimestamp watermark.
release_notes:
  url: https://docs.mlsgrid.com/
  artifact: changelog/mlsgrid-changelog.yml
deprecated_operations: []
probed_on: '2026-07-26'
infrastructure_migrations:
- date: '2026-09-08'
  title: Media delivery migrated off Amazon AWS
  announced: '2026-08-04'
  notice_days: 35
  breaking: true
  detail: >-
    Media moved from Amazon S3/CloudFront to media.mlsgrid.com. New MediaURLs are signed, single-use
    and expire one hour after generation; S3 bucket-to-bucket transfer was withdrawn outright and
    CloudFront consumers had to repoint at the MLS Grid-operated CDN. This is the clearest example of
    how MLS Grid actually retires a capability: a dated notice in the documentation with roughly five
    weeks of warning and repeated email reminders, in the absence of any written deprecation policy
    or RFC 8594 header support.
  url: https://docs.mlsgrid.com/releases/upcoming-changes-to-media-delivery-migration-away-from-amazon-aws.md
- date: '2026-06-01'
  title: Media downloads must send the access token as User-Agent
  breaking: true
  detail: Any other User-Agent may be denied media access from 2026-06-01.
  url: https://docs.mlsgrid.com/recent-releases/changes-to-mls-grid-media-access.md
reprobed_on: '2026-09-17'