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.
API

API

The Sillage API for client applications.

The API lets your application read and manage the signals, lists, leads, companies, content and credits of your Sillage workspace.

Base URL

https://api.getsillage.com

OpenAPI specification: Swagger UI · Raw JSON spec. See also OpenAPI specification.

Authentication

Send your Sillage workspace API key as a bearer token:

Authorization: Bearer <YOUR_API_KEY>

Workspace keys start with sk_live_. You generate them in your Sillage settings. See Authentication for the error model and the response headers.

References

Every endpoint of the API, by family.

Signal templates

The signals you can set up.

Signal setups

The signals your workspace runs.

Signals

The signals detected, searched and counted.

Signal runs

Start a signal and follow it.

Request status

Everything that is running now.

Lists

Lists of companies or people that signals watch.

Account monitoring

Choose which accounts are monitored.

Leads

The people your signals found.

Companies

The companies of your workspace.

Account mapping

The people mapped on each account.

Personas

The profiles of the people you target.

Setup state

What is still missing to get started.

Contents

The content collected for key accounts.

Content requests

The requests that gather content and map accounts.

Credits

Your credit balance.

Usage

What your credits were spent on.

How the routes are named

  • GET reads one item by its ID, or a plain list with few filters.
  • POST .../query searches with filters that take lists of values, such as several domains or several types. The filters travel in a JSON body.
  • POST .../count counts what a search would match.
  • PATCH, PUT and DELETE change or remove an item.

A route that takes a body (POST, PATCH or PUT) needs a JSON body, even when every field is optional: send {}. A missing or empty body is refused with 422 and the code body_required. The restore routes take no body.

Identifiers

All identifiers are integers.

Dates

Date filters take an ISO 8601 date and time with a UTC offset, for example 2026-06-12T10:30:00Z. Responses return dates in UTC.

Lists in query strings and bodies

A query parameter that takes a list accepts a comma list (?company_ids=1,2) or the key repeated (?company_ids=1&company_ids=2); repeating a parameter that takes one value is refused with 422. A body sent with GET or DELETE is ignored.

Pagination

Searches and credit usage page by cursor, plain lists page by page number. See Pagination.

Errors

Every error is an RFC 9457 problem document with a stable code, and input the API does not know is refused with 422. See Authentication.

On this page