# FINRA Arbitration Awards Scraper (`parseforge/finra-arbitration-awards-scraper`) Actor

Search FINRA's Arbitration Awards Online archive of 66,000+ securities arbitration awards from 1988 on, with parties, arbitrators, damages, fees and expungement findings parsed from the award PDFs.

- **URL**: https://apify.com/parseforge/finra-arbitration-awards-scraper.md
- **Developed by:** [ParseForge](https://apify.com/parseforge) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.23 / 1,000 award records

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?

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

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner.jpg)](https://apify.com/parseforge?fpr=vmoqkp)

### FINRA Arbitration Awards Scraper - Awards Online Search

**Search and download FINRA's Arbitration Awards Online archive: 66,600 securities arbitration awards, orders and motions from 1988 to this week.** Every row carries the case number, date of award, forum, claimants, respondents, both sides' representatives, the arbitrators, the hearing site and the link to the award PDF. No login, no API key, no browser. Export to CSV, JSON, Excel, or XML.

FINRA's own Awards Online search shows fifteen results at a time, offers no export, and stops at four filters. This Actor reads the same public index, applies your filters, and then goes one step further: it opens the award PDF and parses what the index never exposes, including the damages awarded, the forum fees, the arbitrator roles, the causes of action and the expungement findings with their CRD numbers.

| Who uses it | What they use FINRA award data for |
|---|---|
| Securities and investor-rights lawyers | Award history for a firm, a broker or an arbitrator before filing or picking a panel |
| Compliance and legal teams at broker-dealers | Every award naming the firm, with the amounts, fees and causes of action |
| Expert witnesses and damages consultants | Comparable awards by cause of action, hearing site and year for a damages opinion |
| Financial journalists and academics | A structured corpus of 66,600 arbitration outcomes going back to 1988 |
| Legal tech and data vendors | A normalised feed of new awards with stable case ids and PDF links |

### What it does

FINRA publishes every arbitration award it administers, plus the court orders and motions filed against them. The archive holds **66,617 documents**: 65,372 awards, 475 orders to confirm, 449 orders to vacate, 130 motions to vacate, 27 motions to confirm and 175 other documents, across eight forums (NASD 36,421, FINRA 25,449, NYSE 4,130, CBOE 197, AMEX 147, MSRB 139, Pacific Exchange/ARCA 78, PHLX 56).

Every row returns:

- 🧾 **The index record:** case number, document title, date of award, award year, the year the case was filed, document type, forum, panel composition, hearing site split into city and state, and the direct PDF link.
- 👥 **The parties:** claimants and respondents as clean lists with counts, each side's representatives, and whether each side was represented at all.
- ⚖️ **The panel:** the arbitrators who signed, as a list and as text, with the count.
- 🚩 **Flags:** whether FINRA has expunged the case from CRD registration records, whether the case has other documents on file, and whether the index carries a summary.
- 💵 **Damages** (optional): compensatory, punitive, attorney fees, expert fees and costs awarded, the total, the interest rate and its start date, the amount the claimant asked for, and whether the claims were denied.
- 🧾 **Forum fees** (optional): filing fees, member surcharge and process fee, total hearing session fees, the session count, and each assessment with the party it was charged to.
- 🧑‍⚖️ **Arbitrator roles** (optional): each arbitrator as public, non-public, presiding chairperson or sole arbitrator, with the panel size and the chairperson.
- 🔎 **Expungement** (optional): requested, granted or denied, the CRD occurrence numbers, the registered persons with their CRD numbers, the Rule 2080 affirmative findings, and whether court confirmation is required.
- 📄 **The document** (optional): counsel and law firms, the causes of action, the case timeline, the narrative sections, and the full award text.

`searchTerms` is verified against the award itself. With a date range, every award in the range is downloaded and checked for the term, so `churning` or `Rule 12206` finds the awards that really say it. Without a date range FINRA's index supplies candidates, which are checked the same way and dropped when the term is not in the document. FINRA's index alone only searches names, case numbers and, for awards before July 2007, the award text.

Every row contains: `caseId`, `documentTitle`, `dateOfAward`, `awardYear`, `caseFiledYear`, `documentType`, `forum`, `panelComposition`, `hearingSite`, `hearingCity`, `hearingState`, `claimants`, `claimantsText`, `claimantCount`, `respondents`, `respondentsText`, `respondentCount`, `claimantRepresentatives`, `respondentRepresentatives`, `claimantRepresented`, `respondentRepresented`, `neutrals`, `neutralsText`, `arbitratorCount`, `summary`, `hasSummary`, `hasRelatedCases`, `isExpungedInCrd`, `documentUrl`, `caseUrl`, `indexId` and `scrapedAt`.

### What you can do with FINRA arbitration award data

**Build a firm's award history.**

Set `partyNameContains` to a broker-dealer and a date range, turn on damages, and you get every award naming that firm with the compensatory, punitive and attorney-fee amounts, the causes of action and the hearing site. That is the table a plaintiff's lawyer, a compliance officer or a journalist needs and that no public search returns.

**Research an arbitrator before you strike the list.**

`arbitratorNameContains` keeps only awards decided by that arbitrator. With the panel block on, each row says whether they chaired, whether they sat as a public or non-public arbitrator, what the panel awarded and how the fees were assessed.

**Track expungements.**

Turn on the expungement block and filter with `onlyExpunged` or `panelCompositions: ["Special Expungement Panel"]`. Each row gives the occurrence numbers, the registered persons with their CRD numbers, the Rule 2080 finding the panel made and whether court confirmation is still required.

**Benchmark damages by cause of action.**

Search a phrase such as `unsuitability` or `selling away` over a date range, keep the damages and causes-of-action blocks, and you have the awarded-versus-requested ratio by year, forum and hearing site.

### Why choose this scraper

|  | What you get |
|---|---|
| **The whole archive** | 66,600 documents from 1988 to this week, including the NASD and exchange forums that predate FINRA |
| **What the index hides** | Damages, fees, arbitrator roles, counsel, causes of action, case timeline and expungement findings parsed from the award PDF itself |
| **Filters that are measured, not guessed** | Forum, document type and panel composition run inside FINRA's index; every value was checked against the archive's own totals |
| **Verified text search** | Every search hit is checked against the award PDF; an award that does not contain your term is never returned or charged |
| **Honest empties** | Awards published as scanned images say so instead of returning blank damages, and are not charged |
| **Clean parties** | Claimants, respondents, representatives and arbitrators split into lists that keep `Drexel Hamilton, LLC` in one piece |
| **No login, no browser, no key** | Plain HTTP against public endpoints; 900 index rows in 23 seconds |

### How it compares

Nobody else on the Apify Store sells this archive. The closest listings are BrokerCheck scrapers, which return a broker's disclosure summary rather than the award, and generic court-record actors that do not cover FINRA arbitration at all. Against FINRA's own site the difference is exports, filters and the parsed PDF.

| Feature | ParseForge | FINRA Awards Online | BrokerCheck actors | Court-record actors |
|---|---|---|---|---|
| Bulk export (CSV, JSON, Excel) | Yes | No | Yes | Yes |
| Awards back to 1988, all eight forums | Yes | Yes | No | No |
| Damages and fees parsed from the award | Yes | No | No | No |
| Arbitrator roles and panel composition | Yes | Partial | No | No |
| Expungement findings with CRD numbers | Yes | No | No | No |
| Text search verified against the award | Yes | No (fuzzy index hits) | No | Sometimes |
| Price per row | $0.007 | Free, manual | $0.0015 to $0.05 | $0.003 to $0.005 |

### What an award record looks like

```json
{
  "caseId": "26-00668",
  "documentTitle": "26-00668.pdf",
  "dateOfAward": "2026-08-26",
  "awardYear": 2026,
  "caseFiledYear": 2026,
  "documentType": "Award",
  "forum": "FINRA",
  "panelComposition": "N/A",
  "hearingSite": "Houston, TX",
  "hearingCity": "Houston",
  "hearingState": "TX",
  "claimants": ["Merrill Lynch Pierce Fenner & Smith Inc."],
  "claimantsText": "Merrill Lynch Pierce Fenner & Smith Inc.",
  "claimantCount": 1,
  "respondents": ["Ignacio Hawley"],
  "respondentsText": "Ignacio Hawley",
  "respondentCount": 1,
  "claimantRepresentatives": ["Maria V. Martin"],
  "respondentRepresentatives": ["Ignacio Javier Hawley"],
  "claimantRepresented": "Yes",
  "respondentRepresented": "Yes",
  "neutrals": ["Maryanne M. Esser"],
  "neutralsText": "Maryanne M. Esser",
  "arbitratorCount": 1,
  "summary": "Not Disclosed",
  "hasSummary": "No",
  "hasRelatedCases": "No",
  "isExpungedInCrd": "No",
  "documentUrl": "https://data-portal.finra.org/aao_documents/26-00668.pdf",
  "caseUrl": "https://www.finra.org/arbitration-mediation/arbitration-awards-online?aao_radios=case_id&field_case_id_text=26-00668",
  "indexId": "26-00668_5e6cd9fd",
  "scrapedAt": "2026-08-27T16:21:11.532Z"
}
```

With the document blocks on, the same row also carries `compensatoryDamagesUsd`, `punitiveDamagesUsd`, `attorneyFeesUsd`, `awardedCostsUsd`, `totalAwardedUsd`, `requestedCompensatoryUsd`, `interestRate`, `feeItems`, `feeAssessments`, `arbitratorPanel`, `chairperson`, `claimantCounsel`, `lawFirms`, `causesOfAction`, `natureOfDispute`, `hearingDates`, `expungementPersons` and the narrative sections. A real award from March 2024 came back with `compensatoryDamagesUsd: 718178`, `punitiveDamagesUsd: 200000`, `attorneyFeesUsd: 417453`, `interestRate: "9%"` and `causesOfAction` listing seven claims.

### Configure the run

Leave everything empty and the Actor returns the most recent awards. Add search terms, case numbers or filters to narrow it, and tick the document blocks you want parsed. `summary`, `panelComposition` and `hearingSite` come back as `Not Disclosed` or `N/A` when FINRA does not publish them, which for pre-2000 awards is most of the time.

The most recent 100 awards:

```json
{ "maxItems": 100 }
```

Every 2024 award naming a firm, with the damages and the panel:

```json
{
  "partyNameContains": "Morgan Stanley",
  "dateFrom": "2024-01-01",
  "dateTo": "2024-12-31",
  "documentTypes": ["Award"],
  "includeAwardDocument": true,
  "includeMonetaryTerms": true,
  "includeArbitratorPanel": true,
  "maxItems": 500
}
```

Expungement decisions with the CRD numbers and the Rule 2080 findings:

```json
{
  "panelCompositions": ["Special Expungement Panel"],
  "dateFrom": "2023-01-01",
  "includeAwardDocument": true,
  "includeExpungementDetail": true,
  "includeCaseTimeline": true,
  "maxItems": 250
}
```

Every 2024 award whose text contains a term (each award in the range is downloaded and checked):

```json
{ "searchTerms": ["churning"], "dateFrom": "2024-01-01", "dateTo": "2024-12-31", "documentTypes": ["Award"], "maxItems": 300 }
```

### Pricing

Pay-per-event. **$7 per 1,000 award records** plus $0.02 per run start and $0.004 for each search page of 15 results the run reads. Every extraction below is opt-in, and each one is charged only when it actually returned something.

| Event | Price | When |
|---|---|---|
| `award-record` | $0.007 | Every row written |
| `search-page` | $0.004 | Each page of 15 results read, never more pages than rows written |
| `award-document` | $0.006 | Award PDF downloaded and text extracted, once per award |
| `award-full-text` | $0.004 | Full award text attached |
| `award-monetary-terms` | $0.008 | Damages, interest and totals parsed |
| `award-fee-breakdown` | $0.006 | Forum fees and assessments parsed |
| `expungement-detail` | $0.008 | Only for awards that ruled on expungement |
| `arbitrator-panel` | $0.005 | Panel roles parsed from the award |
| `party-representation` | $0.005 | Counsel and law firms parsed |
| `causes-of-action` | $0.005 | Causes of action parsed |
| `case-timeline` | $0.005 | Filing, answer and hearing dates parsed |
| `case-narrative` | $0.004 | Case summary, relief requested and award sections |
| `related-cases` | $0.006 | Only when other documents exist for the case |

Downloads made only to check a search term against the award are free; an award that does not contain the term is neither returned nor charged.

| Run | Approximate cost |
|---|---|
| 100 most recent awards | $0.75 |
| 1,000 awards, index only | $7.29 |
| 1,000 awards with the PDF, damages, fees and panel | up to $32.29 |
| 10,000 awards, index only | $72.69 |

New Apify accounts start with $5 in free credit.

### Free users

Free-plan runs return up to 10 awards as a preview. [Upgrade your Apify plan](https://console.apify.com/sign-up?fpr=vmoqkp) to pull the whole archive.

### Run it

1. [Create a free Apify account with $5 in credit](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Open the [FINRA Arbitration Awards Scraper](https://apify.com/parseforge/finra-arbitration-awards-scraper?fpr=vmoqkp).
3. Add search terms, case numbers or filters, tick the document blocks you want, then click **Start**.
4. Export the results as CSV, Excel, JSON, or XML from the **Dataset** tab, or schedule the run weekly to catch new awards.

Run it programmatically through the [Apify API](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) for JavaScript and Python.

### Use with AI agents (MCP)

Give an AI agent live access to FINRA's award archive through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

```bash
claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/finra-arbitration-awards-scraper"
```

Then ask: *"What did FINRA panels award against Interactive Brokers in 2024, and how much was requested?"*, *"List the expungement awards from 2025 with their CRD occurrence numbers"*, or *"Which arbitrators chaired the largest awards last year?"*

### Troubleshooting

**Why am I getting no results?**

A filter combination can be empty: `panelCompositions` tags only 6,000 of the 66,600 documents, and `documentTypes: ["Motion to Confirm"]` matches 27 in the whole archive. Drop one filter at a time. Case numbers must be exact, in FINRA's own format (`24-00627`, `2007-016751`).

**Why fewer rows than I asked for?**

Your date range, filters and local filters (`partyNameContains`, `arbitratorNameContains`, `hearingSites`) may simply match fewer awards than `maxItems`. The run log prints how many each search chain returned.

**Why does a search term return fewer awards than FINRA's website?**

FINRA's own search is fuzzy: `12206` returns awards that never mention Rule 12206, because for awards issued by FINRA (July 2007 onwards) its index only holds the parties, arbitrators and case number. This Actor checks each award's text and drops those, so the count is smaller and every row is a real hit. Give a date range (`dateFrom` and `dateTo`) and every award in it is checked, which is the only way to find a term inside a recent award; without one the Actor can only verify the candidates FINRA's index hands out, and the log says so.

**Why is a search run slower than a browse run?**

Every award in the range is downloaded (about 100 KB) and parsed to check for your term, roughly 0.7 seconds per award at the default 512 MB (577 awards took 6.5 minutes). About 1,400 awards fit in the default 20-minute timeout; raise the run timeout for a larger range, up to 4,000 awards per run.

**Why is a damages field zero?**

Because the panel awarded nothing under that head. Expungement-only awards decide no money at all and come back with `claimsDenied: "N/A"`; awards that denied the claims come back `claimsDenied: "Yes"`. Both are the award's real content.

**Why does an award have no parsed sections?**

About 7% of the archive is a scanned image with no text layer, including a few recent ones. Those rows say `documentTextStatus: "Scanned image with no machine-readable text"`, keep the index fields, and are not charged for the document or any extraction.

**Why is the run slow?**

The search index hands out one page of 15 results at a time and rate limits bursts, so a wide date range is walked month by month across several connections. 900 index rows take about 23 seconds; parsing PDFs adds roughly one second per award. Raise the run's memory to give the PDF parser more CPU.

### FAQ

| Question | Answer |
|---|---|
| Is this data public? | Yes. FINRA publishes every award in Arbitration Awards Online for anyone to read, and this Actor reads only that public index and those public PDFs. |
| How far back does it go? | To 1988, when the NASD forum begins. NASD covers 36,421 documents, FINRA 25,449, and the exchange forums (NYSE, CBOE, AMEX, MSRB, Pacific Exchange/ARCA, PHLX) the rest. |
| How current is it? | Awards appear in the index within days of service. The archive returned an award dated the previous business day during testing. |
| Can I search the text of the awards? | Yes, and every hit is verified. With a date range the Actor downloads every award in it and keeps only those whose text contains the term. Without a date range it relies on FINRA's index, which for awards after July 2007 only covers parties, arbitrators and case numbers; those hits are still checked against the PDF before they are returned or charged. |
| Does it give me the award amounts? | Yes, with `includeMonetaryTerms`. Compensatory, punitive, attorney fees, expert fees, costs, the total, the interest rate and the amount originally requested. |
| Can I filter by arbitrator? | Yes. `arbitratorNameContains` keeps only awards that arbitrator decided, and `includeArbitratorPanel` adds their role on the panel. |
| What is an expunged award? | One FINRA has removed from a broker's CRD record. The index flags 1,350 of them, and `includeExpungementDetail` returns the occurrence numbers, CRD numbers and the Rule 2080 findings behind the ruling. |
| Why do some cases return two rows? | FINRA sometimes files more than one document under a case, such as a corrected award or a motion to vacate. Each document is its own row; `hasRelatedCases` marks them and `includeRelatedCases` lists the siblings. |
| How many awards per run? | Free plan: 10. Paid: up to 1,000,000, bounded by what your filters match. |
| Is this an official FINRA product? | No. It is unofficial and reads only public FINRA data. |

### Related actors

- [FINRA BrokerCheck Scraper](https://apify.com/parseforge/finra-brokercheck-scraper?fpr=vmoqkp): broker and firm registration records, disclosures and exams.
- [SEC Litigation Releases Scraper](https://apify.com/parseforge/sec-litigation-releases-scraper?fpr=vmoqkp): SEC enforcement actions with defendants and case links.
- [CourtListener Dockets Scraper](https://apify.com/parseforge/courtlistener-dockets-scraper?fpr=vmoqkp): federal and state docket entries by party and case number.

Browse the full [ParseForge collection](https://apify.com/parseforge?fpr=vmoqkp) for more scrapers.

🆘 **Need help?** Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ **Disclaimer.** This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by FINRA. It collects only publicly available data from FINRA's Arbitration Awards Online. Awards name real people, so you are responsible for using the data in compliance with applicable laws, including GDPR, CCPA, and PIPL, and with FINRA's terms. Do not use it to identify, profile, or target individuals.

# Actor input Schema

## `searchTerms` (type: `array`):

Words or phrases that must appear in the award, for example "churning", "Rule 12206" or a firm name. Every hit is checked against the award document before it is returned or charged, so a row always contains the term. Set Awards from and Awards to and the Actor downloads every award in that range and keeps the matches (best recall; about 1,400 awards fit in the default 20-minute timeout, up to 4,000 per run with a longer timeout). Without a date range FINRA's own index supplies the candidates, and for awards issued by FINRA (July 2007 onwards) that index only knows the parties, arbitrators and case number. Each term is searched separately; quotes are ignored. Leave empty to browse awards by date.

## `caseIds` (type: `array`):

Exact FINRA case numbers, for example 24-00627, 09-06787 or 1994-004242. Every document filed under the case (award, orders, motions) is returned.

## `startUrls` (type: `array`):

Paste an Arbitration Awards Online search URL (the filters in the URL are read and applied) or a direct award PDF link from data-portal.finra.org.

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

Free users: limited to 10 items (preview). Paid users: up to 1,000,000.

## `dateFrom` (type: `string`):

Earliest date of award to include, as YYYY-MM-DD. The archive starts in 1988.

## `dateTo` (type: `string`):

Latest date of award to include, as YYYY-MM-DD. Leave empty for today.

## `forums` (type: `array`):

Keep only awards issued by these forums. FINRA (2007 onwards) and NASD (until 2007) hold almost all of the archive; the exchange forums are historical.

## `documentTypes` (type: `array`):

Keep only these document types. Awards are 98% of the archive; the rest are motions and court orders to confirm or vacate an award.

## `panelCompositions` (type: `array`):

Keep only awards decided under one of FINRA's special panel programs. Most awards carry no panel composition tag at all.

## `sortBy` (type: `string`):

Newest first (the index's own order), oldest first, or the search engine's relevance ranking. Relevance only differs from date order when you pass search terms without a date range; a full scan over a date range is always returned in date order.

## `hearingSites` (type: `array`):

Keep only awards whose hearing site matches one of these, for example "New York", "FL" or "Boca Raton, FL". Awards before 2000 rarely publish a hearing site.

## `partyNameContains` (type: `string`):

Keep only awards where this text appears in the claimants, respondents or their representatives, for example "Merrill Lynch" or a broker's surname.

## `arbitratorNameContains` (type: `string`):

Keep only awards decided by an arbitrator whose name contains this text. Useful for researching an arbitrator's record before a hearing.

## `onlyExpunged` (type: `boolean`):

Keep only awards FINRA has flagged as expunged from the CRD registration records (about 2% of the archive).

## `onlyWithRelatedCases` (type: `boolean`):

Keep only cases that have more than one document on file, such as an award plus a motion or a court order.

## `includeAwardDocument` (type: `boolean`):

Download each award PDF and extract its text, adding the page count, character count and the list of sections found. Required for every extraction below, and charged once per award however many of them you turn on.

## `includeFullText` (type: `boolean`):

Add the complete text of the award document to the row, up to 200,000 characters.

## `includeMonetaryTerms` (type: `boolean`):

Parse the AWARD section: compensatory, punitive, attorney fees, expert fees and costs awarded, the total, the interest rate and start date, the amount originally requested, and whether the claims were denied.

## `includeFeeBreakdown` (type: `boolean`):

Parse the FEES section: filing fees, member surcharge and process fee, total hearing session fees, the number of hearing sessions and who each assessment was charged to.

## `includeExpungementDetail` (type: `boolean`):

Parse the expungement ruling: requested, granted or denied, the CRD occurrence numbers, the registered persons with their CRD numbers, the Rule 2080 affirmative findings and whether court confirmation is required.

## `includeArbitratorPanel` (type: `boolean`):

Parse the arbitration panel block: each arbitrator with their role (public, non-public, presiding chairperson), the panel size and the chairperson.

## `includeRepresentation` (type: `boolean`):

Parse the representation of parties: counsel for each side, their law firms, and whether a party appeared pro se.

## `includeCausesOfAction` (type: `boolean`):

Parse the causes of action asserted in the statement of claim into a list, for example breach of fiduciary duty, unsuitability, misrepresentation.

## `includeCaseTimeline` (type: `boolean`):

Parse the case dates: nature of the dispute, statement of claim filed, statement of answer filed, submission agreement dates and every hearing date.

## `includeCaseNarrative` (type: `boolean`):

Add the text of the CASE SUMMARY, RELIEF REQUESTED, OTHER ISSUES CONSIDERED AND DECIDED and AWARD sections as separate fields.

## `includeRelatedCases` (type: `boolean`):

For cases flagged as having related documents, look up every other document filed under the same case number and attach them with their type, date and PDF link.

## Actor input object example

```json
{
  "maxItems": 10,
  "sortBy": "newest",
  "onlyExpunged": false,
  "onlyWithRelatedCases": false,
  "includeAwardDocument": false,
  "includeFullText": false,
  "includeMonetaryTerms": false,
  "includeFeeBreakdown": false,
  "includeExpungementDetail": false,
  "includeArbitratorPanel": false,
  "includeRepresentation": false,
  "includeCausesOfAction": false,
  "includeCaseTimeline": false,
  "includeCaseNarrative": false,
  "includeRelatedCases": false
}
```

# Actor output Schema

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

No description

## `awards` (type: `string`):

No description

## `csv` (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 = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/finra-arbitration-awards-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 = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("parseforge/finra-arbitration-awards-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 '{
  "maxItems": 10
}' |
apify call parseforge/finra-arbitration-awards-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parseforge/finra-arbitration-awards-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/IyOHboQx1eWyKDoEN/builds/zXz4WmuQATkuXOqvO/openapi.json