Varqeni Help

Webhooks, deploy events and the read-only API

Updated 11 November 2026

Three small connections, each signed or token-protected, none of which can change anything in your systems.

AvailabilityAvailable to everyone with early access to Varqeni.

How it works

  • Deploy events: your CI posts each deploy (service, version, commit, who). A service that starts failing within 10 minutes of one, with no clean run in between, is named as a bad deploy, with what was deployed.
  • Outbound webhook: every incident, page and resolve as JSON to your endpoint, signed so you can check it came from Varqeni, and retried if your endpoint is busy.
  • Read-only API: incidents, one incident with its seal check and report, and its timeline. Your administrator makes a token on the Varqeni host; it is shown once and stored only as a hash.

What you should see: Requests are limited per minute, and nothing in the API can approve, change or delete anything. In the Fortis lab a recorded deploy followed by errors was named as the bad deploy with its version, commit and who, and the API answered with a token, refused without one, refused writes, and refused the token once revoked. A page and its resolve reached a test endpoint signed, and a delivery the endpoint turned away was retried two seconds later.

What it can and cannot do

Can

  • Take deploy events from your CI and name the deploy that broke a service, and answer read-only API calls with a token. Send every notice, page and resolve to your endpoint, signed and retried.

Cannot

  • Approve, change or delete anything through the API, or send a webhook unsigned.

Still stuck? Contact support or email info@fortisdatagroup.com.