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"
}
Related articles
Collecting events via our CLI agent > Send events via the CLI agent
The provided content demonstrates how to send events using the Manufactory agent by passing base64-encoded actor and event objects.
Collecting Events via Websocket > Send events via the web socket
Web socket connections enable sending user-generated events with specific attributes via an open channel.
Events > Create events schema
The API endpoint creates an events schema by specifying the required attributes and their corresponding data types for a given project in a Manufactory organization.
Actors > Create actors schema
This endpoint allows you to create an actors schema by specifying the required attributes and their data types.