Update pipeline configuration

Enables monitoring for a company, changes its monitoring level, or turns monitoring off, all through the same call. Calling this endpoint again for the same company and pipeline updates the existing configuration instead of creating a duplicate, so it is safe to call whenever you want to change the monitoring level.

Route

Path parameters

Request body

What each configuration value means for this company:

• account_mapping: we keep the account's team map up to date, no content monitoring.
• account_mapping_and_content: full monitoring, team map plus posts, comments, and job-postings signals.
• disabled: turns off account mapping and content monitoring for this company. Existing data is kept. Setting configuration back to account_mapping or account_mapping_and_content re-enables monitoring.

Example request

curl -X PATCH "https://api.getsillage.com/api/v2/companies/456/pipeline-configs" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "pipeline_type": "account_mapping_and_content",
    "configuration": "account_mapping"
  }'

Success response

Status: 200 OK

{
  "data": {
    "pipeline_type": "account_mapping_and_content",
    "configuration": "account_mapping"
  }
}

Example: disable monitoring

To turn monitoring off for a company, send configuration: "disabled". Account mapping and content monitoring both stop; the company's existing data is kept, and the same call with a different configuration value re-enables monitoring later.

curl -X PATCH "https://api.getsillage.com/api/v2/companies/456/pipeline-configs" \
  -H "Authorization: Bearer $SILLAGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "pipeline_type": "account_mapping_and_content",
    "configuration": "disabled"
  }'

Response, status 200 OK:

{
  "data": {
    "pipeline_type": "account_mapping_and_content",
    "configuration": "disabled"
  }
}

Response fields

Errors

Error responses use RFC 9457 problem documents with Content-Type: application/problem+json:

{
  "type": "https://docs.getsillage.com/errors/invalid-query",
  "title": "Invalid request body",
  "status": 400,
  "instance": "/api/v2/companies/456/pipeline-configs",
  "errors": {
    "pipeline_type": ["Invalid literal value, expected \"account_mapping_and_content\""]
  }
}