RICS (Royal Institution of Chartered Surveyors)

aid: rics
url: https://raw.githubusercontent.com/api-evangelist/rics/refs/heads/main/apis.yml
name: RICS (Royal Institution of Chartered Surveyors)
kind: company
description: 'RICS, the Royal Institution of Chartered Surveyors, is the British royal-chartered professional body founded
  in London in 1868 that qualifies, regulates and sets standards for surveyors, valuers and built-environment professionals
  worldwide, with the United Kingdom as its home market. In the property value chain it sits on the professional and valuation
  side rather than the listings side: it writes the RICS Valuation - Global Standards (the Red Book, incorporating IVS), the
  RICS Home Survey Standard, RICS Property Measurement / IPMS, ICMS, ILMS and the Rules of Conduct, it regulates roughly 12,000
  RICS-regulated firms, and it runs the consumer-facing Find a Surveyor directory at ricsfirms.com and the isurv knowledge
  platform. Because the United Kingdom has no MLS, there is no RESO here at all - no RESO Web API or Data Dictionary certification,
  no OData $metadata, no Universal Property Identifier - so the "certified but unreachable" pattern does not apply; there
  is simply no listing-data certification layer in this market. What RICS does publish is genuinely machine-readable: the
  RICS Data Standard (RDS) 3.3.3 is an MIT-licensed JSON Schema and XSD covering land, property and infrastructure assets
  and incorporating ICMS, ILMS, IPMS, IVS and IBOS, hosted openly on GitHub at RICS-Data-Standard/RDS and downloadable anonymously.
  RICS also operates one real production API - the DigitalCommunity API at api.rics.org, whose OpenAPI 3.0.1 contract is served
  publicly and anonymously from a live Swagger UI - but it is not a public data API: it exposes RICS firm regulation schemes,
  PII and redress records, subscriptions, payments, member profiles and survey-writer integration, and its own description
  states that credentials must first be issued by RICS. There is no developer portal, no self-serve signup, and no open dataset
  from RICS; the UK''s open property data layer belongs to HM Land Registry and Ordnance Survey, not to the professional body.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/groq.png
tags:
- Real Estate
- United Kingdom
- Industry Body
- Valuation
- Standards
- Surveying
- Property Measurement
- Regulation
- Construction
- PropTech
created: '2026-07-26'
modified: '2026-07-26'
specificationVersion: '0.19'
apis:
- aid: rics:rics-digitalcommunity-api
  name: RICS DigitalCommunity API
  description: 'The RICS DigitalCommunity API is a live, RICS-operated REST API served from api.rics.org whose OpenAPI 3.0.1
    contract is published anonymously and without credentials at https://api.rics.org/swagger/v1/swagger.json (HTTP 200, 67,992
    bytes, fetched 2026-07-26) and rendered in a Swagger UI at https://api.rics.org/. It carries 16 operations across seven
    tags - Token, Profile, Regulation, Payment, SurveyWriter, AzureStorage and OlaMerchantPost - and its schemas are unmistakably
    those of a professional regulator: RegulationScheme, SchemeLicenceType, SchemeLicenceStatus, PiiInsurer, RedressProvider,
    MemberDesignation, ProfessionalGrade, RegulatedOrganisationType, SurveyingService, SurveyWriterModel, RegulationSubscription
    and RegulationQuote. This is the machinery behind RICS firm regulation, professional indemnity insurance and redress declarations,
    subscription billing and survey-writing software integration - it is NOT a property, listings or valuation-data API. Access
    is not self-serve. The specification''s own info.description states that "to use this API, you need to have been first
    been issued a username and password by RICS", which are POSTed as a JSON User object to /token to receive a short-lived
    bearer JWT that must accompany every subsequent request. No application form, pricing page, terms page or developer documentation
    for this API was found on any RICS property; the closest published route is the RICS Tech Partner Programme. Probed anonymously
    on 2026-07-26, GET /api/Profile/1 returned HTTP 401 and GET /token returned HTTP 405, confirming the surface is live and
    enforcing authentication.'
  humanURL: https://api.rics.org/
  baseURL: https://api.rics.org
  tags:
  - Regulation
  - Membership
  - Payments
  - Surveying
  - Professional Body
  properties:
  - type: OpenAPI
    url: openapi/rics-digitalcommunity-api-openapi.json
    name: RICS DigitalCommunity API OpenAPI 3.0.1, harvested verbatim from https://api.rics.org/swagger/v1/swagger.json on
      2026-07-26 (HTTP 200)
  - type: APIReference
    url: https://api.rics.org/
    name: Swagger UI for the DigitalCommunity API (public, anonymous, tryItOut disabled)
  - type: Partners
    url: https://www.rics.org/get-involved/rics-tech-partner-programme
    name: RICS Tech Partner Programme - the only published route to a RICS technology integration
  - type: Overlay
    url: overlays/rics-digitalcommunity-api-overlay.yaml
    name: API Evangelist Overlay 1.0.0 assigning the operationIds and tags the published spec never declared
  - type: ToolCrosswalk
    url: mcp/rics-tool-crosswalk.yml
    name: Candidate MCP tool to OpenAPI operation crosswalk (RICS runs no MCP server; 16 of 16 bound by construction)
common:
- type: AgenticAccess
  url: agentic-access/rics-agentic-access.yml
- type: DomainSecurity
  url: security/rics-domain-security.yml
- type: Authentication
  url: authentication/rics-authentication.yml
  name: Derived auth profile - one Bearer scheme (apiKey in the Authorization header), credentials issued by RICS
- type: OAuthScopes
  url: scopes/rics-scopes.yml
  name: The single OIDC scope RICS advertises (openid, member sign-in) and why the API itself has no scope model
- type: WellKnown
  url: well-known/rics-well-known.yml
  name: Every /.well-known/ probe across the RICS estate with status - one hit, the Azure AD B2C OIDC discovery document
- type: Conventions
  url: conventions/rics-conventions.yml
  name: Cross-cutting semantics of the DigitalCommunity API - bearer auth, no idempotency, no pagination, no rate-limit signalling
- type: ErrorCatalog
  url: errors/rics-problem-types.yml
  name: The ProblemDetails envelope and every declared 4xx/5xx, plus the undeclared 500 observed on /token
- type: DataModel
  url: data-model/rics-data-model.yml
  name: Derived entity-relationship graph of the 52 DigitalCommunity schemas, hubbed on RegulationScheme
- type: Lifecycle
  url: lifecycle/rics-lifecycle.yml
  name: Versioning and maintenance posture - unversioned v1 API with no deprecation policy, SLA or status page
- type: ChangeLog
  url: changelog/rics-changelog.yml
  name: RICS Data Standard release history from GitHub Releases (v3.3.3 March 2022, v3.2.1 April 2021)
- type: Conformance
  url: conformance/rics-conformance.yml
  name: Standards conformance - OpenAPI 3.0.1, JSON Schema draft-04, OIDC, IVS/IPMS/ICMS/ILMS/IBOS; no RESO, no OData, no
    OAuth on the API
- type: MCPServer
  url: mcp/rics-mcp.yml
  name: Candidate MCP tool list derived from the OpenAPI - RICS publishes no MCP server (api.rics.org/mcp returns 404)
- type: AgentSkill
  url: skills/_index.yml
  name: Three generated agent skills grounded in the real read operations of the DigitalCommunity API
- type: LLMsTxt
  url: llms/rics-llms.txt
  name: Generated llms.txt for RICS - no /llms.txt is published on any RICS host
- type: Website
  url: https://www.rics.org/
- type: About
  url: https://www.rics.org/about-rics
- type: Standards
  url: https://www.rics.org/profession-standards/rics-standards-and-guidance
  name: RICS Standards and Guidance
- type: Standards
  url: https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/valuation-standards/red-book
  name: RICS Valuation - Global Standards (the Red Book), incorporating IVS
- type: Standards
  url: https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/real-estate-standards/rics-property-measurement-2nd-edition
  name: RICS Property Measurement, 2nd edition (IPMS)
- type: Standards
  url: https://www.rics.org/profession-standards/rics-standards-and-guidance/sector-standards/construction-standards/rics-data-standards
  name: RICS Data Standards
- type: JSONSchema
  url: openapi/rics-data-standard-3.3.3-schema.json
  name: RICS Data Standard (RDS) 3.3.3 JSON Schema (draft-04), MIT licensed
- type: XMLSchema
  url: openapi/rics-data-standard-3.3.3-schema.xsd
  name: RICS Data Standard (RDS) 3.3.3 XSD, MIT licensed
- type: DataModel
  url: openapi/rics-data-standard-3.3.3-description.json
  name: RICS Data Standard 3.3.3 schema description, licence and contact block
- type: Examples
  url: openapi/rics-data-standard-3.3.3-example.json
  name: RICS Data Standard 3.3.3 reference example instance (rics:DataTransfer)
- type: Examples
  url: openapi/rics-data-standard-3.3.3-ipms-example.json
  name: RICS Data Standard 3.3.3 IPMS example instance
- type: Examples
  url: openapi/rics-data-standard-3.3.3-icms-example.json
  name: RICS Data Standard 3.3.3 ICMS example instance
- type: SourceCode
  url: https://github.com/RICS-Data-Standard/RDS
  name: RICS Data Standard canonical repository (MIT licence, latest release v3.3.3, March 2022)
- type: GitHubOrganization
  url: https://github.com/RICS-Data-Standard
- type: OpenIDConnect
  url: openapi/rics-azure-ad-b2c-openid-configuration.json
  name: RICS Azure AD B2C OpenID Connect discovery document (member sign-in, tenant ricsb2clive.onmicrosoft.com, policy B2C_1A_RICS_signup_signin)
    fetched anonymously 2026-07-26
- type: Authentication
  url: https://b2clogin.rics.org/ricsb2clive.onmicrosoft.com/B2C_1A_RICS_signup_signin/v2.0/.well-known/openid-configuration
  name: Live OIDC discovery endpoint for RICS member sign-in
- type: Login
  url: https://services.rics.org/Rics.IntermediaryIdentityService/
  name: RICS Intermediary Identity Service sign-in (Azure AD B2C)
- type: Regulation
  url: https://www.rics.org/regulation
  name: RICS regulation of members and regulated firms
- type: Directory
  url: https://www.ricsfirms.com/
  name: Find a Surveyor - public directory of RICS-regulated firms (no documented API)
- type: KnowledgeBase
  url: https://www.isurv.com/
  name: isurv - RICS subscription platform carrying the standards, guidance and document downloads
- type: Partners
  url: https://www.rics.org/get-involved/rics-tech-partner-programme
  name: RICS Tech Partner Programme
- type: Blog
  url: https://www.rics.org/news-insights
  name: RICS news and insights - the professional body's editorial and research publishing
- type: Support
  url: https://www.rics.org/footer/contact-us
  name: Contact RICS - the only published support route; there is no developer support channel
- type: Community
  url: https://community.rics.org/home
  name: myRICS community - member discussion platform
- type: SignUp
  url: https://www.rics.org/join-rics/apply-to-join-rics
  name: Apply to join RICS - membership signup (there is no API signup of any kind)
- type: Pricing
  url: https://www.rics.org/join-rics/join-fees
  name: RICS join fees - published membership pricing (no API pricing exists)
- type: Pricing
  url: https://www.rics.org/renew-my-membership/professional-fees
  name: RICS professional fees - annual subscription rates by region
- type: TermsOfService
  url: https://www.rics.org/footer/rics-org-terms-and-conditions
  name: rics.org terms and conditions
- type: PrivacyPolicy
  url: https://www.rics.org/footer/rics-privacy-policy
  name: RICS privacy policy
- type: Email
  url: mailto:datastandards@rics.org
  name: RICS Data Standard support contact, per the RDS schema description block
- type: Email
  url: mailto:join@rics.org
  name: RICS membership enquiries
- type: LinkedIn
  url: https://www.linkedin.com/company/rics
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com