List services for the account, with their health.
const url = 'https://api.siteqwality.com/service';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/service \ --header 'Authorization: Bearer <token>'Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Query Parameters
Section titled “Query Parameters ”Page size, 1 to 100 (default 50); larger values are clamped.
Deprecated: rows to skip. Use cursor; the two cannot be combined.
next_cursor from the previous page, with the same filters and sort.
Matches name, description or team, case-insensitively.
Only services owned by this team (case-insensitive).
Only services carrying this tag (case-insensitive).
Comma-separated health statuses: operational, degraded, partial_outage, major_outage.
-created_at (default), created_at, name, -name, status (worst first) or
-last_incident_at.
Responses
Section titled “ Responses ”Page of services: data is the array, total counts every match and next_cursor fetches the next page
One page of services: data stays the bare array.
object
object
Whether a failing monitor opens an incident on its service.
Deprecated and unused: every failure joins the service’s open auto incident.
A failure this many minutes after a resolved auto incident’s last alert reopens it; 0 never does.
Whether an auto-created incident resolves itself once every monitor recovers.
When the service was switched off; while set its monitors open no auto incidents.
Prefills Publish and words auto-published incidents.
object
The public title; auto-published incidents never show the monitor’s name.
The first public update when the incident is published.
The public “Resolved” update.
The team that owns the service; filter the list with team.
Free-form labels; filter the list with tag.
Who is on call for this service; without it, the escalation policy’s first level.
The roll-up of incidents, monitors, maintenance and on call. On the list and get routes.
object
The worst of incident and monitor state. Maintenance never changes it.
A maintenance window naming this service is running now. It holds paging, never the status.
Linked monitors failing now; paused ones are left out.
When the newest incident on the service opened.
The service’s on-call schedule, else every user and schedule on the policy’s first level.
One person on call for a service right now.
object
The schedule that puts them on call; absent for a user named on the policy directly.
When the schedule hands off; absent for a direct user or past 90 days.
Services matching the filters, across every page.
Pass back as cursor for the next page; null on the last.
Example
{ "data": [ { "incident_creation_mode": "auto", "auto_resolve": "always", "default_incident_severity": "minor", "health": { "status": "operational" } } ]}Unknown sort or status, a cursor from another sort, or cursor with offset
Missing or invalid authentication
Internal server error