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
Response example
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.
After establishing a websocket connection with Manufactory Collector, users need to authenticate by sending a message containing their org ID, project ID, actor profile ID, and client UUID to pair the connection with the client.
The POST /actors/schema endpoint allows creation of actor schemas by specifying organization ID, project ID, attributes with data types, and a unique identifier field while requiring authentication via a Manufactory access token.
Authentication for Manufactory requires configuring a file with organization ID, project ID, and project key values, which must be placed in the same directory as the manufactory-agent file.
The actors schema endpoint returns attribute details like city, country, email, and username for a specified organization and project when authenticated with a Manufactory access token.