Signals

Create Influencer Engagement signal

Get the people who engage with specific LinkedIn influencers' or thought leaders' posts — those actively reacting to or commenting on content in your space, a strong intent signal.

Input: LinkedIn profile URLs of the influencers/creators to monitor (linkedinUrls); optionally specific postUrls, a look-back window (postedLimit), and engagementTypes, an array choosing who becomes a lead: likes (people who reacted), comments (people who commented), poster (the post author) and both (people who reacted AND commented), combinable; defaults to [likes, comments]. Optional excludedCommentKeywords skips people whose comment is only a polite reaction — e.g. ["félicitations", "bravo", "congrats"] on a post announcing a new job; matched as whole words, ignoring case and accents; reactions are never affected.

Output: each person selected by engagementTypes on those posts who matches your persona/ICP config is pushed to your webhookUrl as an enriched lead; non-matching engagers are filtered out.

Use cases:

  • Influencer-audience capture — reach the engaged audience of your space's thought leaders.
  • Topic targeting — engagers on a niche influencer signal interest in that niche.
post/api/v1/signals/influencer-engagement

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/influencer-engagement
  • 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": {
    "companySizeFilters": [],
    "customPersonaTitles": [],
    "detectTechnologies": false,
    "engagementTypes": [
      "likes",
      "comments"
    ],
    "excludedCommentKeywords": [
      "félicitations",
      "bravo",
      "congrats"
    ],
    "excludedCompanySizeFilters": [],
    "excludedCompanyUrls": [],
    "excludedIndustryFilters": [
      "Financial Services"
    ],
    "excludedLocations": [],
    "excludedTitles": [
      "Intern",
      "Junior"
    ],
    "getEmails": true,
    "getHomepageContent": false,
    "getPhones": false,
    "getSireneData": false,
    "industryFilters": [],
    "linkedinUrls": [
      "https://www.linkedin.com/in/guillaumemoubeche"
    ],
    "locations": [],
    "maxPosts": 0,
    "minEngagement": 5,
    "postedLimit": "week",
    "targetPersonas": []
  },
  "dailyLeadLimit": 50,
  "name": "Influencer engagement tracking",
  "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.