Landmark Information Group · OAuth Scopes

Landmark Information Group OAuth Scopes

OAuth 2.0 derived

Landmark Information Group uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://lmkmaster.eu.auth0.com/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 EstateUnited KingdomPropTechProperty DataConveyancingLand RegistryGeospatialValuationAnti-Money LaunderingPlanning DataMortgage

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://lmkmaster.eu.auth0.com/oauth/token

Flows
clientCredentials

Scopes (0)

Landmark Information Group implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-26'
method: derived
source: openapi/landmark-information-conveyancing-experience-api-openapi.yml
schemes:
- name: BearerAuth
  source: openapi/landmark-information-conveyancing-experience-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://lmkmaster.eu.auth0.com/oauth/token
  description: |-
    OAuth 2.0 client credentials. Request an access token from the token endpoint for your
    environment, then send it as a bearer token on every request. See **Authentication** for details.
scopes: []
notes: >-
  Landmark declares an OAuth 2.0 client-credentials scheme in the Conveyancing Experience API but
  publishes an empty scopes map, and no scope or permission reference page exists on the public
  documentation portal. Authorisation is carried by entitlements attached to the onboarded account
  and audience rather than by OAuth scopes - a 403 with code 40300/40301 ("Invalid Entitlement" /
  "No Entitlement") is how the platform signals an unauthorised operation. See
  authentication/landmark-information-authentication.yml for the working model.