Quickstart
Mint a key
In Sliq, open Settings → MCP and API and create an API key. It is shown once.
Call an endpoint
Send the key as a bearer token to https://api.getsliq.com/v1/people.
Authentication
Every request carries a bearer key in the Authorization header. Mint one under
Settings → MCP and API — the plaintext key is shown once and stored only as a hash, so copy it then.
Each key returns strictly your own data; a key for another workspace's row is indistinguishable from a missing one.
Authorization: Bearer sk_live_YOUR_KEY
Endpoints
Four read-only GET endpoints. Full parameters and response schemas live in the interactive spec.
/v1/people
Your prospect book — filterable and cursor-paginated.
/v1/people/{person_id}
A single prospect by id.
/v1/people/{person_id}/interactions
One person’s LinkedIn + email message and connection timeline.
/v1/agents
Your agents (campaigns), to resolve a prospect’s agent_id to a name.
Filter /v1/people with
updated_since,
stage,
agent_id,
is_connected,
has_replied, and
search. Page with
page_size and
cursor; the envelope carries next_url and has_more.
Example requests
curl https://api.getsliq.com/v1/people \ -H "Authorization: Bearer sk_live_YOUR_KEY"
{
"data": [
{
"id": 884213,
"name": "Priya Raman",
"title": "Director of Process Engineering",
"company": "Kalvex Biologics",
"email": null,
"linkedin_url": "https://www.linkedin.com/in/priya-raman-8a41",
"channel": "linkedin",
"agent_id": 612,
"stage": "replied",
"is_connected": true,
"created_at": "2026-06-19T11:04:22Z",
"updated_at": "2026-07-28T14:02:11Z"
}
],
"next_url": null,
"has_more": false
}
curl "https://api.getsliq.com/v1/people?has_replied=true" \ -H "Authorization: Bearer sk_live_YOUR_KEY"
curl https://api.getsliq.com/v1/people/884213/interactions \ -H "Authorization: Bearer sk_live_YOUR_KEY"
The interactive spec is canonical
Swagger UI and the OpenAPI document are generated from the live endpoints, so they are always exact. Give a coding agent the OpenAPI URL and a key, and it can integrate itself.
Prefer to connect Claude or ChatGPT directly? Use the Sliq MCP server instead.
Frequently asked questions
Does Sliq have an API?
Yes. Sliq has a read-only REST API at https://api.getsliq.com. It lets you pull your prospects and their LinkedIn and email interaction history out of Sliq — for syncing into a CRM or reading from a coding agent. Authenticate with a bearer key you mint in Settings; every key is scoped to your own data.
How do I authenticate with the Sliq API?
Every request carries an "Authorization: Bearer <key>" header. Mint a key inside Sliq under Settings → MCP and API — it is shown once, so copy it then. Keys are per-user and only ever return your own data.
What endpoints does the Sliq API have?
Four read-only GET endpoints: /v1/people (your prospect book), /v1/people/{id} (one prospect), /v1/people/{id}/interactions (a person's cross-channel message and connection timeline), and /v1/agents (your campaigns, for resolving a prospect's agent_id to a name). The full interactive spec is at https://api.getsliq.com/v1/docs.
Is there an OpenAPI spec for the Sliq API?
Yes. The machine-readable OpenAPI spec is at https://api.getsliq.com/v1/openapi.json and interactive Swagger docs are at https://api.getsliq.com/v1/docs. Both are generated from the API itself, so they never drift from the live endpoints — point a coding agent straight at the OpenAPI URL.
Can I use the Sliq API from a coding agent like Claude Code?
Yes — that is what it is built for. Give your agent the OpenAPI URL (https://api.getsliq.com/v1/openapi.json) and a bearer key, and it can read your prospects and replies each run. If you would rather connect Claude or ChatGPT directly, Sliq also has an MCP server.
Can the Sliq API send messages or change my data?
No. v1 is read-only: it reads prospects and interaction history and never writes, sends, or enrolls anyone. Sending stays behind Sliq’s approval queue, where you approve every message.
Delegate every GTM task to AI agents
Everything you know you should do, but don't have time for.