Skip to content

Send events via the CLI agent

Send events

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.

Agent example

Terminal window
manufactory-agent --actor=ewogICAgImNpdHkiOiAiTmV3I \
--event=ewogICAgImV2ZW50X25hbWUiO==

The agent will handle the authentication and sending events, then it will shut down.

Rest Api > Send events via the REST API

Actor profiles can be transmitted by sending a POST request to the /events endpoint with required fields including organization ID, project ID, actor profile object, and attributes object containing specific data values.

Collector > Collecting events via our CLI agent

The Manufactory agent enables data collection and event transmission through various methods while being particularly beneficial for IoT devices with limited resources or when API offloading is needed.

Websocket > Send events via the web socket

Events can be transmitted through a websocket connection by sending a message containing a type and attributes object, which will receive a status confirmation reply.