API

Direct-client API reference for accessing Sillage workspace content and account mapping data.

The API lets client applications read content, content requests, top accounts, and account mapping state from a Sillage workspace.

Most API endpoints are direct-client endpoints using workspace API keys generated from Sillage settings. Account Mapping also supports partner endpoints with partner master keys.

Base URL

https://api.getsillage.com

OpenAPI Specification — Swagger UI · Raw JSON spec

Authentication

For direct-client endpoints, send your Sillage workspace API key as a bearer token:

Authorization: Bearer <YOUR_API_KEY>

Direct-client keys start with sk_live_. Partner master keys start with mk_live_ and are only used for partner routes.

See Authentication for key handling and error behavior.

References

POSTContents/api/v2/contents/query GETContent/api/v2/contents/{id}GETContent Requests/api/v2/content-requests GETContent Request/api/v2/content-requests/{id}GETCompany Mappings/api/v2/company-mappings GETCompany Mapping/api/v2/company-mappings/{mapping_id}POSTEnrich Company Mapping/api/v2/enrich-company-mapping PUTPersona/api/v2/persona POSTAdd Accounts/api/v2/top-account-list/accounts GETList Accounts/api/v2/top-account-list/accounts GETAccount Mapping Stage/api/v2/account-mapping/{id}/stage

Identifiers

All public /v2 identifiers are integer ids.

Dates

Date filters use ISO 8601 timestamps. Responses return timestamps in UTC.

2026-06-12T10:30:00.000Z

Pagination

List endpoints use offset/page pagination with page and page_size query parameters. See Pagination.

Errors and response headers

v2 endpoints return RFC 9457 problem documents, and every response carries request-tracing and rate-limit headers — see Authentication for the full error model, status codes, and header reference.

API