Skip to main content
Grantiva watches your organization’s attestation failure rate and emails you when it spikes — a fast signal that a bad release, a misconfigured app, or an expired Team ID setting is blocking real users. How it fires
  • The failure rate is computed over the last hour of attestations.
  • An alert is sent when the rate is above your threshold and at least minAttestationCount attestations happened in that window.
  • After an alert, the organization is in a 4-hour cooldown before another can be sent.
  • Alerts are emailed to the organization’s billing contact, falling back to the owner’s account email.

Authentication

These endpoints accept either a dashboard session cookie or a server API key sent as Authorization: Bearer <key>.

Get the alert configuration

Returns the organization’s configuration. If none has been saved yet, a default, not-yet-persisted configuration is returned with isEnabled: false — the id in that case is a placeholder and changes between calls. Response

Update the alert configuration

Creates the configuration on first call. Only fields present in the body are changed. Request body
Response200 OK — the updated configuration. Errors

List alert history

The 50 most recent alerts sent for this organization, newest first. Response

See also