Skip to content

Send events via the REST API

You can send actor profiles along by using the endpoint POST /events.

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.
  • attributes (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.

Request example

{
"org_id": "demo",
"project_id": 12345,
"actor_profile": {
"microservice": "accounts-ms"
},
"attributes": {
"request_method": "POST",
"request_url": "/login",
"request_body": {
"username": "john",
"password": "123"
},
"request_ip": "1.1.1.1"
}
}

Response example

{
"message": "success"
}

Collector > Collecting events via the REST API

A comprehensive data collection system that enables sending actor data and events through multiple integration methods including REST API websocket and CLI agent for manufacturing observation and analysis.

Agent > Send events via the CLI agent

The Manufactory agent enables sending actor-generated events by requiring base64-encoded actor and event objects with specific attribute values and data types.

Events > Create events schema

The POST /events/schema endpoint enables creation of event schemas by defining organization ID project ID and attribute specifications while requiring authentication through a Manufactory access token.

Actors > Create actors schema

A POST request to /actors/schema endpoint creates user schemas by specifying organization details project information and attribute definitions while requiring authentication through a Manufactory access token.