Exports and webhooks

Two ways to get data out of Rivarise without using the API: CSV export from the interface, and webhook alerts pushed to an endpoint you control.

CSV export

Available from the Starter plan upward. Export from the Results screen.

• Filters apply. The export contains exactly what the current filters show, so filter to the engine, prompt, date range or citation status you want first.
• Rows are checks. One row per prompt, per engine, per run, including the citation flag, position, sentiment and the answer text.
• Bounded by retention. You cannot export data older than your plan history window.

A note on spreadsheet safety

Answer text comes from third parties and can begin with characters that spreadsheet applications interpret as a formula, such as =, +, - or @. Rivarise neutralizes these fields on export so that opening the file cannot execute anything. If you re-export the data through your own tooling, apply the same handling.

Webhook alerts

Available from the Business plan upward. Configure a webhook as the delivery channel when creating an alert.

When the alert condition is met, Rivarise sends an HTTP POST with a JSON body to the URL you provided. Your endpoint should:

• Accept POST over HTTPS. Plain HTTP endpoints are rejected.
• Return a 2xx status promptly. Slow endpoints may time out.
• Be idempotent. Treat a repeated delivery as the same event rather than a second one.

Slack

Slack delivery, available from Growth, uses a Slack incoming webhook URL. Create one in your Slack workspace, paste it as the destination, and alerts arrive as messages. If Slack messages stop, the usual cause is that the incoming webhook was revoked or regenerated on the Slack side.

Weekly digest

Separate from alerts and included from Starter upward, the weekly digest emails a summary of the week whether or not anything crossed a threshold. It is the low-effort way to keep a stakeholder informed without giving them a seat.

Which to use