List alert sources.
const url = 'https://api.siteqwality.com/v1/alert-sources';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.siteqwality.com/v1/alert-sources \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”next_cursor from the previous page.
1 to 200, default 50.
Responses
Section titled “ Responses ”The account’s alert sources, newest first. Keys are never listed
{"data": [...], "next_cursor": ...}; the /v1 shaping keeps it as is.
object
A source as the api returns it. The key is never stored, only its hash and first characters.
object
Incidents open on this service.
Overrides the service’s escalation policy for incidents this source opens.
The key’s first characters, to tell keys apart.
Where an email source receives alerts. Rolling the key replaces it.
How an email source reads each email.
object
A subject that matches resolves its incident instead of opening one, for example ^(UP|RECOVERY|OK)\b.
Its first group, or the whole match, is the dedup key, so each thing it names gets its own incident: for
example (?:DOWN|UP): (.+). Left out, or with no match, all of the address’s emails share one incident.
Where a generic_json source finds each field.
object
The dedup key: events with the same one open, update and close one incident.
The status. Left out, every event triggers.
Status values that trigger, ignoring case. Empty takes trigger, triggered, firing, alert, alerting,
open, problem and down.
Status values that resolve. Empty takes resolve, resolved, ok, recovered, closed, up, normal and
cleared.
Status values that acknowledge. Empty takes acknowledge, acknowledged and ack.
The severity: critical, error, warning, info or a common synonym.
An http(s) link back to the alert.
With a signing secret set: the header holding the body’s HMAC-SHA256, in hex or base64, with or without
sha256=. Left out, X-Signature.
With a signing secret set: a header holding the Unix time the sender signed at. When named, the signature
covers <timestamp>.<body> and must be under 10 minutes old.
Whether a signing secret is set (sentry and generic_json). The secret itself is never returned.
While set, each event keeps its body, redacted, for debugging. Ends 24 hours after it was turned on.
Send back as cursor for the next page; null on the last one.
Example generated
{ "data": [ { "id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "account_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "service_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "escalation_policy_id": "2489E9AD-2EE2-8E00-8EC9-32D5F69181C0", "name": "example", "format": "example", "key_prefix": "example", "email_address": "example", "email_rules": { "resolve_pattern": "example", "dedup_pattern": "example" }, "mapping": { "dedup_key": "example", "summary": "example", "status": "example", "trigger_values": [ "example" ], "resolve_values": [ "example" ], "acknowledge_values": [ "example" ], "severity": "example", "link": "example", "signature_header": "example", "timestamp_header": "example" }, "signing_secret_set": true, "debug_capture_until": "2026-04-15T12:00:00Z", "disabled_at": "2026-04-15T12:00:00Z", "last_event_at": "2026-04-15T12:00:00Z", "created_at": "2026-04-15T12:00:00Z" } ], "next_cursor": "example"}Invalid limit or cursor
An RFC 9457 problem, the body of every /v1 error.
object
https://docs.siteqwality.com/errors/ and the failure’s code, such as not_found.
urn:uuid: and the request id.
The invalid fields, when the request body was refused.
One validation failure; pointer is an RFC 6901 pointer into the request body.
object
Example generated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example", "errors": [ { "pointer": "example", "detail": "example" } ]}Missing or invalid credentials
An RFC 9457 problem, the body of every /v1 error.
object
https://docs.siteqwality.com/errors/ and the failure’s code, such as not_found.
urn:uuid: and the request id.
The invalid fields, when the request body was refused.
One validation failure; pointer is an RFC 6901 pointer into the request body.
object
Example generated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example", "errors": [ { "pointer": "example", "detail": "example" } ]}The key or member may not do this, or lacks the scope it needs
An RFC 9457 problem, the body of every /v1 error.
object
https://docs.siteqwality.com/errors/ and the failure’s code, such as not_found.
urn:uuid: and the request id.
The invalid fields, when the request body was refused.
One validation failure; pointer is an RFC 6901 pointer into the request body.
object
Example generated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example", "errors": [ { "pointer": "example", "detail": "example" } ]}Too many requests; wait for the time in Retry-After
An RFC 9457 problem, the body of every /v1 error.
object
https://docs.siteqwality.com/errors/ and the failure’s code, such as not_found.
urn:uuid: and the request id.
The invalid fields, when the request body was refused.
One validation failure; pointer is an RFC 6901 pointer into the request body.
object
Example generated
{ "type": "example", "title": "example", "status": 1, "detail": "example", "instance": "example", "errors": [ { "pointer": "example", "detail": "example" } ]}