Signals

Create Forecasted Fundraisings signal

Companies likely to raise — delivered before the round is announced — while budgets are being planned and vendors are still up for debate.

Input: all optional — companySizeFilters, locations, industryFilters (LinkedIn taxonomy, mapped to our forecast industry categories for you) and their excluded* counterparts. Enable enablePersonaTargeting with targetPersonas to add contacts, and getEmails / getPhones for enrichment. There is no forecast-strength parameter: only the strongest tier is ever served.

Output: company-level leads — name, domain, LinkedIn URL, industry, size, location. Contacts are delivered only when persona targeting is on.

Use cases:

  • Get in before the raise — land while the budget is being drafted, not after every vendor has pitched.
  • Tooling expansion — new funding almost always means new headcount and new tools.
  • Warm the relationship — reach out pre-announcement and you are a familiar name when spend unlocks.
post/api/v1/signals/forecasted-funding

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/forecasted-funding
  • 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

statusstring nullable

Initial status (default: draft).

Example request

{
  "config": {
    "companySizeFilters": [
      "11-50",
      "51-200"
    ],
    "getEmails": true,
    "industryFilters": [
      "Software Development"
    ],
    "locations": [
      "France"
    ]
  },
  "dailyLeadLimit": 25,
  "name": "Companies likely to raise (FR/US software, 11-200)",
  "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.