AsyncAPI channel · Crisp · Crisp Realtime Surface (Webhooks + RTM)

rtm/authentication

Socket.IO event the client emits within ~10s of connecting to authenticate. Server replies with `authenticated` on success or `unauthorized` on failure.

Open source AsyncAPI → All Crisp channels Crisp provider profile
Provider: Crisp AsyncAPI: v2.6.0 Spec: Crisp Realtime Surface (Webhooks + RTM) Operations: 2 Messages: 3

Channel address

rtm/authentication

Operations

publish
sendAuthentication
onAuthenticationResult

Messages

authentication
Socket.IO `authentication` event
Content-Type:
authenticated
Socket.IO `authenticated` ack
Content-Type:
unauthorized
Socket.IO `unauthorized` ack
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.