---
title: "Create Social Reactions signal"
method: POST
path: "/api/v1/signals/social-reactions"
tags: ["Signals"]
---

# Create Social Reactions signal

`POST /api/v1/signals/social-reactions`

## 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/social-reactions`
- Auth: HTTP bearer

Get the people engaging with your target LinkedIn posts — everyone who liked, commented, or (optionally) authored them. Use `engagementTypes` to control the mix: combine `"likes"` (reactions) + `"comments"` (commenters) + `"poster"` (author), or use `["poster"]` alone for author-only leads. **Input:** LinkedIn post URLs (`postUrls`), engagement type selection, optional enrichment flags (`getEmails`, `getPhones`, `getSireneData`), and ICP filters (`targetPersonas`, `companySizeFilters`, `industryFilters`, `locations`, `excludedCompanyUrls`). 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 matching your engagement and filter criteria is pushed to your `webhookUrl` as an enriched lead; non-matching engagers are filtered out.

**Use cases:**
- Post-driven leads — turn a high-performing post (yours or a target's) into a warm lead list.
- Warm follow-up — DM or email the people who engaged with a relevant post.

## Request body

- object: Create a Social Reactions signal.
  - `name` string, required: Name for this signal
  - `webhookUrl` string, 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}.
  - `config` SocialReactionsConfig, required: Config for social_reactions — people who reacted to specific POST URLs you supply. Not for watching a person's or a company's whole post history (`company_engagement`, `company_post_reactions`), and not for finding people who stopped posting (`dormant_linkedin_poster`).
    - `excludedCommentKeywords` string[]: Skip people whose COMMENT is just a polite reaction rather than interest. Typical use: on a post announcing a new job, most comments are "Congratulations Marie!" or "Bravo" — list those words and the people who only wrote them are not delivered and not billed. A person is skipped when they commented and their comment contains any of these words or phrases, as whole words, ignoring case and accents ("felicitations" also matches "Félicitations !"). People who only reacted, and the post author, are never affected. Suggested list: ["félicitations", "bravo", "congrats", "congratulations", "well done", "bonne continuation", "bonne chance", "good luck"]. Optional, empty by default (no comment is excluded). On `PATCH`, send the full list; send `[]` to clear it.
    - `postedLimit` string: Time window (default "week" for reactions)
    - `minEngagement` integer: Minimum engagement count
    - `maxPosts` integer: Max posts to process (0 = unlimited)
    - `engagementTypes` string[]: Which people on each surfaced post become leads. Combine the values in this array: - "likes": people who reacted to the post. - "comments": people who commented on the post. - "poster": the post author. Use ["poster"] alone for an author-only signal (no engager fan-out — typically much less noise). - "both": intersection of likes AND comments (highest intent, smallest volume). Examples: ["likes", "comments"] = union (reacted OR commented); ["poster"] = author only; ["poster", "comments"] = author + commenters.
    - `companySizeFilters` string[]: Company size filter. Values: "Self-employed", "1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10000", "10001+". A company qualifies when its declared size band OR its employee count falls in a selected band; a count within 10% of a band edge counts for both neighbouring bands, and a company declaring 501+ employees is never placed in a smaller band by a low count. The delivered `employee_range` / `employee_count` are the pair the lead was judged on.
    - `targetPersonas` string[]: Filter by job-role persona (decision-maker targeting). Accepted values are the persona display names listed here; see GET /v1/personas for the full taxonomy with department, seniority and EN/FR job titles. Titles are matched by meaning, not as text: `targetPersonas` and `customPersonaTitles` form ONE list and a person qualifies by matching ANY entry. Each entry is read as a function plus a seniority level, in any language ("Directeur Commercial" satisfies "Sales Director", "Président" or "Directeur général" a CEO target), and a role at that level or above qualifies: a Director or Head target refuses a plain Manager; a founder running the company counts as CEO. A custom title carries the level its own words state; one with no level word accepts every level. Valid values: "Account Executive", "Account Manager", "Accountant", "Agency Director", "Business Analyst", "Business Developer", "Business Unit Director", "Buyer", "CEO", "CIO", "CSR Director", "CSR Manager", "CTO", "Communication Director", "Community Manager", "Content Manager", "Copywriter", "Creative Director", "Customer Success Director", "Customer Success Manager", "Customer Support Agent", "Cybersecurity Director", "Data Analyst", "Data Director", "Designer", "DevOps Engineer", "Digital Director", "Digital Project Manager", "Ecommerce Director", "Ecommerce Manager", "Engineering Manager", "Engineering Office Director", "Ergonomist", "Executive Assistant", "Finance Director", "Finance Manager", "GTM Director", "GTM Manager", "Growth Director", "Growth Manager", "HR Assistant", "HR Development", "HR Director", "Happiness Manager", "IT Project Manager", "Industrial Director", "Innovation Director", "Lab Manager", "Legal Counsel", "Legal Director", "Legal Manager", "Logistics Coordinator", "Logistics Director", "M&A Director", "Marketing Director", "Marketing Manager", "Office Manager", "Omnichannel Director", "Operations Director", "Operations Manager", "Payroll Manager", "Payroll Officer", "Procurement Specialist", "Product Director", "Product Manager", "Project Manager", "Purchasing Director", "Purchasing Manager", "Quality Health and Safety", "Quality Manager", "Quality Technician", "R&D Director", "R&D Engineer", "R&D Manager", "Recruitment Manager", "Research Director", "Research Scientist", "SDR / BDR", "Sales Director", "Sales Manager", "Social Media Director", "Social Media Manager", "Software Engineer", "Supply Chain Director", "Support Director", "Support Manager", "Talent Acquisition", "Technical Director", "Training Director", "Training Officer", "Transformation Director", "UX Designer", "Warehouse Director", "Web Developer"
    - `locationFilter` string: Filter by location (e.g. 'France', 'Paris')
    - `locations` string[]: Target locations (e.g. ['France', 'Paris']). Applies to the PERSON's LinkedIn profile location, not the company's headquarters: a person in Paris working for a company headquartered abroad matches France. One matching entry is enough. Only fundraising and M&A signals filter on headquarters (`hqLocations`).
    - `excludedLocations` string[]: Locations to exclude from results
    - `industryFilters` string[]: Only return companies in these LinkedIn industries. Two kinds of value work: a single industry (e.g. 'Software Development') or a broad category that covers many (e.g. 'Technology and Media'). Matching is exact, so a near-miss like 'Software development' matches nothing and the signal quietly produces no leads. Empty = all industries. Call GET /api/v1/signals/industries for the valid list.
    - `companyTypeFilters` string[]: Only return companies of these legal/ownership types. Valid values: 'Privately Held', 'Public Company', 'Nonprofit', 'Educational Institution', 'Partnership', 'Sole Proprietorship', 'Government Agency', 'Self-Employed'. Empty = all types. A company whose type is unknown is KEPT, not dropped, so this narrows results only where the type is known.
    - `excludedIndustryFilters` string[]: LinkedIn industries to exclude. Same vocabulary as `industryFilters` (single industry or category name); an unrecognised value excludes nothing. Call GET /api/v1/signals/industries for the valid list.
    - `excludedCompanyUrls` string[]: LinkedIn company URLs to exclude from results
    - `excludedCompanySizeFilters` string[]: Company sizes to exclude from results
    - `customPersonaTitles` string[]: Custom free-text job titles to match in addition to predefined personas. Titles are matched by meaning, not as text: `targetPersonas` and `customPersonaTitles` form ONE list and a person qualifies by matching ANY entry. Each entry is read as a function plus a seniority level, in any language ("Directeur Commercial" satisfies "Sales Director", "Président" or "Directeur général" a CEO target), and a role at that level or above qualifies: a Director or Head target refuses a plain Manager; a founder running the company counts as CEO. A custom title carries the level its own words state; one with no level word accepts every level.
    - `excludedTitles` string[]: Job titles to exclude. Matched as whole words, case- and accent-insensitive: "intern" excludes "Intern" and "Interns", never "International"; a phrase matches the same words in the same order; end a word with * to match a prefix ("infirmi*" excludes "Infirmière").
    - `getEmails` boolean: Enable email enrichment (0.5 credit/lead, charged only on success)
    - `getPhones` boolean: Enable phone enrichment (5 credits/lead, charged only on success)
    - `getSireneData` boolean: Enrich with French SIRENE registry data (1 credit/lead, charged only on success)
    - `detectTechnologies` boolean: Detect technologies used on the company's public website (1 credit/lead, charged only on success)
    - `getHomepageContent` boolean: Fetch the company's homepage content (1 credit/lead, charged only on success)
    - `postUrls` string[]: LinkedIn post URLs to track reactions on (required for activation). Short links (https://lnkd.in/…) are accepted and stored as the full post URL they point to; the query string (tracking parameters) is dropped.
  - `dailyLeadLimit` integer: Max leads per day
  - `duplicateHandling` string, 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.
  - `status` string, nullable: Initial status (default: draft). Accepts draft, active, or paused. If active, mandatory config fields are validated.

## Response `201`

Signal created

- object: A single signal: create, GET /signals/{id} and PATCH. It carries two fields the list does not. A customer reads their stored `config` back and assumes it is the one in force; on `job_changes` three fields were not (`maxJobAgeDays` 90 stored / 180 applied, `publishedDate` stored and never read, `allowUnknownCompanySize` true and applied false), with nothing anywhere saying so.
  - `id` string, required
  - `name` string, required
  - `status` string, required
  - `signalTypeId` string, required
  - `webhookUrl` string, nullable
  - `config` object, nullable: Signal-specific configuration
  - `dailyLeadLimit` integer, required
  - `leadsToday` integer, required
  - `leadsTotal` integer, required
  - `duplicateHandling` string, required: Duplicate lead handling: 'refuse' (never accept), 'allow' (always accept), or 'Xd' (accept after X days)
  - `createdAt` string, required
  - `updatedAt` string, required
  - `lastLeadAt` string, nullable
  - `applied` object: 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.
  - `warnings` SignalConfigWarning[]: What you should know about this configuration: values applied differently from what is stored, and filter values that are probably not what you meant. Computed from the stored configuration, so they appear on GET as well as on create and update - a signal created before these fields existed reports them too. Never an error: the signal is created or updated regardless.
    - `code` string, required: Stable identifier. `VALUE_BELOW_MINIMUM` (a value under the documented minimum is applied as the minimum), `VALUE_ADJUSTED` (a value the search cannot use as written is applied as the nearest one it can, e.g. a `publishedDate` of 14d searches 15 days), `FIELD_NOT_USED` (a stored field this signal ignores), `UNKNOWN_SIZE_NOT_ACCEPTED`, `CATEGORY_WITH_OWN_INDUSTRIES` (a category listed together with industries it already covers), `UNKNOWN_INDUSTRY` (a value matching no published industry), `UNKNOWN_FIELD` (a config key this signal does not have), `UNKNOWN_TOOL` / `UNKNOWN_CATEGORY` (a tracked tool or category name that is not in the catalog of GET /api/v1/signals/technographic-tools; on a GMB Discovery signal, a `category` that is not a Google Maps category, so the signal matches no business), `UNKNOWN_CITY` (GMB Discovery: cities in `cities` that are not in the signal's `country` — `values` lists them; when none is, the signal matches no business until `cities` or `country` is changed; never an error, nothing stored is changed), `NO_FOLLOWER_SOURCE` (a Company Followers signal with no follower extraction set up yet, so it produces nothing), `DAILY_LIMIT_PENDING` (a job signal's `dailyLeadLimit` changed less than a day after its search was last rebuilt: the search keeps its previous volume until the time in `values`, while the leads delivered per day already follow the new limit), `WATCHED_LIST_EMPTY` (a watchlist reading its list from your CRM holds no company or person — the CRM is not connected, the list could not be read, or it is empty — so it produces nothing until the list fills; cleared on its own once it does), `QUOTE_REQUIRED` (an `active` Company Followers signal in `icp` mode whose follower extraction has not been priced and accepted, so it produces nothing yet: `values[0]` says why — `not_requested`, `awaiting_acceptance` (then `values[1]` is the quoted price in credits), `expired`, `declined`, `failed`, or, after an automatic quote, `auto_quote_refused` / `auto_accept_refused` (then `values[1]` is the error code); the message names the call to make — see POST /api/v1/signals/{signal_id}/extraction/quote; cleared once a quote is accepted), `WATCHED_LIST_IMPORTING` (a company watchlist whose HubSpot list is still being read: companies are added as they arrive; `values[0]` is the number of members read so far, `values[1]` the list id; cleared once the whole list is read), `MATCHING_CONFIRMATION_REQUIRED` (a New Decision Maker or Account watchlist whose companies must be matched to their LinkedIn company page before they can be watched, at a cost above the amount we match without asking: nothing is matched or charged until you confirm with POST /api/v1/watchlists/{signalId}/companies/confirm-matching; `values[0]` is the maximum cost, `values[1]` the number of companies to match; cleared once confirmed), `DESTINATION_UNAVAILABLE` (the outreach campaign this signal sends leads to cannot receive them — not found, archived, ended or without any step — so leads are not reaching it: `values[0]` is `campaign_not_found`, `campaign_archived`, `campaign_ended` or `campaign_no_steps`; cleared once a lead reaches the campaign or the signal's destination is changed), `DESTINATION_NEEDS_CONTACT` (the signal delivers companies with no contact and a destination in `destinations` only accepts people, so none of its leads reach that destination), `DESTINATION_SKIPS_COMPANY_ONLY` (some leads are companies with no contact, e.g. no one matching your personas was found, and a destination only accepts people), `DESTINATION_NEEDS_EMAIL` (a destination only accepts leads with an email and `getEmails` is off) — for these three, `values[0]` is the destination key in `destinations`, the next values are the fixes: `add_persona` (turn on `enablePersonaTargeting` with `targetPersonas`), `require_contact` (turn on `requireContact`), `add_company_destination` (add a destination that accepts companies: `hubspot`, `pipedrive`, `googleSheets` or `customWebhook`), `enable_email_finding` (turn on `getEmails`); severity `warning` when those leads reach no destination at all, `info` when another destination still receives them; never blocks the save; `COMPANY_PAGE_UNAVAILABLE` (a Company Followers signal whose extraction stopped because a page in `linkedinCompanyUrls` does not exist on LinkedIn: nothing was extracted or charged; `values` lists the pages; replace them with PATCH /api/v1/signals/{signal_id}, then start the extraction again; cleared once the pages are replaced or a new extraction runs), `COMPANY_PAGE_UNVERIFIED` (create / PATCH responses only: a page in `linkedinCompanyUrls` could not be verified at that moment and was accepted; `values` lists them — if one does not exist, its extraction stops without using credits and the signal carries `COMPANY_PAGE_UNAVAILABLE`).
    - `severity` string, required: `info`: nothing to do. `warning`: probably not what you meant.
    - `field` string, required: The `config` key concerned, camelCase (or `dailyLeadLimit`).
    - `message` string, required
    - `values` string[]: The offending values, when there are some.

## Other responses

- `400`: Invalid request: missing required config (Post URLs), or an unrecognized location
- `401`: Missing or invalid API key
- `402`: Account has no credits
- `422`: Validation Error
- `429`: Rate limit exceeded. Retry after the number of seconds in the `Retry-After` response header.

---

[API](https://skmtc.dev/rodz/apis/rodz-api.md) · [All operations](https://skmtc.dev/rodz/apis/rodz-api/llms.txt) · [OpenAPI document](https://skmtc.dev/rodz/apis/rodz-api/revisions/3003505ff896?raw)