Crisp

Crisp is a messaging-first support platform offering live chat, chatbot, shared inbox, knowledge base, and status pages. For agents, the distinctive feature is real-time capability: a WebSocket-based RTM (Real Time Messaging) API enables agents to participate in conversations in real-time, not just via webhooks. The REST API covers conversation management, contact profiles, and knowledge base articles. The plugin system allows extending Crisp's behavior from within conversations. Chatbot scenarios can be built visually and triggered programmatically. Pricing is straightforward with a functional free tier. Main limitations: smaller marketplace ecosystem, less mature third-party integration library, and documentation that assumes familiarity with the platform's concepts rather than explaining them from scratch.

REST API uses Basic Auth with a plugin identifier and key. Tokens are generated per-plugin in the Crisp Marketplace developer area. Plugin tokens can be scoped to specific websites (workspaces). For internal integrations, tokens are created via the developer settings. The RTM API authenticates using the same plugin credentials. No OAuth for third-party integrations — the plugin marketplace uses its own distribution model. Token permissions are tied to the plugin's requested scopes at registration. For agents, obtaining credentials requires creating a plugin entry (even for internal use), which adds a setup step. No temporary credential mechanism. Webhook payloads are signed with a secret for verification.

Documentation at docs.crisp.chat covers the REST API, RTM API, and JavaScript SDK. API reference includes endpoint descriptions and parameter tables. The RTM API documentation includes event type listings and WebSocket connection examples. Node.js SDK (crisp-api) is the best-maintained client library — maintained by Crisp directly. Libraries for other languages (Python, Ruby, Go, PHP) exist but with varying quality. The documentation style is functional but could benefit from more integration-pattern guides and end-to-end examples. The Crisp developer community is smaller than competitors' but the team is responsive on GitHub and their support channels. For agents building real-time chat integrations, the RTM documentation is the most valuable section.

Crisp offers two API paths: REST API at api.crisp.chat/v1/ for standard CRUD operations, and RTM API via WebSocket for real-time conversation participation. The REST API covers websites (workspaces), conversations, messages, contacts, and knowledge base. Conversation management includes sending messages, changing state, assigning to operators, and adding notes. The RTM API streams conversation events in real-time — message received, message sent, conversation opened, etc. — enabling agents to react instantly rather than polling. The dual REST+WebSocket architecture is more complex to implement but powerful for chat-oriented agents. Pagination uses offset-based patterns. Markdown is supported in messages. File attachments use a separate upload endpoint.

REST API errors return JSON with reason and data fields. HTTP status codes follow conventions but error reason strings are Crisp-specific (e.g., 'invalid_parameter', 'not_found', 'forbidden'). Rate limits are documented at 10 requests per second for plugin API access — tighter than most platforms. 429 responses require backoff. The RTM WebSocket connection requires heartbeat messages to stay alive — agents must implement ping/pong handling. Conversation search supports filtering by status, operator, and time range. The platform is generally stable but with a smaller engineering team than enterprise competitors, edge case resolution may be slower. Error documentation could be more comprehensive — not all error codes are documented with resolution guidance.