agent_id claim matches the agent identified by the provided agent key, ensuring a session cannot be used to log events on behalf of a different agent.
You must call the session creation endpoint first to obtain an
X-OTAS-AGENT-SESSION-TOKEN before logging events. The session token is bound to a single process — never reuse it across separate runs.Request
string
required
The agent’s API key. Used to identify and authenticate the agent via UASAM.
string
required
Session JWT obtained from the session creation endpoint. Must have been issued for the same agent as the agent key.
Body
Required fieldsstring
required
UUID of the project this event belongs to.
string
required
The external API path that was called (e.g.
/api/v1/the-external-path).string
required
HTTP method used for the external request (e.g.
GET, POST, PUT, DELETE).number
required
HTTP status code returned by the external API.
number
required
Actual measured round-trip latency of the external request in milliseconds.
number
Size of the request payload in bytes.
number
Size of the response payload in bytes.
string
Serialized request headers sent to the external API.
string
Raw or serialized request body sent to the external API.
string
Query string or serialized query parameters.
string
Form post data, if applicable.
string
Serialized response headers received from the external API.
string
Raw or serialized response body received from the external API.
string
Content-Type of the request (e.g. application/json).string
Content-Type of the response.object
Arbitrary JSON object for attaching user-defined metadata to the event.
string
Error message or identifier if the external request failed. Leave empty on success.
object
Additional JSON metadata for internal or debugging purposes.
Response
On success the endpoint returns HTTP201 and includes an event_id in the response object. You can use this ID to retrieve the event later via the session events endpoint.
number
required
1 on success, 0 on failure.string
required
event_captured on success.object
required