Move Home Organisation CIC · OAuth Scopes

Move Home Organisation CIC OAuth Scopes

OAuth 2.0 searched

Move Home Organisation CIC publishes 3 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Move Home Organisation CIC API on a user’s behalf.

Tokens are issued from https://movehome.org/oauth/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 EstatePropertyLettingsProperty SalesAgentsA2AMCPAgent-NativeAgent RegistryNon-ProfitOpen SourceRAIA ProtocolUnited Kingdom
Scopes: 3 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://movehome.org/oauth/token
Flows
clientCredentials

Scopes (3)

ScopeDescriptionFlows
feed.read Read listings, branches, performance and enquiries. clientCredentials
feed.write Upsert and remove listings. clientCredentials
products.write Request portal product activations. clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-09-19'
method: searched
source: openapi/movehome-org-raia-portal-feed-openapi.yaml
docs: https://github.com/MoveHome/MoveHome.Org/blob/main/docs/raia-portal-feed-api.md#2-getting-credentials
token_url: https://movehome.org/oauth/token
summary: >-
  Three OAuth 2.0 scopes, all on the RAIA Portal Feed API's client-credentials flow, declared in the
  OpenAPI's OAuth2ClientCredentials scheme and documented identically in MoveHome's integrator guide. A
  credential is bound to one agent and an ALLOWED set of scopes at issuance; a token request's scope is
  intersected with that set, and omitting scope grants every allowed scope. The agent surfaces (A2A, both
  MCP servers) and the registry API have no scopes because they have no authentication.
schemes:
- name: OAuth2ClientCredentials
  source: openapi/movehome-org-raia-portal-feed-openapi.yaml
  flows:
  - flow: clientCredentials
    tokenUrl: https://movehome.org/oauth/token
    tokenUrl_in_spec: https://feed.example.com/oauth/token
    note: The standard's OpenAPI carries an implementer placeholder; MoveHome's docs and the live 401 (WWW-Authenticate Bearer realm="raia-portal-feed") fix the real issuer. Bound in overlays/movehome-org-raia-portal-feed-overlay.yaml.
  token: HS256 JWT, 1-hour TTL, jti audit-logged
  client_authentication: HTTP Basic or form client_id / client_secret
  description: |-
    Server-to-server OAuth2 client credentials flow. The token endpoint is
    published by the implementer; credentials are issued out-of-band
    during onboarding. Tokens are short-lived Bearer JWTs.
scopes:
- scope: feed.read
  description: Read listings, branches, performance and enquiries.
  grants: [getListing, listBranchListings, getBranchPerformance, listBranchEnquiries, listPremiumListingActivations, getPremiumListingActivation, listFeaturedPropertyActivations, getFeaturedPropertyActivation]
  flows: [clientCredentials]
  sources: [openapi/movehome-org-raia-portal-feed-openapi.yaml, docs §2]
- scope: feed.write
  description: Upsert and remove listings.
  grants: [upsertListing, deleteListing]
  flows: [clientCredentials]
  sources: [openapi/movehome-org-raia-portal-feed-openapi.yaml, docs §2]
- scope: products.write
  description: Request portal product activations.
  grants: [requestPremiumListingActivation, requestFeaturedPropertyActivation]
  flows: [clientCredentials]
  sources: [openapi/movehome-org-raia-portal-feed-openapi.yaml, docs §2]
unscoped:
- {operation: getHealth, note: 'security: [] in the spec; live 200 without a token'}
- {surface: 'A2A https://movehome.org/api/a2a', note: no authentication or scopes}
- {surface: 'MCP https://movehome.org/mcp and /api/registry/mcp', note: no authentication or scopes}
- {surface: 'Registry REST https://movehome.org/api/registry/v1', note: no authentication or scopes}
scope_count: 3

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/movehome-org-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.