POST
/
v1
/
signals
# Monitor for job postings
curl -X POST https://api.pipeium.com/v1/signals \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "list_id": "list_123",
    "level": "account",
    "signal": "open_job_post",
    "metadata": {
      "title": "Sales Engineer"
    },
    "notify_mode": "on_change",
    "monitor_frequency": 7
  }'

# Monitor for funding news with value notification
curl -X POST https://api.pipeium.com/v1/signals \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "list_id": "list_123",
    "level": "account",
    "signal": "news",
    "metadata": {
      "article": "funding_round"
    },
    "notify_mode": "on_value",
    "notify_value": "Series B",
    "monitor_frequency": 14
  }'

{
  "id": "sig_123",
  "detail": "Signal created"
}

​
Request Body

​
list_id
string
required

The ID of the list to monitor

​
level
string
required

The level of signal to monitor. Must be either “contact” or “account”

​
signal
string
required

The type of signal to monitor. Available options depend on the level:

​
Contact Level Signals

  • “current_role”
  • “deep_research”

​
Account Level Signals

  • “news”
  • “open_job_post”
  • “deep_research”
​
metadata
object

Additional data required for specific signal types:

​
For deep_research

{
  query: string,    // Search query
  extract: string   // Data to extract
}

​
For news

{
  article: "funding_round" | "acquisition" | "new_product" | "leadership_change"
}

​
For open_job_post

{
  title: string
}
​
notify_mode
string
required

How to trigger notifications. Must be either:

  • “on_change”: Notify whenever the signal value changes
  • “on_value”: Notify when a specific value is found
​
notify_value
string

Required when notify_mode is “on_value”. The specific value to trigger notifications for.

​
monitor_frequency
number
required

How often to check for this signal (in days). Must be between 4 and 30 days.

​
Response

​
id
string

The ID of the created signal

​
detail
string

Success message confirming the signal was created

# Monitor for job postings
curl -X POST https://api.pipeium.com/v1/signals \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "list_id": "list_123",
    "level": "account",
    "signal": "open_job_post",
    "metadata": {
      "title": "Sales Engineer"
    },
    "notify_mode": "on_change",
    "monitor_frequency": 7
  }'

# Monitor for funding news with value notification
curl -X POST https://api.pipeium.com/v1/signals \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "list_id": "list_123",
    "level": "account",
    "signal": "news",
    "metadata": {
      "article": "funding_round"
    },
    "notify_mode": "on_value",
    "notify_value": "Series B",
    "monitor_frequency": 14
  }'

{
  "id": "sig_123",
  "detail": "Signal created"
}

​
Delete Signal

To delete a signal, send a DELETE request:

DELETE /v1/signals/{signalId}

​
Response

{
  "detail": "Signal deleted"
}