Before you can start sending data to Manufactory via a web socket, you need to authenticate the client/end-user.
You can authenticate users using the endpoint POST /auth
.
Required header:
X-Manufactory-Auth
- Project key of the project to be populated.
Required keys
org_id
(required) string - Manufactory org ID.project_id
(required) number - The project ID associated with this schema.actor_profile
(required) object - Pairs containing attribute name and the corresponding value while considering the correct attribute names and data types. Please refer to Get Actors schema .
Request example
{
"org_id": "xyz",
"project_id": 12345,
"actor_profile":{
"city": "New York",
"country": "USA",
"username": "john.doe",
"email": "john.doe@email.com"
}
}
Response example
{
"org_id": "xyz",
"project_id": 12345,
"actor_profile_id": 1,
"client_uuid": "dcd21714-894c-46bc-9d59-ae9f22753205"
}
The generated client UUID is limited to this specific user profile, and it’s valid for a 12 hours session. After 12 hours, you would need to re-authenticate the client.
Related articles
Collecting Events via Websocket > Connect to our Web Socket Server
The websocket connection is authenticated using the actor profile ID and client UUID obtained after successful authentication, allowing the sending of actor-generated events.
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.
Actors > Create actors schema
This endpoint allows you to create an actors schema by specifying the required attributes and their data types.
Manufactory > Authentication
Customized authentication is available for Manufactory customers through prior agreement and discussion with the Tallyfy team.