Signals

Create Mergers & Acquisitions signal

Track companies making acquisitions or merging in your target markets — surface the acquiring company as a sales opportunity the moment a deal is announced, with optional enrichment of its key decision-makers. Acquisitions often trigger budget, integration, and new-tooling needs you can act on early.

Input: deal types (dealTypes: acquisition, merger, leveraged_buyout, management_buyout); minimum deal size (minAmount, in USD); recency window (announcedPeriod: 24h, 7d, 30d, 60d, 90d, 12m, or custom); ICP filters — applied to the acquiring company — (industryFilters, companySizeFilters, hqLocations, each with an excluded* counterpart); optional persona targeting to reach executives at the acquirer (enablePersonaTargeting, targetPersonas, customPersonaTitles); optional enrichment flags (getEmails, getPhones, getSireneData, detectTechnologies, getHomepageContent).

Output: each qualifying deal is pushed to your webhookUrl as it's announced, carrying both sides of the transaction — acquirer and acquired-company names, websites, industries, and locations — plus the deal type, deal price in USD (with currency), announcement date, and an AI-generated article summary and acquisition rationale. The lead's company is the acquirer. If persona targeting is enabled, matched executives at the acquirer are attached as the contact; otherwise contact is empty. Requested enrichments are included when available.

Use cases:

  • Consolidation plays — post-M&A, tools and systems get re-evaluated and consolidated; pitch the platform that wins.
  • Integration services — offer migration / integration help during the merge.
post/api/v1/signals/mergers-acquisitions

Request

  • Base URL: https://api.rodz.io (the document declares no server; this is the origin it was published from)
  • URL: https://api.rodz.io/api/v1/signals/mergers-acquisitions
  • Auth: HTTP bearer

Request body

namestring required

Name for this signal

webhookUrlstring nullable

Where each lead is POSTed as it is produced. Optional (since 2026-09-23): omit it when you read leads with GET /api/v1/signals/{signalId}/leads or route them to a connected CRM or sequencer with destinations on PATCH /api/v1/signals/{signalId}.

dailyLeadLimitinteger

Max leads per day

duplicateHandlingstring nullable

Duplicate lead handling: 'refuse' (never accept), 'allow' (always accept), or 'Xd' (accept a duplicate after X days, e.g. '7d'). Optional — defaults to 'allow', so a contact who triggers this signal a second time is delivered a second time.

statusstring nullable

Initial status (default: draft). Accepts draft, active, or paused. If active, mandatory config fields are validated.

Example request

{
  "config": {
    "announcedPeriod": "30d",
    "companySizeFilters": [
      "51-200",
      "201-500"
    ],
    "customPersonaTitles": [
      "Chief Strategy Officer"
    ],
    "dealTypes": [
      "acquisition",
      "merger"
    ],
    "detectTechnologies": false,
    "enablePersonaTargeting": true,
    "getEmails": true,
    "getHomepageContent": false,
    "getPhones": false,
    "getSireneData": false,
    "hqLocations": [
      "France",
      "United Kingdom"
    ],
    "industryFilters": [
      "Software Development",
      "IT Services and IT Consulting"
    ],
    "minAmount": 500000,
    "personaExportMode": "top_ranked",
    "personaLocations": [],
    "targetPersonas": [
      "CEO",
      "Finance Director"
    ]
  },
  "dailyLeadLimit": 50,
  "name": "SaaS acquisitions in Europe",
  "status": "active",
  "webhookUrl": "https://your-server.com/webhooks/rodz"
}

Response

Signal created

idstring required
namestring required
statusstring required
signalTypeIdstring required
webhookUrlstring nullable
configobject nullable

Signal-specific configuration

dailyLeadLimitinteger required
leadsTodayinteger required
leadsTotalinteger required
duplicateHandlingstring required

Duplicate lead handling: 'refuse' (never accept), 'allow' (always accept), or 'Xd' (accept after X days)

createdAtstring required
updatedAtstring required
lastLeadAtstring nullable
appliedobject

Settings this signal runs with where they differ from config, keyed like config. {} when every stored setting is applied as stored. A null value means the stored field is not used by this signal. Every entry is explained by a warning naming the same field.

Example response

{
  "applied": {
    "allowUnknownCompanySize": false,
    "maxJobAgeDays": 180
  },
  "config": {
    "companySizeFilters": [
      "201-500",
      "501-1000"
    ],
    "getEmails": true,
    "jobTitles": [
      "CTO"
    ],
    "locations": [
      "France"
    ],
    "maxJobAgeDays": 90
  },
  "createdAt": "2026-01-15T10:30:00Z",
  "dailyLeadLimit": 50,
  "duplicateHandling": "refuse",
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "lastLeadAt": "2026-03-15T14:22:00Z",
  "leadsToday": 3,
  "leadsTotal": 127,
  "name": "CTOs changing jobs in France",
  "signalTypeId": "job_changes",
  "status": "active",
  "updatedAt": "2026-03-16T08:00:00Z",
  "warnings": [
    {
      "code": "VALUE_BELOW_MINIMUM",
      "field": "maxJobAgeDays",
      "message": "`maxJobAgeDays` is 90; this signal applies 180. Job changes are delivered up to 180 days after the start date, and a shorter window is raised to that minimum.",
      "severity": "info",
      "values": [
        "90"
      ]
    }
  ],
  "webhookUrl": "https://your-server.com/webhooks/rodz"
}

Changes

No recorded changes to this operation across all 1 revision of this API.