Authentication for the agent collector

Authentication

Before you can start sending data to Tallyfy 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[^2] (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.

Related articles

Collector > Collecting events via our CLI agent

The Tallyfy Manufactory collector agent provides a lightweight solution for off-loading API event transmission and enables data collection from IoT devices with limited computing power or connectivity constraints.

Websocket > Authentication for the web socket collector

Tallyfy Manufactory requires websocket client authentication through a POST /auth endpoint using organization ID project ID and actor profile data to generate a 12-hour session UUID.

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.

Manufactory > Collector

The Tallyfy Manufactory collector enables sending actor data and events through REST API websocket or CLI agent methods with data viewable in a custom interface after creating required schemas.

Footnotes

1. Directus-based data management system for custom schemas and workflows ↩