How do you create a Rodz signal and route it to lemlist, entirely through the API?

Before you start

• A Rodz API key (Integrations → API in the dashboard), exported as RODZ_API_KEY.
• A lemlist API key and a lemlist campaign with at least one step.
• curl and, to read responses more easily, jq.

Steps

1. Step 1. Pick the signal type and its allowed values

   GET /api/v1/signal-types is the entry point: each type gives its createEndpoint, configParameters, pricingModel and outputFields. For job changes, roles come from GET /api/v1/personas (the name field) and industries from GET /api/v1/signals/industries (copy them verbatim: matching is exact).

   Catalog, personas and industries

   curl -s "https://api.rodz.io/api/v1/signal-types" -H "Authorization: Bearer $RODZ_API_KEY" \
     | jq '.signalTypes[] | {signalTypeId, createEndpoint, creditsPerLead}'
   curl -s "https://api.rodz.io/api/v1/personas" -H "Authorization: Bearer $RODZ_API_KEY"
   curl -s -G "https://api.rodz.io/api/v1/signals/industries" -H "Authorization: Bearer $RODZ_API_KEY" \
     --data-urlencode "search=software"

2. Step 2. Create the signal as a draft

   Send name, config, dailyLeadLimit and duplicateHandling. Without status, the signal is created as draft. Turn on getEmails: an email sequence needs the address.

   The 201 response returns the signal with two fields to read: applied (the settings actually in force where they differ from config) and warnings (filter values that are probably not what you meant). They are never errors: the signal is created regardless.

   POST /api/v1/signals/job-changes

   curl -s -X POST "https://api.rodz.io/api/v1/signals/job-changes" \
     -H "Authorization: Bearer $RODZ_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "name": "New sales directors, SaaS, France",
       "dailyLeadLimit": 30,
       "duplicateHandling": "refuse",
       "config": {
         "jobTitles": ["Sales Director"],
         "customTitles": ["Head of Revenue"],
         "companySizeFilters": ["51-200", "201-500"],
         "industryFilters": ["Software Development"],
         "locations": ["France"],
         "getEmails": true
       }
     }' | tee signal.json
   export SIGNAL_ID=$(jq -r .id signal.json)

3. Step 3. Connect lemlist

   PUT /api/v1/integrations/lemlist saves your lemlist key; it is validated before it is stored, then encrypted. GET /api/v1/integrations then shows connected: true. HubSpot, Pipedrive and Google Sheets connect once through OAuth in the dashboard (the API answers 400 USE_DASHBOARD_OAUTH).

   PUT /api/v1/integrations/lemlist

   curl -s -X PUT "https://api.rodz.io/api/v1/integrations/lemlist" \
     -H "Authorization: Bearer $RODZ_API_KEY" \
     -H "Content-Type: application/json" \
     -d "{\"apiKey\": \"$LEMLIST_API_KEY\", \"label\": \"Sales team\"}"

4. Step 4. Get the campaign id

   GET /api/v1/integrations/lemlist/campaigns returns items[] with id, name and status. The id is the campaignId of the next step. A 409 means lemlist is not connected.

   GET /api/v1/integrations/lemlist/campaigns

   curl -s "https://api.rodz.io/api/v1/integrations/lemlist/campaigns" \
     -H "Authorization: Bearer $RODZ_API_KEY" | jq '.items[] | {id, name, status}'

5. Step 5. Route the signal to the campaign, then activate it

   A PATCH with destinations.lemlist.campaignId plugs the signal into the campaign. If several lemlist accounts are connected, add integrationId. A second PATCH sets the signal to active: from then on, every lead delivered is charged and pushed into the campaign.

   PATCH /api/v1/signals/{signal_id}

   curl -s -X PATCH "https://api.rodz.io/api/v1/signals/$SIGNAL_ID" \
     -H "Authorization: Bearer $RODZ_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"destinations": {"lemlist": {"campaignId": "cam_aBc123XyZ"}}}'
   
   curl -s -X PATCH "https://api.rodz.io/api/v1/signals/$SIGNAL_ID" \
     -H "Authorization: Bearer $RODZ_API_KEY" \
     -H "Content-Type: application/json" \
     -d '{"status": "active"}'

Example payload

`201 Created` response of `POST /api/v1/signals/job-changes` (fictitious data). An empty `applied` means everything runs as stored.

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "name": "New sales directors, SaaS, France",
  "status": "draft",
  "signalTypeId": "job_changes",
  "webhookUrl": null,
  "config": {
    "jobTitles": ["Sales Director"],
    "customTitles": ["Head of Revenue"],
    "companySizeFilters": ["51-200", "201-500"],
    "industryFilters": ["Software Development"],
    "locations": ["France"],
    "getEmails": true
  },
  "dailyLeadLimit": 30,
  "leadsToday": 0,
  "leadsTotal": 0,
  "duplicateHandling": "refuse",
  "createdAt": "2026-10-12T08:00:00Z",
  "updatedAt": "2026-10-12T08:00:00Z",
  "lastLeadAt": null,
  "applied": {},
  "warnings": []
}

Frequently asked questions

Sources

• Rodz API reference: Create Job Changes signal, Update signal, Integrations
• Rodz API OpenAPI specification

Related guides

• API recipe How do you pull a Rodz signal’s leads through the API, without a webhook?
• API recipe How do you receive Rodz leads by webhook and verify their HMAC signature?
• Recipe How do you start a lemlist sequence when a prospect changes jobs?
• About this signal Job changes