CareGist

CareGist exposes daily-refreshed UK care-provider data through the same layer that powers the dashboard and exports. The goal is not raw feed access alone. The goal is operationally usable regulatory data.

Dashboard, exports, and API on one data layer

Use CareGist in the way your team actually works: browser first, export next, API when embedding and automation matter.

Dashboard-first workflow

Start with search, nearby discovery, saved comparisons, exports, and monitoring before writing integration code.

Geospatial search

Query by postcode, region, service type, and nearby radius using cleaned coordinates and locality fields.

Operational exports

Move lists into analyst and operator workflows with plan-based CSV exports and field visibility.

API access

Use the same cleaned dataset programmatically when you need embedding, product integration, or recurring automation.

Monitoring layer

Track providers for rating changes so teams do not have to poll the raw register manually.

Daily refresh

Data syncs against the public CQC register every day; we avoid claiming live source updates.

Sample Response

{
  "data": [{
    "id": "1-123456789",
    "name": "Sunrise Care Home",
    "slug": "sunrise-care-home-bournemouth",
    "type": "Social Care Org",
    "status": "ACTIVE",
    "overall_rating": "Good",
    "town": "Bournemouth",
    "postcode": "BH1 1AA",
    "region": "South West",
    "service_types": "Care home service with nursing",
    "quality_score": 82,
    "quality_tier": "GOOD",
    "latitude": 50.7192,
    "longitude": -1.8808,
    "phone": "01202 000000"
  }],
  "meta": { "total": 1, "page": 1, "per_page": 20, "pages": 1 }
}

How webhooks work

Business plans can register outbound webhooks for rating changes. CareGist signs each payload with an HMAC SHA-256 signature in X-CareGist-Signature.

The currently supported event is provider.rating_changed. Delivery retries use 1s, 2s, and 4s backoff. Failed deliveries remain visible in the dashboard so teams can spot broken endpoints without digging through support tickets.

Webhooks are intended for operational sync and alerting workflows, not as a substitute for daily batch exports.

Webhook Example

POST /webhooks
{
  "url": "https://ops.example.com/caregist/webhooks",
  "events": ["provider.rating_changed"]
}

Headers on delivery:
X-CareGist-Event: provider.rating_changed
X-CareGist-Signature: sha256=<hmac>

Retries:
1s, 2s, 4s backoff before final failure

Pricing

Starter

£39 + VAT/mo

Nearby search, 500-row export, 15 monitors, 10 requests/sec

Pro

Recommended

£99 + VAT/mo

5,000-row export, 100 monitors, 3 included users, 25 requests/sec, recommended for recurring team use

Business

£399 + VAT/mo

Full fields, webhooks, 10,000-row export, 500 monitors, 10 included users, 10,000 requests/day

See full pricing details

Need a reviewed integration path?

Starter, Pro, and Business can begin self-serve. Use this form if you want help scoping a higher-volume integration or enterprise procurement path.

Data sourced from the CQC public register · Updated daily · Built to make raw regulatory data usable inside workflows