/enterprise/orgs/{org_id}/siem) forwards completed enterprise audit events to one HTTPS endpoint. ReclaimLLM is the producer. Your SIEM is the consumer.
The internal record stays on the Audit tab. SIEM delivery sends that record outward. It does not create a second analytics product.
What you’ll see
- Destination — enable or disable delivery, one webhook URL, and authentication.
- Event categories — which new audit categories are sent.
- Delivery health — queued, retrying, failed, consecutive failures, last success, and last failure.
- Contract — schema version, at-least-once delivery,
event_ididempotency, a 24-hour retry window, and no history replay.
Payloads contain the audit record only. They do not include prompts, responses, session bodies, raw request bodies, or the destination secret.
What you can do
Authentication is a bearer token or one API-key header. The header name is required for API-key mode and defaults to
X-SIEM-API-Key. The secret is encrypted at rest. After it is saved, the page shows that a secret is configured and does not return the value. Leave the field blank to keep the current secret.
Redirects and private-network destinations are rejected.
Event categories
Only completed events in the selected categories are delivered, and only events that finish after delivery is enabled. Pending audit events are not sent. Historical replay is off.
Delivery contract
Each request is one JSON event:schema_versionis1.0event_idis the idempotency key, also sent asIdempotency-KeyandX-ReclaimLLM-Event-ID- A
2xxresponse counts as delivered - Delivery is at least once. Receivers must tolerate a duplicate
event_id - Temporary failures retry for 24 hours
- A configuration failure is not retried automatically
Who sees it
Admin only, from the Admin menu.Related pages
- Audit — the ledger these events come from
- Compliance — RC-AI-09 uses SIEM delivery when it is enabled