We’ve added a new enhancement to the StatusGator API that makes it faster and easier to identify service issues in real time: status-based filtering for monitors and components.
Why this matters
Some services expose hundreds (or thousands) of components. If you’re using the API to determine what’s currently having problems, paging through every component just to find the few that are affected is inefficient and noisy.
With this update, you can now filter API responses to only the statuses you care about, dramatically reducing response size and time-to-insight.
What’s new
Both the monitors and components endpoints now support an optional status query parameter.
You can use it to:
- Fetch only components or monitors with a specific status
- Fetch only affected components (anything that is not
up) - Filter by multiple statuses at once
Example requests
Filter monitors by a specific status:
GET /boards/{id}/monitors?status=up
Retrieve only affected components (anything not fully operational):
GET /boards/{id}/monitors/{id}/components?status=affected
Filter by multiple statuses using a comma-separated list:
GET /boards/{id}/monitors/{id}/components?status=down,warn
Supported filtering options
affected– returns all components or monitors that are notup- Specific statuses – such as
up,down,warn - Multiple statuses – comma-separated for flexible filtering
The result
This change makes it much easier to:
- Quickly identify outages or degraded services
- Build alerting or dashboards that focus only on current issues
- Avoid unnecessary pagination and large API responses
