List this merchant's endpoint-health alerts
GET
/alertsAuthorization
AuthorizationBearer token (JWT) · headerrequiredJWT issued by the external IdP via the OAuth 2.0 authorization-code flow (Kinde in
production; a simulator in test). The client obtains it and sends it as a Bearer token on
every authenticated call. Sarvex's services verify it — issuer, audience, signature
(IdP JWKS), expiry — and read identity and tenant from its claims. Sarvex does not issue
or revoke these tokens. merchant_id/store_id are read from the verified claims (and the
merchant→store mapping), never from the URL. The operator scope is required for
/operator/*. Operators acting on a specific merchant pass the X-Operate-As header,
which is recorded in the audit log.
Query parameters
cursorstringOpaque pagination cursor from the previous page's page.cursor.
limitintegerMaximum items per page.
min 1 · max 100 · default: 25
statusstringAllowed:
openacknowledgedresolvedseveritystringAllowed:
healthydegradedcriticalstore_idstringResponses
200
Alerts.
dataalert[]requiredShow propertiesHide properties
Array of
alertalert_idstringstore_idstringcheck_typestringseveritystringAllowed:
healthydegradedcriticalstatusstringAllowed:
openacknowledgedresolveddetailstringopened_atstring<date-time>acknowledged_atstring<date-time> | nullacknowledged_bystringresolved_atstring<date-time> | nullauto_resolvedbooleanpagepagerequiredShow propertiesHide properties
cursorstring | nullrequiredhas_morebooleanrequired