API v3 is live and in beta: expect possible malfunctions and breaking changes in the coming days. If you find a bug, please report it to your Sillage contact.
v2Deprecated

Lists

Reusable lists of companies or people that signal agents watch.

A list is a reusable, named collection of canonical companies or people that you bind to a signal agent. The agent then surfaces interactions involving the list's members. Lists are workspace-scoped and exist independently of any agent — one list can be bound to several agents over time.

This replaces the deprecated /watchlists endpoints, which keep answering but no longer receive updates. name is what those endpoints call title, and member_count is what they call entity_count.

Kind is derived from type

Every list has an immutable type, set at creation. The type determines the list kind (company vs people) — you never declare the kind yourself:

typekindmembers
competitorcompanycompanies
partnercompanycompanies
customercompanycompanies
prospectcompanycompanies
influencerprofilepeople
championprofilepeople

type cannot be changed after creation (it would move the list across kinds). name, description and default_tracking_status are editable.

customer and prospect lists additionally carry a tier (an integer, or null). It has no effect on how the list behaves — it is recorded and returned only.

Authentication

Authorization: Bearer $SILLAGE_API_KEY

Endpoints

Single-list endpoints are keyed by a compound /:kind/:list_id path, where kind is company or profile and matches the list's immutable type. The company and profile collections have independent id sequences, so the kind disambiguates which one a list_id refers to (no cross-kind id collision). The collection endpoints take no kind.

  • Create list: POST /api/v2/partner/workspaces/:partner_workspace_id/lists
  • List lists: GET /api/v2/partner/workspaces/:partner_workspace_id/lists
  • Get list: GET /api/v2/partner/workspaces/:partner_workspace_id/lists/:kind/:list_id
  • Update list: PUT /api/v2/partner/workspaces/:partner_workspace_id/lists/:kind/:list_id
  • Delete list: DELETE /api/v2/partner/workspaces/:partner_workspace_id/lists/:kind/:list_id
  • List members: GET /api/v2/partner/workspaces/:partner_workspace_id/lists/:kind/:list_id/members
  • Add members: POST /api/v2/partner/workspaces/:partner_workspace_id/lists/:kind/:list_id/members
  • Remove member: DELETE /api/v2/partner/workspaces/:partner_workspace_id/lists/:kind/:list_id/members/:member_id

Binding to an agent

Bind a list to an agent with the watchlist_kind and watchlist_id fields together on Create agent or Update agent — pass this list's kind and id, the field names have not changed. An agent watches at most one list; pass both watchlist_kind: null and watchlist_id: null on update to unbind.

On this page