Skip to content

Send events via the web socket

After establishing a websocket connection with Tallyfy Manufactory1, we can start sending user-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

Tallyfy Manufactory websocket authentication requires establishing a connection to wss://collector.tallyfy.com/ws then sending an auth message with five required keys (type org_id project_id client_uuid actor_profile_id) to pair the connection with the authenticated client before events can be transmitted.

Events > Create events schema

Tallyfy Manufactory allows you to create events schemas by sending a POST request to /events/schema with organization ID project ID and attribute definitions using proper authentication headers.

Rest Api > Send events via the REST API

The POST /events endpoint enables sending actor profiles to Tallyfy Manufactory by providing organization ID project ID actor profile object and event attributes with proper schema validation.

Footnotes

  1. Tallyfy’s event tracking and analytics platform for process automation insights ↩

Get in touch
About Tallyfy