Financial Signals: Fundraising, M&A and Registrations via Rodz

In a nutshell: The Rodz API exposes three financial signal types, fundraising, mergers-acquisitions and company-registration, that let you detect companies at inflection points where budgets shift and decisions get made. This guide explains what each signal detects, when to use it, how to configure it with cURL, what the webhook payload looks like, and how to combine all three into a unified prospecting workflow.

What Are Financial Signals?

Financial signals are business events tied to capital movement, corporate restructuring, or legal entity creation. They sit at the intersection of public records, press coverage and regulatory filings. Unlike behavioral intent data (social engagement, website visits), financial signals are factual. A company either raised a Series B or it did not. A merger either closed or it did not. A new entity was either registered or it was not.

This makes them some of the most reliable triggers for outbound sales. When a company raises funding, it has fresh capital and pressure to deploy it. When two organizations merge, the combined entity reassesses every vendor relationship. When a new company registers, it needs everything from accounting software to office chairs.

The Rodz API groups these three event types under the financial signals category. Each one is a distinct signal type you can configure independently, with its own filters, thresholds and webhook payloads. You can run them separately or combine them into a multi-signal strategy that covers the full spectrum of capital-related buying triggers.

This article is part of the Rodz API technical guide series. If you need a broader view of all available endpoints, rate limits and response formats, see the API Reference.

Prerequisites

Before configuring financial signals, make sure you have the following ready:

1. A Rodz account with API access enabled. API access is available on all paid plans. Register at app.rodz.io if you have not already.
2. Your API key, generated from the Rodz dashboard under Settings > API Keys. If you need help with this step, follow the authentication and first request guide.
3. cURL installed on your machine. macOS and Linux ship with it by default. Windows users can use Git Bash or WSL.
4. A configured webhook endpoint (optional but recommended). Financial signals are most powerful when delivered in real time. See How to Set Up Rodz Webhooks for a full walkthrough.
5. A clear Ideal Customer Profile (ICP). Financial signals generate a lot of matches. Knowing your target industries, geographies and company sizes will help you set effective filters from the start.

Set your API key as an environment variable so the examples below stay clean:

export RODZ_API_KEY="your_api_key_here"

All requests go to the base URL https://api.rodz.io/v1. Authentication is handled via a Bearer token in the Authorization header.

Signal Type 1: Fundraising

What It Detects

The fundraising signal type monitors funding events across the startup and scale-up ecosystem. It covers seed rounds, Series A through D, growth equity, venture debt, and undisclosed rounds. Rodz aggregates data from regulatory filings, press releases, investor announcements and financial databases to surface funding events as close to the announcement date as possible.

Each match includes the company name, funding amount, round type, lead investors, date of announcement, and a link to the original source when available. This gives your sales team enough context to write a relevant opening line without any additional research.

When to Use It

Fundraising signals are most valuable when your product or service helps companies scale. If you sell hiring tools, marketing platforms, CRM software, cloud infrastructure, or consulting services, a freshly funded company is a textbook ideal prospect. The budget is approved. The mandate is to grow. The window of opportunity is narrow, typically 30 to 90 days after the announcement, before the company has committed its new capital to specific vendors.

Use this signal when:

• Your average deal size fits the post-funding budget range. A company that just raised a $2M seed round is unlikely to sign a $500K annual contract.
• You sell into growth-stage companies (typically Series A to C).
• You want to time your outreach to the exact moment decision-makers are evaluating new solutions.
• You are building account lists for ABM campaigns triggered by financial events.

cURL Example: Creating a Fundraising Signal

curl -X POST https://api.rodz.io/v1/signals \
  -H "Authorization: Bearer $RODZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Series A-C in SaaS (Europe)",
    "type": "fundraising",
    "filters": {
      "round_types": ["series_a", "series_b", "series_c"],
      "min_amount": 5000000,
      "max_amount": 100000000,
      "currency": "EUR",
      "industries": ["saas", "fintech", "martech"],
      "geographies": ["FR", "DE", "NL", "BE", "ES"],
      "company_size": {
        "min_employees": 20,
        "max_employees": 500
      }
    },
    "active": true
  }'

The response returns the full signal configuration object, including the generated id you will use to query matches or update the configuration later.

Webhook Payload

When a fundraising signal fires, Rodz sends a POST request to your registered webhook endpoint with the following structure:

{
  "event_type": "signal.matched",
  "signal_id": "sig_fnd_7x9k2m",
  "signal_type": "fundraising",
  "timestamp": "2026-03-06T09:15:32Z",
  "company": {
    "id": "comp_48fj29",
    "name": "Acme SaaS",
    "domain": "acmesaas.com",
    "industry": "saas",
    "employee_count": 85,
    "country": "FR",
    "linkedin_url": "https://linkedin.com/company/acmesaas"
  },
  "signal_data": {
    "round_type": "series_b",
    "amount": 25000000,
    "currency": "EUR",
    "lead_investors": ["Summit Partners", "Partech"],
    "announced_date": "2026-03-05",
    "source_url": "https://example.com/acme-series-b-announcement"
  }
}

The signal_data object changes depending on the signal type. For fundraising, it always includes round_type, amount, currency and announced_date. The lead_investors and source_url fields are included when available.

Use Case: Automated Post-Funding Outreach

A sales development team selling project management software configures a fundraising signal for Series A and B rounds in the technology sector, filtered to companies with 30 to 200 employees in Western Europe. When the webhook fires, a serverless function picks up the payload, enriches the company with decision-maker contacts via the Rodz enrichment endpoint, and pushes the contact into a dedicated outbound sequence. The email references the specific funding round and congratulates the team, then positions the product as a tool to manage the operational complexity that comes with scaling. Response rates on funding-triggered sequences consistently outperform generic cold outreach because the timing and relevance are built into the trigger itself.

Signal Type 2: Mergers and Acquisitions

What It Detects

The mergers-acquisitions signal type captures M&A activity: full acquisitions, majority stake purchases, mergers of equals, and acqui-hires. Rodz monitors press releases, regulatory filings, stock exchange announcements and financial news sources to detect these events. Each match identifies the acquiring company, the target company, the deal type, the announced or estimated deal value (when disclosed), and the date of the event.

M&A signals are inherently more complex than fundraising signals because two companies are involved. The webhook payload reflects this by including data for both the acquirer and the target. You can filter by either side of the transaction.

When to Use It

M&A events create vendor displacement opportunities. When two companies merge, they rarely keep both sets of tools. One CRM gets chosen over the other. One project management tool survives. One cloud provider wins the consolidated contract. If you sell a product that competes with a tool used by either the acquirer or the target, the post-merger integration window is your chance to get in front of the decision.

Use this signal when:

• You sell enterprise software where vendor consolidation is common after mergers.
• You offer integration, migration, or consulting services that help companies unify their tech stacks.
• You target industries with high M&A activity (financial services, healthcare, technology, manufacturing).
• You want to identify companies going through organizational change, which often loosens buying criteria and accelerates purchasing decisions.

Post-merger prospecting requires speed. The vendor reassessment window is typically three to six months after the deal closes. Reaching out with a relevant message during that period puts you in the conversation at the right time.

cURL Example: Creating an M&A Signal

curl -X POST https://api.rodz.io/v1/signals \
  -H "Authorization: Bearer $RODZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "M&A in Financial Services",
    "type": "mergers-acquisitions",
    "filters": {
      "deal_types": ["full_acquisition", "majority_stake", "merger"],
      "industries": ["financial_services", "insurance", "banking"],
      "geographies": ["FR", "DE", "GB", "US"],
      "company_size": {
        "min_employees": 50
      },
      "include_acquirer": true,
      "include_target": true
    },
    "active": true
  }'

The include_acquirer and include_target filters let you control which side of the deal triggers the signal. Set both to true to capture the full picture, or limit to one side when your ICP only matches one profile.

Webhook Payload

{
  "event_type": "signal.matched",
  "signal_id": "sig_ma_3p8w1n",
  "signal_type": "mergers-acquisitions",
  "timestamp": "2026-03-06T14:22:10Z",
  "company": {
    "id": "comp_92kd47",
    "name": "EuroFinance Group",
    "domain": "eurofinancegroup.com",
    "industry": "financial_services",
    "employee_count": 1200,
    "country": "DE",
    "linkedin_url": "https://linkedin.com/company/eurofinancegroup"
  },
  "signal_data": {
    "deal_type": "full_acquisition",
    "role": "acquirer",
    "counterpart": {
      "id": "comp_17bx83",
      "name": "PayStream AG",
      "domain": "paystream.de",
      "industry": "fintech",
      "employee_count": 180,
      "country": "DE"
    },
    "estimated_value": 45000000,
    "currency": "EUR",
    "announced_date": "2026-03-04",
    "source_url": "https://example.com/eurofinance-acquires-paystream"
  }
}

Notice the role field, which indicates whether the matched company is the acquirer or the target. The counterpart object provides details about the other party in the deal. If both include_acquirer and include_target are set to true, you will receive two separate webhook events for the same deal, one for each side.

Use Case: Post-Merger Tech Stack Consolidation

A cloud infrastructure provider configures an M&A signal filtered to technology and financial services companies with more than 100 employees. When the signal fires, the sales team checks whether either company in the deal is already a customer or uses a competing product. If the acquirer is a customer but the target uses a competitor, the rep reaches out to the integration lead with a migration proposal. If neither company is a customer, the team adds both to a nurture sequence that positions their platform as the natural choice for a freshly consolidated organization. The M&A trigger provides a concrete reason for the outreach that feels timely rather than generic.

Signal Type 3: Company Registration

What It Detects

The company-registration signal type flags newly registered legal entities. Rodz pulls from official business registries, chambers of commerce databases, and government filing systems across supported countries. Each match includes the company name, registration number, registration date, legal form, registered address, stated business activity, and the names of the founding directors when available.

This signal is fundamentally different from fundraising and M&A because it captures companies at day zero. There is no track record, no employee count to filter by, and often no website yet. What you get instead is the earliest possible awareness that a new business exists.

When to Use It

New company registrations are valuable when you sell products or services that every business needs from the start. Think accounting software, banking services, legal incorporation packages, office space, insurance, payroll tools, or business phone systems. The earlier you reach out, the more likely you are to be the first (and sometimes only) vendor the founder evaluates.

Use this signal when:

• You sell to small businesses or startups at the pre-revenue or early-revenue stage.
• Your product has a low barrier to entry (free trial, freemium tier, low starting price).
• You target specific industries or legal forms. For example, if you sell compliance software for financial services companies, you can filter for newly registered firms with a stated activity code in that sector.
• You operate in a geography where registry data is reliable and timely (France, Germany, Netherlands, Belgium, UK, and others).

Timing is everything with company registrations. The founders are making purchasing decisions in the first weeks after incorporation. Reaching them during that window, with a relevant offer, puts you ahead of competitors who rely on intent data that only appears months later.

cURL Example: Creating a Company Registration Signal

curl -X POST https://api.rodz.io/v1/signals \
  -H "Authorization: Bearer $RODZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "New Tech Companies in France",
    "type": "company-registration",
    "filters": {
      "geographies": ["FR"],
      "legal_forms": ["SAS", "SASU", "SARL"],
      "activity_codes": ["6201Z", "6202A", "6311Z"],
      "min_capital": 10000
    },
    "active": true
  }'

The activity_codes field uses the official classification codes for each country (NAF/APE codes in France, SIC codes in the UK, WZ codes in Germany). The min_capital filter helps exclude shell companies or dormant registrations by requiring a minimum share capital.

Webhook Payload

{
  "event_type": "signal.matched",
  "signal_id": "sig_reg_5t2v8q",
  "signal_type": "company-registration",
  "timestamp": "2026-03-06T08:45:19Z",
  "company": {
    "id": "comp_63nx91",
    "name": "NovaTech Solutions",
    "domain": null,
    "industry": "technology",
    "employee_count": null,
    "country": "FR",
    "linkedin_url": null
  },
  "signal_data": {
    "registration_number": "912345678",
    "registration_date": "2026-03-05",
    "legal_form": "SAS",
    "activity_code": "6201Z",
    "activity_label": "Computer programming activities",
    "share_capital": 50000,
    "currency": "EUR",
    "registered_address": "15 Rue de la Paix, 75002 Paris, France",
    "founders": [
      {
        "first_name": "Marie",
        "last_name": "Dupont",
        "role": "Président"
      }
    ]
  }
}

Note that domain, employee_count and linkedin_url are often null for newly registered companies. These fields get populated over time as Rodz enriches the company profile. The founders array provides the names and roles of the registered directors, which gives your sales team a direct contact to reach out to.

Use Case: Day-One Banking and Accounting Outreach

A neobank targeting freelancers and small business founders configures a company registration signal filtered to SAS, SASU and micro-enterprise legal forms in France. When a new company registers, the webhook triggers an automated welcome email from the sales team. The email addresses the founder by name (pulled from the founders array), congratulates them on the incorporation, and offers a free business account with no setup fees for the first year. Because the outreach arrives within hours of the registration, it often lands before the founder has even started searching for a banking provider. The conversion rate on these sequences significantly exceeds standard acquisition campaigns.

Combining Financial Signals

Each financial signal type tells a different story, but together they paint a complete picture of capital-related buying triggers. Here is how to think about combining them.

The Multi-Signal Strategy

Running all three financial signals in parallel lets you cover the full lifecycle of capital events:

1. Company registration catches businesses at birth. These prospects need foundational tools and services.
2. Fundraising catches companies at growth inflection points. These prospects have budget and pressure to spend it.
3. Mergers and acquisitions catches companies at structural transitions. These prospects are reassessing vendor relationships.

Each trigger calls for a different messaging angle, but they can all feed into the same CRM pipeline with proper tagging.

Practical Architecture

A recommended setup looks like this:

1. Create one signal configuration per type, each with filters tailored to your ICP.
2. Register a single webhook endpoint that receives all three signal types.
3. In your webhook handler, route events based on the signal_type field.
4. Tag incoming companies in your CRM with the signal type so your sales team knows which angle to use.
5. Apply different SLAs to each signal type. Fundraising signals have the shortest window (30 to 90 days). Company registrations require the fastest response (first 48 hours). M&A signals give you more time (3 to 6 months) but require deeper research.

Here is a simple routing example in your webhook handler:

app.post('/webhooks/rodz', (req, res) => {
  const event = req.body;

  switch (event.signal_type) {
    case 'fundraising':
      handleFundraising(event);
      break;
    case 'mergers-acquisitions':
      handleMergersAcquisitions(event);
      break;
    case 'company-registration':
      handleCompanyRegistration(event);
      break;
  }

  res.status(200).json({ received: true });
});

Deduplication

It is possible for the same company to trigger multiple financial signals within a short period. A newly registered company might raise a seed round within weeks of incorporation. A recently funded company might acquire a smaller competitor. Your webhook handler should deduplicate by company.id and merge signal context rather than creating duplicate records in your CRM.

Prioritization

Not all financial signals carry the same urgency. Consider this priority framework:

• High priority: Fundraising (Series A and above) and M&A events. These involve significant capital and typically lead to purchasing decisions within weeks.
• Medium priority: Seed rounds and early-stage fundraising. The budget is smaller, but the company is actively building its stack.
• Standard priority: Company registrations. Volume is high, conversion rates are lower on a per-lead basis, but the cost of outreach is also low when automated.

Adjust these priorities based on your own sales data. If company registrations convert better for your product than fundraising signals, promote them accordingly.

Frequently Asked Questions

How soon after a funding round does the signal fire?

Rodz processes fundraising data continuously. Most signals fire within 24 to 48 hours of the public announcement. In some cases, particularly with regulatory filings that become public before a press release, the signal can fire before the round is widely reported. The announced_date field in the payload reflects the original announcement date, not the processing date.

Can I filter fundraising signals by specific investors?

Yes. The filters object supports an investors array where you can specify investor names. The signal will only fire when one of the listed investors participates in the round. This is useful if you want to target companies backed by investors known for portfolio support in your domain.

What geographies are supported for company registration signals?

Rodz currently supports company registration data from France, Germany, the Netherlands, Belgium, the United Kingdom, Spain, Italy and the United States. Coverage varies by country. France and the UK have the most comprehensive and timely data because their business registries publish records quickly. Additional countries are added regularly. Check the API documentation for the current list.

How do I distinguish between the acquirer and the target in M&A signals?

The webhook payload includes a role field set to either acquirer or target. If both include_acquirer and include_target are enabled in your signal configuration, you will receive two separate events for the same deal. Each event identifies the matched company in the top-level company object and the other party in the signal_data.counterpart object.

Can I backfill historical financial signals?

Yes. The Rodz API supports historical queries through the /signals/{id}/matches endpoint with date range parameters. You can retrieve matches from up to 12 months in the past. This is useful when setting up a new signal and wanting to populate your pipeline with companies that triggered the signal before your configuration was active. See the API reference for pagination and date filtering details.

What happens if a company appears in both a fundraising and an M&A signal?

Each signal fires independently. If a company raises a round and is later acquired, both events generate separate webhook deliveries. The company.id field is consistent across events, so you can correlate them in your system. As mentioned in the combining section above, your webhook handler should merge context rather than create duplicate CRM records.

Are company registration signals useful outside of Europe?

Yes, though the depth of data varies. European registries tend to publish more structured information (share capital, activity codes, founder names). US registration data from state-level registries includes entity name, registration date, registered agent and state of incorporation, but often lacks detailed activity classification. Rodz normalizes the payload format across countries, so your integration code works the same regardless of geography.

How do I test financial signals without waiting for real events?

The Rodz API provides a test mode. When you create a signal with "test_mode": true, the system generates synthetic events that match your filter criteria. These test events are delivered to your webhook endpoint with a "test": true flag in the payload so you can validate your handler logic without waiting for actual funding rounds, M&A deals, or company registrations to occur. Remove the test_mode flag when you are ready to go live.

---

Financial signals give you a structural advantage in outbound prospecting. They tell you not just which companies to target, but precisely when to reach out and why. If you have not already, explore the full API documentation to see how financial signals fit alongside enrichment, hiring signals and the rest of the Rodz platform. And if you need a refresher on the fundamentals, the getting started guide will have you up and running in under ten minutes.