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

The websocket connection process requires authentication with client UUID and actor profile ID followed by pairing the connection using an auth message containing organization details and profile credentials to establish an active event transmission channel.

Collector > Collecting events via websocket

A comprehensive guide to real-time data collection methods showcasing REST API websocket and CLI agent integrations for manufacturing monitoring through secure authentication channels and IoT device connections.

Agent > Send events via the CLI agent

The Manufactory agent enables sending actor-generated events by requiring base64-encoded actor and event objects with specific attribute values and data types.

Rest Api > Send events via the REST API

The POST /events endpoint allows sending actor profiles with required fields including organization ID project ID actor profile details and attribute specifications for successful event tracking and monitoring.
Get in touch
About Tallyfy