# Bank Mergers & Acquisitions: Federal Reserve Applications (`quarrylane-data/fed-bank-holding-company-applications`) Actor

Bank mergers, acquisitions and holding company applications filed with the Federal Reserve, from official Federal Register notices: applicant, target bank, Reserve Bank, comment deadline. New-applications-only monitor mode. No API key.

- **URL**: https://apify.com/quarrylane-data/fed-bank-holding-company-applications.md
- **Developed by:** [Quarrylane Data](https://apify.com/quarrylane-data) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $21.00 / 1,000 federal reserve applications

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

## Federal Reserve Bank M\&A & Holding Company Applications Monitor

Get every **bank acquisition, bank holding company merger, new holding company formation and nonbanking-activity application** filed with the **Federal Reserve**, as soon as the Board publishes the public notice — typically **30 days before the comment deadline** and months before the deal closes. Includes fintechs applying to own banks (recent examples: **Chime**, **Upstart**, **TabaPay**), community bank M\&A and ESOP control filings.

Data comes from the official, **keyless** [Federal Register API](https://www.federalregister.gov/developers/documentation/api/v1): the Board's weekly *Formations of, Acquisitions by, and Mergers of Bank Holding Companies* notices (plus savings and loan holding company and nonbanking-activity notices). Each item is parsed into structured fields. Turn on **monitor mode** for a daily or weekly feed of only **new applications**.

### What does this Actor do?

Bank M\&A data products usually report a deal after it is announced or closed. The Fed notice is the regulatory filing itself: applicant, what it wants to acquire or merge with, the bank it would control, the handling Reserve Bank and the public comment deadline. This Actor lists the Board's notices in your window, reads each notice's text, splits it into individual applications, classifies the transaction and extracts the target company, target bank and location.

### Who uses it?

- **Bank M\&A advisers, investment banks and law firms** — deal pipeline and comment-deadline tracking
- **Core-banking, data-conversion and fintech vendors** — banks entering a conversion or integration project
- **Bank investors, analysts and journalists** — community bank consolidation and fintech bank-charter strategies
- **Community groups** — CRA comment periods on mergers
- **Clay, n8n and Make** workflows that push new filings into a CRM or Slack

### Input

| Field | What it does |
|---|---|
| `daysBack` / `startDate` / `endDate` | Federal Register publication window. Default: last **60 days**. |
| `noticeTypes` | `bhc` (bank holding companies), `slhc` (savings and loan holding companies), `nonbanking`. Default all. |
| `transactionTypes` | `holding-company-formation`, `acquisition`, `merger`, `nonbanking-activity`, `retain-shares`, `other`. |
| `states` | Two-letter states matched on applicant **or** target location. |
| `reserveBanks` | Federal Reserve Bank district, e.g. `Dallas`, `San Francisco`. |
| `keyword` | Text match on applicant or proposal, e.g. `ESOP`. |
| `onlyNew` + `monitorName` | Monitor mode: later runs return (and charge for) only applications not seen before. The first run bills up to `maxItems` as standard records and seeds the rest of the window without charging. |
| `maxItems` | Default **15** (fast, auto-test safe). Free plans are capped at 15. |

#### Example input

```json
{
  "daysBack": 365,
  "transactionTypes": ["acquisition", "merger"],
  "states": ["TX", "OK"],
  "maxItems": 100
}
```

### Output

Sample from a real run of this Actor (person-name and personal contact fields masked in this README only; long text and lists shortened):

```json
[
  {
    "recordId": "2026-23245#1",
    "frDocumentNumber": "2026-23245",
    "itemNumber": 1,
    "applicantName": "Third Coast Bancshares, Inc.",
    "applicantCity": "Humble",
    "applicantState": "TX",
    "applicantCountry": "US",
    "proposal": "to acquire Great Plains Bancshares, Inc., and thereby indirectly acquire Great Plains National Bank, both of Elk City, Oklahoma.",
    "transactionType": "acquisition",
    "reserveBank": "Dallas",
    "correctsDocument": null,
    "targetCompany": "Great Plains Bancshares, Inc.",
    "targetBank": "Great Plains National Bank",
    "targetCity": "Elk City",
    "targetState": "OK",
    "commentDeadline": "2026-12-16",
    "noticeType": "bhc",
    "noticeTitle": "Formations of, Acquisitions by, and Mergers of Bank Holding Companies",
    "publicationDate": "2026-11-16",
    "frCitation": "91 FR 73582",
    "frUrl": "https://www.federalregister.gov/documents/2026/11/16/2026-23245/formations-of-acquisitions-by-and-mergers-of-bank-holding-companies",
    "frPdfUrl": "https://www.govinfo.gov/content/pkg/FR-2026-11-16/pdf/2026-23245.pdf",
    "source": "Federal Register notices of the Board of Governors of the Federal Reserve System",
    "scrapedAt": "2026-11-17T23:17:36.957Z"
  },
  {
    "recordId": "2026-22599#1",
    "frDocumentNumber": "2026-22599",
    "itemNumber": 1,
    "applicantName": "Pinnacle Bancorp, Inc.",
    "applicantCity": "Omaha",
    "applicantState": "NE",
    "applicantCountry": "US",
    "proposal": "to merge with Southern Bancshares, Inc., Houston, Texas, and thereby indirectly acquire Southstar Bank, S.S.B., Moulton, Texas.",
    "transactionType": "merger",
    "reserveBank": "Kansas City",
    "correctsDocument": null,
    "targetCompany": "Southern Bancshares, Inc.",
    "targetBank": "Southstar Bank",
    "targetCity": null,
    "targetState": null,
    "commentDeadline": "2026-12-07",
    "noticeType": "bhc",
    "noticeTitle": "Formations of, Acquisitions by, and Mergers of Bank Holding Companies",
    "publicationDate": "2026-11-05",
    "frCitation": "91 FR 69847",
    "frUrl": "https://www.federalregister.gov/documents/2026/11/05/2026-22599/formations-of-acquisitions-by-and-mergers-of-bank-holding-companies",
    "frPdfUrl": "https://www.govinfo.gov/content/pkg/FR-2026-11-05/pdf/2026-22599.pdf",
    "source": "Federal Register notices of the Board of Governors of the Federal Reserve System",
    "scrapedAt": "2026-11-17T23:17:36.957Z"
  }
]
```

Also returned: `applicantCountry`, `noticeType`, `noticeTitle`, `frDocumentNumber`, `itemNumber`, `frCitation`, `frPdfUrl`, `correctsDocument` (for correction notices) and `scrapedAt`.

### Pricing

Pay per result, with no monthly rental:

| Event | Price |
|---|---|
| Application (`application-record`) | **$0.03 per application ($30 per 1,000)** |
| New application (`new-application`, later monitor-mode runs) | **$0.05 per application ($50 per 1,000)** |

The Fed publishes roughly 100–200 such applications a year nationwide, so a full year of history costs a few dollars and a weekly monitor costs cents. Set **Max cost per run** for a hard budget. Free Apify plans are capped at 15 results per run.

#### Price per event and Store discounts

| Event | Charged for | Free plan | Bronze | Silver | Gold | Per 1,000 (Free plan) |
|---|---|---|---|---|---|---|
| Federal Reserve application (`application-record`) | Charged for each Federal Reserve holding company application saved in a standard run, including the first run of a monitor. | $0.03 | $0.027 | $0.024 | $0.021 | $30.00 |
| New Federal Reserve application (monitor) (`new-application`) | Charged instead of the standard record for each application delivered on a later run when monitor mode (onlyNew) is on and this monitor name has already been used. | $0.05 | $0.045 | $0.04 | $0.035 | $50.00 |

Prices are in USD per event. This Actor is pay-per-event only: there is no monthly rental and no separate platform usage charge on top, because compute is included in the event price. Apify Bronze, Silver and Gold subscribers get the discounted prices automatically. Set **Max cost per run** in the run options to cap spend, and the Actor stops before it goes over.

### Data notes

- **Organisations only.** Change in Bank Control notices (mostly individuals buying bank shares) are not included, applications whose applicant is not an organisation are withheld, and trustee names are redacted. Federal Reserve staff names and e-mail addresses are never copied.
- Text parsing is heuristic: `proposal` always holds the full published wording, and the structured target fields are best-effort.
- Requests go only to federalregister.gov, send an identifying User-Agent, are spaced politely, time out after 45 seconds and are retried with backoff.

### How to automate with Clay.com, n8n, Make, and Claude MCP

All examples use this Actor's Store ID `quarrylane-data/fed-bank-holding-company-applications`. Replace `YOUR_APIFY_TOKEN` with your Apify API token (Console → Settings → API & Integrations). Never paste a token into a public workflow.

#### Official Apify API (run-sync-get-dataset-items)

```bash
curl -sS -X POST \
  "https://api.apify.com/v2/acts/quarrylane-data~fed-bank-holding-company-applications/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"daysBack":90,"transactionTypes":["acquisition","merger"],"maxItems":15}'
```

For a weekly feed, pass `"onlyNew": true` and a stable `"monitorName"`, then schedule the Actor in Apify.

#### n8n

- **Apify node** (community, `n8n-nodes-apify`): add the Apify credentials, choose **Run Actor**, set the Actor to `quarrylane-data/fed-bank-holding-company-applications`, and paste the JSON input above. Use "wait for finish", then read the default dataset.
- **HTTP Request node**: Method `POST`, URL `https://api.apify.com/v2/acts/quarrylane-data~fed-bank-holding-company-applications/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN`, header `Content-Type: application/json`, body as JSON.

#### Make (Integromat)

Use the **Apify** module's **Run an Actor** action (or an HTTP module with the endpoint above). After the run finishes, use **Get Dataset Items**, or call `run-sync-get-dataset-items` in a single HTTP module.

#### Clay.com

Add an **HTTP API** enrichment column:

- Method: `POST`
- URL: `https://api.apify.com/v2/acts/quarrylane-data~fed-bank-holding-company-applications/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN`
- Headers: `Content-Type: application/json`
- Body: `{"daysBack":30,"maxItems":15}`

Map `applicantName`, `targetCompany`, `targetBank`, `targetState`, `transactionType` and `commentDeadline` into Clay columns, then find each bank's website and executives with your usual Clay providers.

#### Claude and the Apify MCP server

This Actor is MCP-compatible (limited permissions). Point Claude, Cursor, or any MCP client at Apify's hosted server and include this Actor in the `tools` query parameter:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=quarrylane-data/fed-bank-holding-company-applications"
    }
  }
}
```

On first connect, sign in to Apify (OAuth) or send an `Authorization: Bearer YOUR_APIFY_TOKEN` header. In Claude, you can also add `https://mcp.apify.com?tools=quarrylane-data/fed-bank-holding-company-applications` as a custom connector under Settings → Connectors. Then ask Claude to "list bank acquisitions filed with the Federal Reserve in Texas this quarter."

### Is it legal to use this data?

Yes. These are public notices published by the Board of Governors of the Federal Reserve System in the Federal Register, accessed through the Federal Register's documented public API with no key and no login. Records describe **banks and holding companies**, not private consumer data.

Built by **Quarrylane Data**. Not affiliated with the Federal Reserve or the Office of the Federal Register.

### More US public-record lead data by Quarrylane Data

| Actor | What you get |
|---|---|
| [NYS Contract Reporter Bids & RFPs](https://apify.com/quarrylane-data/nys-contract-reporter-bids-scraper) | New York State government bids, RFPs, RFQs and grants with due dates and links |
| [US Contractor License Leads (9 states)](https://apify.com/quarrylane-data/us-contractor-license-leads) | Official contractor licences from 9 state registries with phone, address and status |
| [MWBE, DBE & Diversity-Certified Business Leads](https://apify.com/quarrylane-data/us-diversity-certified-business-leads) | Officially certified minority, women-owned and disadvantaged businesses |
| [Texas TDLR Contractor License Leads](https://apify.com/quarrylane-data/texas-tdlr-contractor-license-leads) | Texas TDLR licence holders (HVAC, electricians and more) with phone and address |
| [US Federal Contract Awards (USAspending)](https://apify.com/quarrylane-data/usaspending-federal-contract-awards) | Recent federal prime contract awards and the companies that won them |
| [NPPES NPI New Provider Leads](https://apify.com/quarrylane-data/nppes-npi-new-provider-leads) | Newly registered medical practices and providers from the official CMS NPI file |
| [FMCSA New Authority Leads](https://apify.com/quarrylane-data/fmcsa-new-authority-leads) | Newly granted USDOT / MC trucking authorities with carrier census details |
| [EPA Enforcement Case Leads](https://apify.com/quarrylane-data/epa-enforcement-case-leads) | EPA and state environmental enforcement cases with penalties and facilities |
| [OCC Bank Applications Monitor](https://apify.com/quarrylane-data/occ-bank-applications-monitor) | OCC bank charter, branch, merger and control applications |

# Actor input Schema

## `daysBack` (type: `integer`):

Federal Register publication dates in the last N days. Default 60.

## `startDate` (type: `string`):

First Federal Register publication date to include, as YYYY-MM-DD (inclusive). When set, it overrides "Days back".

## `endDate` (type: `string`):

Last publication date to include, as YYYY-MM-DD (inclusive). Defaults to today.

## `noticeTypes` (type: `array`):

Which Federal Reserve notice types to include: bank holding company deals, savings and loan holding company deals, and/or nonbanking activity proposals. Leave empty for all three.

## `transactionTypes` (type: `array`):

Only return these transaction types (classified from the notice text): becoming a holding company, acquisition, merger, nonbanking activity, retaining shares, or other. Leave empty for all.

## `states` (type: `array`):

Two-letter states matched on the applicant or target location, e.g. TX, OK.

## `reserveBanks` (type: `array`):

Only return applications handled by these Federal Reserve Bank districts, e.g. New York or Dallas. Leave empty for all 12.

## `keyword` (type: `string`):

Optional text match on applicant or proposal, e.g. Chime or ESOP.

## `onlyNew` (type: `boolean`):

Later runs return only applications not seen before under this monitor key. The first run bills up to maxItems as application-record events and seeds the rest without charging. Later runs bill new-application events.

## `monitorName` (type: `string`):

Label for this saved monitor (plain text, not a password or API key). When "Only new" monitor mode is on, the Actor remembers which records it has already delivered under this name and returns only new ones next time. Use a different name per filter set or client, for example "client-a-weekly". Older inputs that use monitorKey still work.

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

Default 15 (fast, auto-test safe). Free Apify plans are capped at 15.

## Actor input object example

```json
{
  "daysBack": 60,
  "onlyNew": false,
  "monitorName": "default",
  "maxItems": 15
}
```

# Actor output Schema

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

Applications (applicant, location, transaction type, target company and bank, Reserve Bank, comment deadline, Federal Register links).

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quarrylane-data/fed-bank-holding-company-applications").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("quarrylane-data/fed-bank-holding-company-applications").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 '{}' |
apify call quarrylane-data/fed-bank-holding-company-applications --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quarrylane-data/fed-bank-holding-company-applications"
        }
    }
}
```

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/4ehRzq8niEXSdrMfP/builds/W0VjrHsUK8fV7DK13/openapi.json
