BigPanda Alert Filters API

Alert filters and filter schedules, in current and v1 routes, for suppressing alerts before correlation.

Operations 20

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /resources/v1.0/plans Create an alert filter (v1, org token) · Create an Alert Filter #
Ask an LLM
“How do I create an alert filter with my org token on the v1 API?”
“Does a v1 alert filter need a BPQL condition and an active flag?”
Tell an agent
Create a v1 alert filter named {name} matching BPQL {bpql}, active {active}.
Using the org token, add filter {name} for {bpql} on schedule {schedule}.
GET /resources/v1.0/plans List alert filters (v1, org token) · Retrieve All Alert Filters #
Ask an LLM
“Can I list alert filters with an organization token on the older v1 endpoint?”
“Which v1 alert filters are currently active?”
Tell an agent
List all alert filters using the v1 org-token endpoint.
Get v1 alert filters where active is {active}.
POST /resources/v2.0/plans Create an alert filter (v2, user API key) · Create an Alert Filter #
Ask an LLM
“How do I suppress noisy alerts with a new filter in BigPanda?”
“Can a new alert filter exclude certain alert statuses?”
Tell an agent
Create an alert filter {name} that drops alerts matching {bpql}, active {active}.
Add filter {name} for {bpql} excluding statuses {exclude_status}.
GET /resources/v2.0/plans List alert filters (v2, user API key) · Retrieve All Alert Filters #
Ask an LLM
“Which alert filters exist in my organization under the current v2 API?”
“Can I see only inactive alert filters with a user API key?”
Tell an agent
List every v2 alert filter with my user API key.
Show v2 alert filters with active set to {active}.
POST /resources/v1.0/schedules Create an alert filter schedule (v1, org token) · Create an Alert Filter Schedule #
Ask an LLM
“How do I create a filter schedule with a start and end date using the org token?”
“Can I create an inactive schedule on the v1 API?”
Tell an agent
With the v1 org-token API, create schedule {name} from {starts_on} to {ends_on}.
Add a v1 filter schedule {name} with active {active}.
GET /resources/v1.0/schedules List alert filter schedules (v1, org token) · Retrieve All Alert Filter Schedules #
Ask an LLM
“Can I list maintenance-style filter schedules with the v1 org token API?”
“Which schedules exist on the legacy v1 schedules endpoint?”
Tell an agent
List all alert filter schedules via the v1 org-token API.
Fetch v1 filter schedules for my organization.
POST /resources/v2.0/schedules Create an alert filter schedule (v2, user API key) · Create an Alert Filter Schedule #
Ask an LLM
“How do I schedule an alert filter to run only during a maintenance window?”
“Can I describe a filter schedule when creating it?”
Tell an agent
Create filter schedule {name} starting {starts_on} and ending {ends_on}.
Add a v2 schedule {name} described as {description}.
GET /resources/v2.0/schedules List alert filter schedules (v2, user API key) · Retrieve All Alert Filter Schedules #
Ask an LLM
“What schedules control when my alert filters are applied?”
“Can I list all filter schedules with my user API key?”
Tell an agent
List all v2 alert filter schedules.
Show every schedule my alert filters can use.
DELETE /resources/v1.0/plans/{filter_id} Delete an alert filter (v1, org token) · Delete an Alert Filter #
Ask an LLM
“Can I delete an alert filter using only an organization token?”
“Is deleting a filter on the v1 endpoint permanent?”
Tell an agent destructive · confirm first
Delete alert filter {filter_id} via the v1 org-token API.
Remove v1 filter {filter_id} from the system.
GET /resources/v1.0/plans/{filter_id} Get an alert filter (v1, org token) · Retrieve an Alert Filter #
Ask an LLM
“Can I read a single alert filter's definition with the org token?”
“What BPQL does a given filter use, via the v1 endpoint?”
Tell an agent
Get alert filter {filter_id} via the v1 org-token API.
Show the v1 definition of filter {filter_id}.
PATCH /resources/v1.0/plans/{filter_id} Update an alert filter (v1, org token) · Update an Alert Filter #
Ask an LLM
“Can I change a filter's BPQL condition with the org token API?”
“Do I have to resend the name, active flag and BPQL when updating a v1 filter?”
Tell an agent
Using the v1 org token, update filter {filter_id} to name {name}, BPQL {bpql}, active {active}.
Change v1 filter {filter_id} custom tags to {custom_tags}.
DELETE /resources/v2.0/plans/{filter_id} Delete an alert filter (v2, user API key) · Delete an Alert Filter #
Ask an LLM
“How do I get rid of an alert filter I no longer need?”
“Will deleting a filter let the previously suppressed alerts through?”
Tell an agent destructive · confirm first
Delete alert filter {filter_id}.
Permanently remove filter {filter_id} with my user API key.
GET /resources/v2.0/plans/{filter_id} Get an alert filter (v2, user API key) · Retrieve an Alert Filter #
Ask an LLM
“What condition and schedule does one of my alert filters use?”
“Can I look up a single filter by ID with a user API key?”
Tell an agent
Get alert filter {filter_id}.
Show the BPQL and schedule of filter {filter_id}.
PATCH /resources/v2.0/plans/{filter_id} Update an alert filter (v2, user API key) · Update an Alert Filter #
Ask an LLM
“Can I deactivate an alert filter without deleting it?”
“How do I attach a schedule to an existing alert filter?”
Tell an agent
Update filter {filter_id}: name {name}, condition {bpql}, active {active}.
Attach schedule {schedule} to alert filter {filter_id}.
DELETE /resources/v1.0/schedules/{schedule_id} Delete a filter schedule (v1, org token) · Delete an Alert Filter Schedule #
Ask an LLM
“Can I delete a filter schedule using the organization token?”
“Is there a v1 route to remove a schedule from the system?”
Tell an agent destructive · confirm first
Delete filter schedule {schedule_id} via the v1 org-token API.
Remove v1 schedule {schedule_id}.
GET /resources/v1.0/schedules/{schedule_id} Get a filter schedule (v1, org token) · Retrieve an Alert Filter Schedule #
Ask an LLM
“Can I read one schedule's start and end with the org token API?”
“Which v1 call shows a single filter schedule?”
Tell an agent
Get filter schedule {schedule_id} via the v1 org-token API.
Show v1 schedule {schedule_id} details.
PATCH /resources/v1.0/schedules/{schedule_id} Update a filter schedule (v1, org token) · Update an Alert Filter Schedule #
Ask an LLM
“Can I extend a schedule's end date with the org token API?”
“Which v1 call edits an existing filter schedule?”
Tell an agent
Using the v1 org token, set schedule {schedule_id} to end on {ends_on}.
Update v1 schedule {schedule_id} active flag to {active}.
DELETE /resources/v2.0/schedules/{schedule_id} Delete a filter schedule (v2, user API key) · Delete an Alert Filter Schedule #
Ask an LLM
“How do I remove a filter schedule I no longer use?”
“Can I delete a schedule with a user API key?”
Tell an agent destructive · confirm first
Delete alert filter schedule {schedule_id}.
Permanently remove schedule {schedule_id} with my user API key.
GET /resources/v2.0/schedules/{schedule_id} Get a filter schedule (v2, user API key) · Retrieve an Alert Filter Schedule #
Ask an LLM
“When does a particular alert filter schedule start and end?”
“Can I look up one schedule by ID with my user API key?”
Tell an agent
Get alert filter schedule {schedule_id}.
Show the start and end dates of schedule {schedule_id}.
PATCH /resources/v2.0/schedules/{schedule_id} Update a filter schedule (v2, user API key) · Update an Alert Filter Schedule #
Ask an LLM
“Can I move a maintenance window's start date on an existing schedule?”
“How do I rename or pause a filter schedule?”
Tell an agent
Change schedule {schedule_id} to start {starts_on} and end {ends_on}.
Rename filter schedule {schedule_id} to {name}.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/bigpanda:bigpanda-alert-filters-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

bigpanda-alert-filters-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: BigPanda Alert Filters API
  description: BigPanda Alert Filters operations, assembled verbatim from the OpenAPI fragments BigPanda publishes on its own API reference at https://api-docs.bigpanda.io/. Each operation carries x-source-url naming the exact provider page it was read from. BigPanda hosts each organization in a single data management region (US or EU); send requests to the base URL for your region.
  version: 1.0.0
  contact:
    name: BigPanda Support
    url: https://api-docs.bigpanda.io/
  license:
    name: Proprietary
    url: https://www.bigpanda.io/legal/
  x-provenance:
    method: searched
    source: https://api-docs.bigpanda.io/llms.txt
    harvested: '2026-09-04'
    assembly: 'Operations copied verbatim from the per-endpoint OpenAPI 3.0.1 fragments BigPanda publishes at https://api-docs.bigpanda.io/<endpoint>.md. Assembly-only normalizations: Apidog x-apidog security metadata stripped, securityScheme type "bearer" corrected to type http/scheme bearer, schema name collisions suffixed. No operation, parameter, schema or response was authored by API Evangelist.'
    operations: 20
servers:
- url: https://api.bigpanda.io
  description: US Region
- url: https://api.eu.bigpanda.io
  description: EU Region
tags:


# --- truncated at 32 KB (45 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/bigpanda/refs/heads/main/openapi/bigpanda-alert-filters-api-openapi.yml