After successful authentication and getting client UUID along with actor profile ID, you can connect to our websocket server: wss://collector.tallyfy.com/ws
Once a websocket connection is established you will receive a message Manufactory Collector ✅
The next step is that we need to pair the connection with the client/end-user. This is where actor profile ID and client UUID become active.
Required keys
type(required) string - The message type, in this case we will be usingauth.org_id(required) string - Manufactory org ID.project_id(required) number - The project ID associated with this schema.actor_profile_id(required) number - The actor profile ID we got after authentication.client_uuid(required) string - the generated UUID we got after authentication.
Websocket message example
{
"type": "auth",
"org_id": "xyz",
"project_id": 12345,
"client_uuid": "e17a56a9-596f-40e6-b01c-d37136df1de8",
"actor_profile_id": 1
}
Websocket reply example
{
"type": "auth",
"status": "ok"
}
Now we are able to send actor’s generated events via the open websocket channel.
Related articles
Collecting Events via Websocket > Authentication for the web socket collector
Authentication is required to send data to Manufactory via a web socket, which can be done using the POST /auth endpoint with the project key, org ID, project ID, and actor profile details in the request header and body.
Collecting Events via Websocket > Send events via the web socket
Web socket connections enable sending user-generated events with specific attributes via an open channel.
Collector > Collecting Events via Websocket
Web sockets facilitate real-time, bi-directional communication between servers and clients, making them ideal for long-lived browser sessions.
Collecting events via our CLI agent > Authentication for the agent collector
The config file for Manufactory requires the org ID, project ID, and project key to authenticate and send data.