Provider API
Partner integration reference for managing workspaces via the Sillage provider API.
The Provider API lets partner applications manage workspace data on behalf of their end-users. All provider endpoints authenticate with a partner master key — the key alone identifies the partner, no slug is needed in any URL.
Base URL
https://api.getsillage.comOpenAPI Specification — Swagger UI · Raw JSON spec
Authentication
Send your partner master key as a bearer token:
Authorization: Bearer $SILLAGE_API_KEYPartner master keys start with mk_live_. The key alone identifies the partner. No slug is required in any URL.
References
/api/v2/partner/workspaces/{partner_workspace_id}/company-mappings
GETCompany Mapping/api/v2/partner/workspaces/{partner_workspace_id}/company-mappings/{mapping_id}
POSTEnrich Company Mapping/api/v2/partner/workspaces/{partner_workspace_id}/enrich-company-mapping
POSTAdd Accounts/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list/accounts
GETGet Status/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list/status
GETList Accounts/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list/accounts
GETList Not-Found Accounts/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list/accounts/not-found
GETGet Top Account List/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list
GETCount Accounts/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list/count
POSTRemove Accounts/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list/accounts/remove
DELETERemove Account By Id/api/v2/partner/workspaces/{partner_workspace_id}/top-account-list/accounts/{id}
POSTSignals/api/v2/partner/workspaces/{partner_workspace_id}/signals/query
POSTSignal Runs/api/v2/partner/workspaces/{partner_workspace_id}/signal-runs
GETAgents/api/v2/partner/workspaces/{partner_workspace_id}/agentsPOSTCreate Watchlist/api/v2/partner/workspaces/{partner_workspace_id}/watchlists
GETList Watchlists/api/v2/partner/workspaces/{partner_workspace_id}/watchlists
GETGet Watchlist/api/v2/partner/workspaces/{partner_workspace_id}/watchlists/{kind}/{watchlist_id}
PUTUpdate Watchlist/api/v2/partner/workspaces/{partner_workspace_id}/watchlists/{kind}/{watchlist_id}
DELETEDelete Watchlist/api/v2/partner/workspaces/{partner_workspace_id}/watchlists/{kind}/{watchlist_id}
POSTAdd Entities/api/v2/partner/workspaces/{partner_workspace_id}/watchlists/{kind}/{watchlist_id}/entities
GETList Entities/api/v2/partner/workspaces/{partner_workspace_id}/watchlists/{kind}/{watchlist_id}/entities
DELETERemove Entity/api/v2/partner/workspaces/{partner_workspace_id}/watchlists/{kind}/{watchlist_id}/entities/{entity_id}
GETContents/api/v2/partner/workspaces/{partner_workspace_id}/contentsGETContent Requests/api/v2/partner/workspaces/{partner_workspace_id}/content-requests
POSTLeads/api/v2/partner/workspaces/{partner_workspace_id}/leads/query
Identifiers
By default, /v2 identifiers are numeric integer ids. They are specific to your environment and are not portable across environments. Two exceptions: partner_workspace_id, present in every partner URL, is an opaque string that you chose when you created the workspace, not a Sillage-issued numeric id. And on the top account list, tal_id, company_id, and the not-found id are also opaque strings, not numeric ids.
Dates
Date filters use ISO 8601 timestamps. Responses return timestamps in UTC.
2026-06-12T10:30:00.000ZError model
v2 endpoints return errors as RFC 9457 problem documents with Content-Type: application/problem+json.
{
"type": "https://docs.getsillage.com/errors/forbidden",
"title": "Forbidden",
"status": 403,
"detail": "Account Mapping is not enabled for this workspace.",
"instance": "/api/v2/partner/workspaces/ws_123/company-mappings"
}Common response headers
Every response includes:
| Header | Description |
|---|---|
| X-Request-Id | Request UUID for debugging and support. |
| X-Response-Time | Server response time. |