Send messages and manage conversation state in Crisp using the website and plugin token REST API

domain: docs.crisp.chat · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Authenticate with an Authorization: Basic base64(identifier:key) header using either a website token or a plugin token keypair
  2. If using a plugin token, also send the X-Crisp-Tier: plugin header alongside Basic auth
  3. Create a conversation with POST /v1/website/{website_id}/conversation
  4. Send a message with POST /v1/website/{website_id}/conversation/{session_id}/message, choosing a type such as text, note, file, or carousel — the call returns 202 Accepted since delivery is asynchronous
  5. Read or change conversation state with GET or PATCH /v1/website/{website_id}/conversation/{session_id}/state, using values pending, unresolved, or resolved

Known gotchas

Related routes

Send operator messages and manage conversations via the Crisp API
crisp · 5 steps · unrated
Assign, close, and manage conversation state via the Intercom Conversations API
developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans