Ragenta Docs
Connections

Webhooks — tell your systems when something happens

Register an endpoint, the available events, verifying the X-Ragenta-Signature header and reading the delivery log.

Settings → Webhooks. Needs a plan with Webhooks and triggers (Starter and up) and webhook.manage (Owner/Admin).

We POST a signed JSON body to your server when something happens here — a run finishes, a document finishes indexing.

Register an endpoint

FieldNotes
NameInternal name.
URLhttps required.
Events to sendPick from the list below.
EnabledOff pauses it without deleting.

After saving, SecretOnce shows the whsec_… secret once. New secret on the endpoint row rotates it (the old one stops working immediately).

Events

EventWhendata carries
agent.run.succeededAn agent run finished and produced an answerrunId agentId agentName trigger credits durationMs
agent.run.failedAn agent run stopped without an answerrunId agentId agentName trigger credits error
document.ingestedA document finished indexing and is searchabledocumentId knowledgeBaseId name chunks
document.failedA document could not be indexeddocumentId knowledgeBaseId name error

The body is always { id, event, occurredAt, workspaceId, data }.

Verify the signature

Every request carries X-Ragenta-Event, X-Ragenta-Delivery (a unique id, use it to de-duplicate) and X-Ragenta-Signature of the form t=<unix>,v1=<hex>.

  1. Read t and v1 from the header.
  2. Compute HMAC-SHA256(secret, t + "." + rawBody) and compare its hex with v1 (constant-time).
  3. Reject when t is more than 5 minutes from now — replay protection.

Answer 2xx within a few seconds. Ragenta retries on failure; after 20 consecutive failures the endpoint flips to switched off after failures and you must re-enable it by hand.

Deliveries

Show under an endpoint opens the log: When · Event · Attempt · Result · Took · Your server said (status code and the start of the response). Status pending · succeeded · failed. Needs webhook.read.

On this page