Connect

API & webhooks

Quincer is API-first. Everything you can do in the dashboard — take over a live chat, update a lead, read the activity log — you can do via REST. This page is the map. For request/response previews against your real workspace, open Developer APIs inside the dashboard.

Authentication

All API requests use a workspace developer key. Generate one under Dashboard → Developers → API Keys, choose scopes, and pass it as a Bearer token:

Authorization: Bearer cw_dev_<your-key>

Two kinds of credentials exist: widget keys (cw_live_) are embedded in the page script and only identify a widget to the public chat endpoint. Developer keys (cw_dev_) are scoped to an organization, carry explicit scopes like leads:read or conversations:takeover, and must stay server-side.

Base URL

https://chat.quincer.com

External agent (takeover) endpoints

Use these to let an outside AI (OpenClaw, a custom agent, or your own backend) take over a live conversation, reply as a human, and hand back to the Quincer AI. These are how the OpenClaw integration works under the hood.

Method	Path	Scope	Purpose
`GET`	`/api/v1/conversations/:id`	`conversations:read`	Fetch full transcript + metadata.
`POST`	`/api/v1/conversations/:id/takeover`	`conversations:takeover`	Claim a conversation — AI stops responding.
`POST`	`/api/v1/conversations/:id/reply`	`conversations:reply`	Post a human-agent message (auto-translated to visitor's language).
`POST`	`/api/v1/conversations/:id/handback`	`conversations:handback`	Release the takeover — AI resumes.

Leads & activities

Method	Path	Scope	Purpose
`GET`	`/api/v1/leads`	`leads:read`	List leads. Filters: `widgetId`, `stage`, `temperature`, `assignedTo`, `updatedSince`.
`GET`	`/api/v1/leads/:id`	`leads:read`	Full lead record (BANT, tags, assigned task history).
`PATCH`	`/api/v1/leads/:id`	`leads:write`	Update fields: stage, temperature, tags, score, assignment, contact info.
`GET`	`/api/v1/activities`	`tasks:read`	Agent task log. Filters: `leadId`, `status`, `type`, `updatedSince`.
`GET`	`/api/v1/activities/:id`	`tasks:read`	Full activity record with execution + result data.

Rate limits

Developer keys are rate-limited per key: 100 reads/min and 30 writes/min. Over the limit returns 429 with an error message indicating remaining requests.

Webhooks

Subscribe to events under Dashboard → Settings → Webhooks. Quincer signs every payload with HMAC-SHA256 using the secret you set. Requests include X-Quincer-Signature (sha256=...), X-Quincer-Event, and X-Quincer-Timestamp.

Events

Event	Fires when
`conversation.message_received`	Visitor sends any message. Payload includes `status` (`active` or `human_active`) so subscribers know whether an external agent is driving.
`lead.created`	A new lead record is captured.
`lead.updated`	Any lead field changes.
`lead.stage_changed`	Lead moves between pipeline stages (includes `previousStage`).
`task.created`	An agent task (follow-up, qualification, CRM sync, etc.) is scheduled.
`task.completed`	A task finishes successfully.
`email.sent`	A lead email goes out.
`email.draft_created`	An AI-drafted email is ready for review.

Verifying signatures

const signature = req.headers["x-quincer-signature"];
const expected = "sha256=" + crypto
  .createHmac("sha256", process.env.QUINCER_WEBHOOK_SECRET)
  .update(req.rawBody)
  .digest("hex");
if (signature !== expected) {
  return res.status(401).send("invalid signature");
}

OpenClaw integration

Quincer ships a first-class OpenClaw skill so any OpenClaw agent can take over Quincer conversations, query leads, and log activity. Setup takes about a minute:

In Quincer, open Dashboard → Integrations → OpenClaw and click Connect OpenClaw. This creates a dedicated "OpenClaw" team member in your workspace and issues an API token bound to it.
Download SKILL.md and drop it in ~/.openclaw/workspace/skills/quincer/.
Add the token to ~/.openclaw/openclaw.json under skills.entries.quincer.env.QUINCER_API_KEY.
Restart the OpenClaw gateway. The quincer tool is now available.

OpenClaw actions (takeovers, replies) appear in your Quincer inbox under the OpenClaw team member, with their own avatar and audit trail — not as a generic "external agent."