# RICS DigitalCommunity API

**Canonical:** https://apis.io/apis/rics/rics-digitalcommunity-api/  
**Provider:** RICS (Royal Institution of Chartered Surveyors) — https://apis.io/providers/rics/  
**Base URL:** https://api.rics.org  
**Documentation:** https://api.rics.org/

RICS DigitalCommunity API is published by [RICS (Royal Institution of Chartered Surveyors)](https://apis.io/providers/rics/) on the [APIs.io](https://apis.io/) network, described by a machine-readable OpenAPI specification. Tagged areas include Regulations, Membership, Payments, Surveying, and Professional Body. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

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.

## Machine-readable artifacts (6)

- **OpenAPI** — https://raw.githubusercontent.com/api-evangelist/rics/refs/heads/main/openapi/rics-digitalcommunity-api-openapi.json
- **APIReference** — https://api.rics.org/
- **Partners** — https://www.rics.org/get-involved/rics-tech-partner-programme
- **Overlay** — https://raw.githubusercontent.com/api-evangelist/rics/refs/heads/main/overlays/rics-digitalcommunity-api-overlay.yaml
- **ToolCrosswalk** — https://raw.githubusercontent.com/api-evangelist/rics/refs/heads/main/mcp/rics-tool-crosswalk.yml
- **APIsJSON** — https://raw.githubusercontent.com/api-evangelist/rics/refs/heads/main/apis.yml

## Tags

Regulations, Membership, Payments, Surveying, Professional Body

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/rics/rics-digitalcommunity-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/rics/.