Create Job Changes signal

Track when the decision-makers you care about change jobs — get notified when someone matching your target personas starts a new position at a company in your ICP, and receive their enriched profile at your webhookUrl.

Input: name, webhookUrl, and a config object with: jobTitles (preset personas from GET /api/v1/personas, e.g. "CTO", "Sales Director"), customTitles (your own titles), excludedTitles, companySizeFilters / excludedCompanySizeFilters, locations / excludedLocations, industryFilters / excludedIndustryFilters (values from GET /api/v1/signals/industries), companyTypeFilters, excludedCompanyUrls, maxJobAgeDays (how recent the new position must be; minimum and default 180 days), and optional enrichments (getEmails, getPhones, getSireneData, detectTechnologies, getHomepageContent). Top-level dailyLeadLimit (1–999,999) and status (draft/active/paused, default draft) complete the request.

How the filters are applied — read this before sizing a list:

• Titles are matched by meaning, not as text. jobTitles and customTitles form ONE list; a person qualifies by matching ANY entry. Each entry is read as a function plus a seniority level, in any language ("Directeur Commercial" satisfies a "Sales Director" target), and a role at that level OR ABOVE qualifies: a Director target accepts VPs and heads of the function and refuses a plain Manager; a Manager target also accepts Directors. A custom title carries the level its own words state; one with no level word accepts every level. excludedTitles is applied first and matches whole words, case- and accent-insensitive ("intern" removes "Intern" and "Interns", never "International"; end a word with * to match a prefix).
• Company size is judged on the NEW employer: its declared band OR its employee count must fall in companySizeFilters (a count within 10% of a band edge counts for both bands; a company declaring 501+ employees is never placed in a smaller band by a low count). Exclusions are strict on either value. A company whose size cannot be determined is delivered only when your selection includes a band under 51 employees.
• Location is the PERSON's profile location, not the company's headquarters. One matching entry in locations is enough; a profile with no location is dropped when locations is set; a profile that states only a country does not match a city or region entry. locationFilter is not used — send locations.
• Industry is an exact-name match on the new employer's industry, except that a CATEGORY name accepts every industry inside it — and ten names ("Manufacturing", "Retail", "Wholesale", …) are both an industry and a category and are applied as the category. GET /api/v1/signals/industries gives each category's real industryCount and ?category= lists its members. A value outside that list matches nothing.
• Recency: a position is delivered up to maxJobAgeDays days after its start date, never less than 180; a smaller value is applied as 180.

Output: 201 Created returns the signal, its stored config, applied (the settings in force where they differ from config) and warnings (filter values that are probably not what you meant — a category sent with its own industries, an unknown industry). Each person matching your personas and filters who recently started a new job is pushed to your webhookUrl as a JSON lead payload (WebhookPersonLeadPayload): a signal object (id, name, type, human-readable label, detection date, plus the move itself — previous_title, previous_company, previous_company_linkedin_url, previous_job_started_on, previous_job_ended_on, new_title, new_company, new_job_started_on ("MM/YYYY"), new_job_start_month (the same month as "YYYY-MM", sortable) and change_type: company, title or both. Test the freshness of a change against new_job_started_on / new_job_start_month — previous_job_ended_on is a different date whenever there was a gap between the two jobs. These ten signal keys are a stable contract: present on every job-change lead, never renamed or null, "" when a value is unknown — safe to map straight into your CRM), a contact object (first/last name, title, location, LinkedIn and Sales Navigator profile URLs, matched persona, and email/phone when enrichment is enabled), and a company object (name, website, LinkedIn URL — plus detected tech stack and homepage title/description when those enrichments are on). Fields that aren't available are returned as empty strings.

Use cases:

• New-buyer outreach — reach decision-makers in their first 90 days, when they re-evaluate tools and vendors.
• Champion tracking — follow past champions to their new company for a warm re-intro.
• Territory alerts — notify the owning rep when a target persona lands at an account.