# UK Employment Tribunal Decisions Scraper (`jungle_synthesizer/uk-employment-tribunal-decisions-scraper`) Actor

Scrape UK Employment Tribunal decisions from gov.uk — claimant, respondent, case number, jurisdiction codes, judge, venue, decision date, outcome and award amount, text-extracted from the decision documents. Covers England & Wales and Scotland across the full published archive.

- **URL**: https://apify.com/jungle\_synthesizer/uk-employment-tribunal-decisions-scraper.md
- **Developed by:** [BowTiedRaccoon](https://apify.com/jungle_synthesizer) (community)
- **Categories:** Lead generation, Jobs, Business
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 record scrapeds

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

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## UK Employment Tribunal Decisions Scraper — Employer Case Data

Scrape published UK Employment Tribunal decisions from [gov.uk](https://www.gov.uk/employment-tribunal-decisions). Returns claimant, respondent, case number, jurisdiction codes, judge, venue, outcome and award amount for England & Wales and Scotland decisions — parsed from the decision documents, not just the listing page, across the full published archive of 130,000+ cases.

***

### UK Employment Tribunal Decisions Scraper Features

- Parses claimant, respondent and case number out of every decision title — no manual splitting
- Extracts jurisdiction codes (Unfair Dismissal, Race Discrimination, Working Time, and 25+ others), tribunal country and decision date
- Reads the decision document itself for judge, venue, panel members, outcome and award amount — fields that don't exist on the listing page
- Returns the decision document's full extracted text alongside the structured fields
- Filter by keyword or a published-date window, or leave both blank for the newest decisions first
- Covers both England & Wales and Scotland tribunals in one dataset

***

### Who Uses UK Employment Tribunal Data?

- **Employment law firms** — track outcomes and award trends across specific jurisdiction codes or industries
- **HR-tech and compliance vendors** — build employer-risk scoring on top of named respondents, or at least the dataset that makes it possible
- **Insurers and litigation funders** — screen employers with a history of tribunal claims before underwriting or funding
- **Journalists and researchers** — corpus analysis of tribunal outcomes, award sizes, and case volume by jurisdiction
- **Recruiters and due-diligence teams** — check a target employer's litigation history before a placement or an acquisition

***

### How UK Employment Tribunal Decisions Scraper Works

1. The scraper queries gov.uk's published Employment Tribunal decisions index, newest first, optionally narrowed by keyword or a publish-date window.
2. For each decision it reads the case's gov.uk page for jurisdiction codes, tribunal country, decision date, and the attached decision document's link.
3. It fetches the decision document itself and extracts venue, judge, panel members, outcome and award amount — the fields that only ever appear in the document body, never the listing.
4. Results land in your Apify dataset as flat JSON records, one per decision.

***

### UK Employment Tribunal Decisions Scraper Input Fields

```json
{
  "maxItems": 10,
  "query": "Tesco",
  "publishedFrom": "2026-09-01T00:00:00",
  "publishedTo": "2026-09-25T23:59:59"
}
```

| Field           | Type    | Default  | Description |
|-----------------|---------|----------|---------------------------------------------------------------------------------------|
| `maxItems`      | integer | `10`     | Maximum number of decisions to return. Each one requires a document fetch, so keep this modest for a fast run. |
| `query`         | string  | *(none)* | Free-text keyword filtering the decisions index — an employer or claimant name works well. Leave blank for the unfiltered archive. |
| `publishedFrom` | string  | *(none)* | ISO-8601 date/time. Only decisions published on gov.uk on or after this timestamp. |
| `publishedTo`   | string  | *(none)* | ISO-8601 date/time. Only decisions published on gov.uk on or before this timestamp. |

To pull the whole archive, run the scraper repeatedly with a `publishedFrom`/`publishedTo` window each time, or a keyword narrowing the result set — one unbounded run isn't the intended shape here, since every decision costs a document fetch.

***

### UK Employment Tribunal Decisions Scraper Output Fields

```json
{
  "decision_slug": "mr-e-lopez-v-tesco-stores-ltd-2309092-slash-2024",
  "case_number": "2309092/2024",
  "claimant": "Mr E Lopez",
  "respondent": "Tesco Stores Ltd",
  "decision_date": "2026-09-16",
  "published_date": "2026-09-25T12:38:35Z",
  "jurisdiction_codes": ["Breach of Contract", "Unfair Dismissal"],
  "tribunal_country": "England and Wales",
  "venue": "London South (by video)",
  "judge": "Buckley",
  "panel_members": [],
  "decision_type": "Judgment",
  "outcome": "upheld",
  "award_amount_gbp": 1841,
  "is_reserved": false,
  "document_urls": ["https://assets.publishing.service.gov.uk/media/6ab62cd7fceb6fb3a65011e0/Mr_E_Lopez_v_Tesco_Stores_Limited_2309092-2024_Lopez_Judgment_17-Sep-26.pdf"],
  "document_formats": ["pdf"],
  "full_text": "Case No:2309092/2024 ... JUDGMENT ... 1. The claim for unfair dismissal is dismissed...",
  "source_url": "https://www.gov.uk/employment-tribunal-decisions/mr-e-lopez-v-tesco-stores-ltd-2309092-slash-2024",
  "scraped_at": "2026-09-26T13:24:23.711Z"
}
```

| Field                | Type    | Description |
|----------------------|---------|--------------------------------------------------------------------------------------------------------|
| `decision_slug`      | string  | gov.uk URL slug for this decision — a stable key |
| `case_number`        | string  | Tribunal case number(s), e.g. `2309092/2024` |
| `claimant`           | string  | Claimant name as published — anonymised forms ("Mr A") are common and expected |
| `respondent`         | string  | Respondent (employer) name |
| `decision_date`      | string  | ISO-8601 date the tribunal decided the case |
| `published_date`     | string  | ISO-8601 timestamp the decision was published on gov.uk |
| `jurisdiction_codes` | array   | Claim categories, e.g. Unfair Dismissal, Race Discrimination, Working Time |
| `tribunal_country`   | string  | `England and Wales` or `Scotland` |
| `venue`              | string  | Tribunal office / hearing location, read from the decision document (blank on paper-only decisions with no hearing) |
| `judge`              | string  | Presiding Employment Judge, read from the decision document |
| `panel_members`      | array   | Non-legal panel members, when the case was heard by a full panel rather than a judge sitting alone |
| `decision_type`      | string  | Document type(s) attached — Judgment, Reasons, Judgment with Reasons, Costs, Remedy, Strike Out, etc. |
| `outcome`            | string  | Best-effort classification of the judgment: upheld, dismissed, struck out, withdrawn, or settled |
| `award_amount_gbp`   | number  | Compensation awarded in GBP, where the document states one — most decisions carry no monetary award |
| `is_reserved`        | boolean | True when the document indicates the judgment was reserved (written reasons issued after the hearing) |
| `document_urls`      | array   | URLs of the decision document(s) attached to this case — often more than one (judgment, reasons, remedy) |
| `document_formats`   | array   | File formats of the attached documents: `pdf`, `doc`, `docx`, or `rtf` |
| `full_text`          | string  | Extracted text of the primary decision document |
| `source_url`         | string  | Canonical gov.uk URL for this decision |
| `scraped_at`         | string  | ISO-8601 timestamp when the record was scraped |

***

### FAQ

#### How do I scrape UK Employment Tribunal decisions?

UK Employment Tribunal Decisions Scraper needs no account, login, or API key. Set `maxItems` and, optionally, a keyword or a published-date window, then run — you get back structured JSON, not a page of links to click through yourself.

#### How much does UK Employment Tribunal Decisions Scraper cost to run?

Pricing is pay-per-event: $0.10 per actor start, plus $0.01 per decision returned. Scraping 100 decisions costs roughly $1.10. Each decision requires reading its underlying document for the fields the listing page doesn't carry, which is where the per-record cost goes.

#### What data can I get from gov.uk Employment Tribunal decisions?

Claimant, respondent, case number, jurisdiction codes, tribunal country, decision date, venue, judge, outcome, award amount, and the full text of the decision document — for every publicly published Employment Tribunal decision, England & Wales and Scotland alike.

#### Can I filter by employer name or claim category?

Yes — the `query` field does a keyword search against the decisions index, and an employer or claimant name works as well as any other term. There's no separate jurisdiction filter; the unfiltered archive already returns everything, newest first.

#### Do award amount and outcome show up for every decision?

No. Both are read out of the decision document body, and plenty of decisions — strike-outs, withdrawals, case-management orders — carry no monetary award and no hearing to report a venue or judge for. Those fields come back empty rather than guessed.

***

### Need More Features?

Need custom fields, filters, or a different target site? [File an issue](https://console.apify.com/actors/issues) or get in touch.

### Why Use UK Employment Tribunal Decisions Scraper?

- **Employer-named, not just linked** — claimant and respondent are parsed out of every record, turning a list of case links into employer-searchable data.
- **Reads the document, not just the listing** — judge, venue, outcome and award amount only ever live in the decision document body, and this is the layer that goes and gets them, PDF text extraction included.
- **Complete archive, one query** — the unfiltered index already returns the full 130,000+ decision corpus, newest first, so there's no jurisdiction-by-jurisdiction crawl to assemble yourself.

# Actor input Schema

## `sp_intended_usage` (type: `string`):

What will this data feed? E.g. lead lists, KYB checks, price tracking.

## `sp_improvement_suggestions` (type: `string`):

Provide any feedback or suggestions for improvements.

## `sp_contact` (type: `string`):

We'll personally help with your use case. No spam.

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

Maximum number of decisions to scrape. Each record requires a detail-page fetch plus a decision-document fetch and text extraction, so keep this modest per run for fast turnaround.

## `query` (type: `string`):

Free-text keyword filtering the gov.uk search index (e.g. an employer or claimant name). Leave blank to walk the full unfiltered archive, newest first.

## `publishedFrom` (type: `string`):

ISO-8601 date/time. Only decisions published on gov.uk on or after this timestamp. Leave blank for no lower bound.

## `publishedTo` (type: `string`):

ISO-8601 date/time. Only decisions published on gov.uk on or before this timestamp. Leave blank for no upper bound (newest first).

## Actor input object example

```json
{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "maxItems": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("jungle_synthesizer/uk-employment-tribunal-decisions-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 = {
    "sp_intended_usage": "Describe your intended use...",
    "sp_improvement_suggestions": "Share your suggestions here...",
    "sp_contact": "Share your email here...",
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("jungle_synthesizer/uk-employment-tribunal-decisions-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 '{
  "sp_intended_usage": "Describe your intended use...",
  "sp_improvement_suggestions": "Share your suggestions here...",
  "sp_contact": "Share your email here...",
  "maxItems": 10
}' |
apify call jungle_synthesizer/uk-employment-tribunal-decisions-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jungle_synthesizer/uk-employment-tribunal-decisions-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/ff3lpUCcbbQ5wcX79/builds/21vKYPCGdlEPbS5xW/openapi.json