Append a batch of Edge agent action events
Changed onAppends a fully prevalidated, ordered batch for existing Edge session/execution parents. Mixed-tenant or invalid items are rejected before append where possible. Large raw payloads must be stored separately and referenced by artifact_ptrs. Optional Idempotency-Key retries are scoped by tenant and endpoint: the same normalized batch replays the first 201 response without partial append or duplicate events, while the same key with a different normalized batch returns 409 idempotency_conflict. The append and replay record commit in one Redis transaction. If the replay record has expired and any same logical event_id is already present, the API returns 409 idempotency_window_expired and does not append duplicate events.
Request
- Base URL: http://localhost:8081
- URL: http://localhost:8081/api/v1/edge/events/batch
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Headers
Tenant isolation header (required on all protected routes).
Optional idempotency key for safe retries. Edge event create/batch scopes keys by tenant and endpoint, replays the first response for the same normalized request, and returns 409 idempotency_conflict if the same key is reused with a different normalized request. Callers SHOULD send a UUID (per the original Job submit contract); the Edge runtime additionally accepts any non-empty string up to 512 bytes for backward-compatible local-dev keys.
Request body
Response
Edge events appended in input order
Changes
- warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
limit_exceededenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
replay_window_fullenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status - warning
added the new
step_up_requiredenum value to theresponse property for the response status
- warning
- info
endpoint added
- info