Create agent instance history itemAdded in 8.10
POST/agent-instances/:agentInstanceKey/history
Strongly Consistent About endpoint data consistency
Appends a single history item to an agent instance's conversation history. The created item has commitStatus PENDING until the job identified by jobLease completes successfully, at which point it transitions to COMMITTED. If the job fails or is superseded by a retry, the item is marked DISCARDED.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 500
- 503
The history item was created.
The provided data is not valid.
The request lacks valid authentication credentials.
Response Headers
Forbidden. The request is not allowed.
The agent instance with the given key was not found, or the specified jobKey does not correspond to an active job. More details are provided in the response body.
An internal error occurred while processing the request.
The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains RESOURCE_EXHAUSTED. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .