REALTOR.ca · OAuth Scopes

REALTOR.ca OAuth Scopes

OAuth 2.0 searched

REALTOR.ca publishes 5 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the REALTOR.ca API on a user’s behalf.

Tokens are issued from https://identity.crea.ca/connect/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Real-EstateCanadaProperty ListingsMLSRESOIDXListing SyndicationPropTechODataRentals
Scopes: 5 Flows: clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://identity.crea.ca/connect/authorize
Token URL
https://identity.crea.ca/connect/token
Flows
clientCredentials

Scopes (5)

ScopeDescriptionFlows
DDFApi_Read Read access to the REALTOR.ca DDF Web API — the Property, Member, Office, OpenHouse and Destination OData resources and their Replication endpoints, restricted to the Destinations entitled to the calling data feed. This is the only scope CREA documents, and the only one a DDF integrator requests. clientCredentials
openid Standard OpenID Connect scope; returns an ID token for interactive flows. authorizationCode, implicit
offline_access Standard OAuth 2.0 scope requesting a refresh token. Not applicable to the documented client_credentials DDF flow. authorizationCode
OfferManagementApi.read.write Read/write access to a CREA offer-management API. Advertised by identity.crea.ca but CREA publishes no documentation, no host and no key-issuance path for it — offerapi.crea.ca and offermanagement-docs.realtor.ca do not resolve. clientCredentials
BoardDataApi.read Read access to a CREA board-data API. Advertised by identity.crea.ca but undocumented — boarddataapi.crea.ca and boarddata-docs.realtor.ca do not resolve. clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-07-26'
method: searched
source: >-
  https://identity.crea.ca/.well-known/openid-configuration (HTTP 200, anonymous) — the
  `scopes_supported` array — cross-read against the "API Access Tokens" table in the DDF Web API
  documentation
docs: https://ddfapi-docs.realtor.ca/#section/Authorization
note: >-
  derive-oauth-scopes.py returned zero because neither harvested OpenAPI declares an oauth2
  securityScheme. The scopes below are SEARCHED: CREA's authorization server publishes them
  anonymously in its discovery document, and the documentation names exactly one — DDFApi_Read —
  as the scope a DDF data feed requests. The other three are advertised by the same authorization
  server for CREA products that have no public documentation and no resolvable host; they are
  recorded as observed-but-undocumented, and no endpoint was invented for them.
schemes:
- name: DDFApiOAuth2
  source: https://identity.crea.ca/.well-known/openid-configuration
  flows:
  - flow: clientCredentials
    tokenUrl: https://identity.crea.ca/connect/token
    authorizationUrl: https://identity.crea.ca/connect/authorize
scopes:
- scope: DDFApi_Read
  description: >-
    Read access to the REALTOR.ca DDF Web API — the Property, Member, Office, OpenHouse and
    Destination OData resources and their Replication endpoints, restricted to the Destinations
    entitled to the calling data feed. This is the only scope CREA documents, and the only one a
    DDF integrator requests.
  flows: [clientCredentials]
  documented: true
  sources: [https://ddfapi-docs.realtor.ca/#section/Authorization]
- scope: openid
  description: Standard OpenID Connect scope; returns an ID token for interactive flows.
  flows: [authorizationCode, implicit]
  documented: false
  sources: [https://identity.crea.ca/.well-known/openid-configuration]
- scope: offline_access
  description: Standard OAuth 2.0 scope requesting a refresh token. Not applicable to the documented client_credentials DDF flow.
  flows: [authorizationCode]
  documented: false
  sources: [https://identity.crea.ca/.well-known/openid-configuration]
- scope: OfferManagementApi.read.write
  description: >-
    Read/write access to a CREA offer-management API. Advertised by identity.crea.ca but CREA
    publishes no documentation, no host and no key-issuance path for it — offerapi.crea.ca and
    offermanagement-docs.realtor.ca do not resolve.
  flows: [clientCredentials]
  documented: false
  undocumented_product: true
  sources: [https://identity.crea.ca/.well-known/openid-configuration]
- scope: BoardDataApi.read
  description: >-
    Read access to a CREA board-data API. Advertised by identity.crea.ca but undocumented —
    boarddataapi.crea.ca and boarddata-docs.realtor.ca do not resolve.
  flows: [clientCredentials]
  documented: false
  undocumented_product: true
  sources: [https://identity.crea.ca/.well-known/openid-configuration]
summary:
  total: 5
  documented: 1
  granularity: >-
    Coarse. One read scope covers the entire national listing pool; entitlement is enforced not by
    scope but by the `destinationid` claim bound to the credential — a feed sees only the
    Destinations a member or broker owner linked to it. There is no per-resource, per-board or
    per-field scope.

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • 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 scope set
curl "https://apis.io/api/v1/scopes/realtor-ca-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

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.