Skip to content

Send events via the web socket

After establishing a web socket connection, we can start sending user’s generated events via the open channel.

Required keys

  • type (required) string - The message type, in this case we will be using event.
  • attributes (required) object - Pairs containing attribute name and the corresponding value while considering the correct attribute names and data types. Please refer to get events schema.

Websocket message example

{
  "type": "event",
  "attributes": {
    "event_name": "login",
    "event_type": "user-actions",
    "made_purchase": false
  }
}

Websocket reply example

{
  "type": "event",
  "status": "ok"
}

Collector > Collecting events via websocket

A comprehensive system enables real-time data collection through multiple integration methods including REST API websocket and CLI agent while providing secure authentication and data viewing capabilities.

Websocket > Connect to our web socket server

Authentication for a websocket connection requires pairing with client/end-user through an auth message containing org ID project ID actor profile ID and client UUID before enabling event transmission.

Events > Create events schema

The POST /events/schema endpoint allows creation of custom event schemas by specifying organization details project ID and attribute definitions using a Manufactory access token for authentication.
Get in touch
About Tallyfy