# UK Osteopath Register Scraper (`crawlerbros/uk-osteopath-register-scraper`) Actor

Search the General Osteopathic Council's public register (osteopathy.org.uk) by postcode/town, surname, or practice features, or look up exact registration numbers. Returns status, qualifications, training, and practice details.

- **URL**: https://apify.com/crawlerbros/uk-osteopath-register-scraper.md
- **Developed by:** [Crawler Bros](https://apify.com/crawlerbros) (community)
- **Categories:** Automation, Lead generation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## UK Osteopath Register Scraper

Verify UK-registered osteopaths against the **General Osteopathic Council (GOsC)** official public register at `osteopathy.org.uk`. Search by postcode/town, surname, or practice features (disabled access, home visits, Welsh spoken) — or look up an exact GOsC registration number — to confirm whether an osteopath is currently registered and legally able to practise in the UK. No login, no cookies, no paid proxy required.

### What this actor does

- **Two lookup modes:** browse/filter the register, or exact registration-number lookup
- **Search by any combination of:** postcode or town (with a configurable radius for postcode searches), surname, disabled access, home visits, Welsh spoken
- **Browse the entire register** — leave all filters blank to page through every currently-registered osteopath
- **Full result-set pagination** — follows the register's own paging so large matches are returned in full (bounded only by `maxItems`)
- **Multiple practice addresses per osteopath** — many osteopaths practise at more than one clinic; every practice they are listed at is captured (address, opening hours, home visits, disabled access, Welsh spoken, website)
- **Empty fields are never included** — only real, extracted data is emitted

### Output per osteopath

- `registrantId` — GOsC internal registrant identifier
- `registrationNumber` — unique GOsC registration number
- `name` — full name as shown on the register (with courtesy title)
- `gender`
- `practisingStatus` — e.g. `Fully Registered`
- `dateOfRegistration` — date first joined the register (ISO `YYYY-MM-DD`)
- `qualifications` — post-nominal qualifications (e.g. `DO`, `BSc (Hons) Ost`)
- `placeOfTraining` — institution where the osteopath trained
- `qualificationDate` — month/year of qualification (ISO `YYYY-MM`)
- `contactNumber` — personal contact phone number, when published on the register
- `email` — personal contact email address, when published on the register
- `practiceCount` — number of practices this osteopath is listed at
- `practices[]` — one entry per practice: `name`, `practiceUrl`, `address`, `postcode`, `openingHours`, `email`, `phone`, `website`, `homeVisits` (boolean), `disabledAccess` (boolean), `welshSpoken` (boolean)
- `sourceUrl` — direct link to the official GOsC register entry
- `recordType`, `scrapedAt`

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `mode` | select | `search` | `search` (browse/filter) or `byRegistrationNumbers` (exact lookup) |
| `location` | string | `London` | UK postcode or town/city name (mode=search). Leave blank to browse the whole register |
| `radius` | select | `10mi` | `5mi` / `10mi` / `25mi` / `50mi` — only applies when `location` is a postcode |
| `surname` | string | – | Filter to osteopaths whose surname contains this text |
| `disabilityAccess` | boolean | `false` | Only return osteopaths practising where disabled access is available |
| `homeVisit` | boolean | `false` | Only return osteopaths who offer home visits |
| `welshSpoken` | boolean | `false` | Only return osteopaths practising where Welsh is spoken |
| `registrationNumbers` | array | `["1766"]` | Exact GOsC registration numbers (mode=byRegistrationNumbers) |
| `maxItems` | integer | `20` | Maximum number of osteopath records to return (1–2000) |

#### Example: search osteopaths near a postcode

```json
{
  "mode": "search",
  "location": "SW1A 1AA",
  "radius": "10mi",
  "maxItems": 25
}
```

#### Example: filter by surname and practice features

```json
{
  "mode": "search",
  "surname": "Smith",
  "homeVisit": true,
  "disabilityAccess": true,
  "maxItems": 25
}
```

#### Example: look up exact registration numbers

```json
{
  "mode": "byRegistrationNumbers",
  "registrationNumbers": ["1766", "7065", "8596"]
}
```

### Use cases

- **Employers & clinics** verifying a candidate osteopath's registration status before hiring
- **Patients** confirming their osteopath is legitimately registered with the GOsC
- **Insurers** cross-checking practitioner registration numbers
- **Researchers** analysing the geographic distribution, qualifications, or training institutions of UK osteopaths
- **Directory builders** enriching a UK health-practitioner dataset with official register data

### FAQ

**Is this official data?**
Yes — every record is scraped live from the General Osteopathic Council's own public register search at `osteopathy.org.uk/register-search/`. This is the same register the GOsC itself uses to let the public verify osteopaths.

**Do I need an account, login, or cookies?**
No. The register search is fully public; no login or paid proxy is required.

**What if my search returns 0 results?**
Check the spelling of the surname/postcode, widen the `radius`, or remove filters. The actor sets a clear status message when a search or lookup finds no matches.

**Why do some osteopaths have more than one entry in `practices[]`?**
Many osteopaths work across multiple clinics. Every practice location currently listed against that osteopath on the register is captured in the `practices[]` array.

**Can I look up multiple registration numbers at once?**
Yes — set `mode` to `byRegistrationNumbers` and pass an array of registration numbers.

**Why do `sourceUrl` and `practices[].practiceUrl` return a blank/challenge page with a plain HTTP request (e.g. `curl`)?**
The GOsC register-search pages sit behind a JavaScript security check. They render correctly and instantly in any real browser (which is exactly how this actor reads them) but a plain HTTP client without JavaScript will see an interstitial instead of the page content. This does not affect the actor's own output — only manual `curl`/`wget` checks of these specific URLs.

**How long does a run take?**
Each osteopath record requires solving a JavaScript security check, so expect roughly 5-10 seconds per osteopath. For runs with a large `maxItems`, allow a generous run timeout (the platform default is usually sufficient, but very large runs — 100+ records — may need the timeout increased in Actor run settings).

# Actor input Schema

## `mode` (type: `string`):

What to fetch.

## `location` (type: `string`):

UK postcode or town/city name to search near, e.g. "London" or "SW1A 1AA". Leave blank to browse the whole register.

## `radius` (type: `string`):

Distance from the postcode entered in `location`. Only applies when `location` is a postcode — ignored for town/city names.

## `surname` (type: `string`):

Filter to osteopaths whose surname contains this text. Can be combined with `location`.

## `disabilityAccess` (type: `boolean`):

Only return osteopaths practising at a location that reports disabled access.

## `homeVisit` (type: `boolean`):

Only return osteopaths practising at a location that offers home visits.

## `welshSpoken` (type: `boolean`):

Only return osteopaths practising at a location where Welsh is spoken.

## `registrationNumbers` (type: `array`):

Exact GOsC registration numbers to look up, e.g. "1766".

## `maxItems` (type: `integer`):

Maximum number of osteopath records to return in this run.

## Actor input object example

```json
{
  "mode": "search",
  "location": "London",
  "radius": "10mi",
  "disabilityAccess": false,
  "homeVisit": false,
  "welshSpoken": false,
  "registrationNumbers": [
    "1766"
  ],
  "maxItems": 20
}
```

# Actor output Schema

## `osteopaths` (type: `string`):

Dataset containing all scraped osteopath registrants.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "search",
    "location": "London",
    "radius": "10mi",
    "disabilityAccess": false,
    "homeVisit": false,
    "welshSpoken": false,
    "registrationNumbers": [
        "1766"
    ],
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawlerbros/uk-osteopath-register-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "search",
    "location": "London",
    "radius": "10mi",
    "disabilityAccess": False,
    "homeVisit": False,
    "welshSpoken": False,
    "registrationNumbers": ["1766"],
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("crawlerbros/uk-osteopath-register-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "search",
  "location": "London",
  "radius": "10mi",
  "disabilityAccess": false,
  "homeVisit": false,
  "welshSpoken": false,
  "registrationNumbers": [
    "1766"
  ],
  "maxItems": 20
}' |
apify call crawlerbros/uk-osteopath-register-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawlerbros/uk-osteopath-register-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/g3lkDvoVFtIyt7Q1S/builds/X37e4bqiYxT0e7Xll/openapi.json