After filling the required values in the previous section, we can start sending actor’s generated events via Manufactory agent.
Required keys
--actor (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.
--event (required) object - Pairs containing attribute name and the corresponding value while considering the correct attribute names and data types. Please refer to Get events schema.
Actor example
{
"city":"New York",
"country":"USA",
"username":"john.doe",
"email":"john.doe@email.com"
}
Event example
{
"event_name":"login",
"event_type":"user-actions",
"made_purchase":false
}
Before we pass actor and event objects, we need to encode the objects using base64.
The POST /events endpoint allows sending actor profiles with required fields including organization ID project ID actor profile details and attribute specifications for successful event tracking and monitoring.
The Manufactory agent serves as a data collection tool that enables sending actor data and events through various integration methods while being particularly suitable for IoT devices with limited resources or API offloading needs.
Websocket connections enable real-time event transmission by sending messages with event type and attributes while receiving status confirmations through an established channel.
A data collection system enables event and actor information transmission through REST API websocket or CLI agent integration while providing a simple interface for viewing the collected data.