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"
}

Websocket > Connect to our Web Socket Server

Connect to the websocket server with authentication credentials and pair the connection using actor profile ID and client UUID to establish a secure communication channel for sending actor-generated events.

Collector > Collecting Events via Websocket

A bidirectional data communication system utilizing websockets REST API and CLI agents enables real-time data collection and authentication through the Manufactory Collector platform for manufacturing observation.

Agent > Send events via the CLI agent

The Manufactory agent facilitates event transmission by accepting base64-encoded actor and event objects with specific attributes for user tracking and monitoring purposes.

Rest Api > Send events via the REST API

The POST /events endpoint enables sending actor profiles by requiring org_id project_id actor_profile and attributes with specific data formatting and returns a success message upon completion.
Get in touch
About Tallyfy