Request Models

Request

Represents a container for one or more interactions in a session.

RequestData

Contains a request with its associated interactions.

Session

Groups multiple requests by session identifier.

GetRequestsRequest

Request model for getting requests grouped by session.

GetRequestsResponse

Response model for getting requests.

DeleteRequestRequest

Request model for deleting a request and all its associated interactions.

DeleteRequestResponse

Response model for request deletion requests.

DeleteSessionRequest

Request model for deleting all requests in a session.

DeleteSessionResponse

Response model for session deletion requests.

SetSessionOutcomeRequest

Records an optional external success, failure, or unknown outcome for an existing session. The server derives user_id and source from the earliest request ordered by (created_at, request_id); callers cannot override either field.

SetSessionOutcomeResponse

For a canonical row, an exact retry must match the caller payload, outcome contract, and canonical trajectory. It returns the same identity fields with success=true and recorded=false. A mismatch returns success=false, recorded=false, and reason="conflicting_finalization"; it does not replace the outcome you reported.

Outcomes Reflexio inferred

Where a session has no reported outcome, Reflexio may record one it inferred from its own evaluation of the session, so that playbook tuning has something to learn from. An inferred outcome never overwrites yours, and never takes the place of a report you have already made.

Your report always wins. If you report an outcome for a session Reflexio has already inferred one for, your report replaces it: the call returns success=true, recorded=true, and an outcome_revision of 2. The inferred outcome is retained alongside it for later analysis, and is not returned by the API.

This is the only case in which a stored outcome is replaced. An outcome you reported yourself stays immutable, and a second differing report still returns conflicting_finalization.

A rolling-upgrade row whose four identity fields are all null still compares the caller payload and any available server-derived session context, but it cannot compare the absent contract or trajectory digests. An accepted retry preserves all four identity fields as null. A changed payload or available session context returns conflicting_finalization.

SessionOutcomeRecord

For canonical records, the four identity fields are populated together. Legacy rolling-upgrade records may return all four as null and preserve those nulls on retry; a partial identity is invalid.

GetSessionOutcomesRequest

All supplied filters combine with AND. Results use exact, case-sensitive matches and are ordered by occurred_at DESC, then user_id and session_id ascending.

GetSessionOutcomesResponse