Skip to content

Authentication for the agent collector

Authentication

Before you can start sending data to Manufactory, you need to fill the config file with the following values.

Required keys

  • org_id (required) string - Manufactory org ID.
  • project_id (required) number - The project ID associated with this schema.
  • project_key (required) string - of the project to be populated.

config.yaml

org_id: xyz
project_id: 12345
project_key: b0iqA8ezfhPgacy32PybGWghRkGrOo9H

manufactory-agent and config.yaml file should be within the same folder.

Manufactory > Projects

Projects in Manufactory require unique API keys and separate schemas for users and events which must be set up before sending platform-specific data from different applications.

Collector > Collecting events via our CLI agent

The Manufactory agent serves as a data collection solution that enables sending actor information and events through various integration methods while reducing API load and supporting IoT devices with limited resources.

Websocket > Connect to our web socket server

Authentication for a websocket connection requires pairing with client/end-user through an auth message containing org ID project ID actor profile ID and client UUID before enabling event transmission.