Inbound alert ingestion and batch alert resolution — the write path monitoring tools use to push events into BigPanda.
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
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/bigpanda:bigpanda-alerts-api"curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
title: Bigpanda Alerts API
license:
name: Proprietary
url: https://www.bigpanda.io/legal/
x-refined-note:
- x-generated-from differs across the merged source definitions and was not carried
- x-refined-note differs across the merged source definitions and was not carried
version: '1.0'
description: 'Operations tagged Alerts across 2 of this provider''s published API definitions: bigpanda-openapi.yml, bigpanda-alerts-api-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.bigpanda.io
description: BigPanda API
- url: https://api.eu.bigpanda.io
description: EU Region
tags:
- name: Alerts
description: Ingest and manage monitoring alerts
paths:
/data/v2/alerts:
post:
operationId: sendAlert
summary: BigPanda Send Alert
description: Ingests a monitoring alert into BigPanda for correlation and incident management.
tags:
- Alerts
security:
- bearerAuth: []
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AlertRequest'
examples:
SendAlert201Example:
summary: Default sendAlert request example
x-microcks-default: true
value:
app_key: abc123appkey
status: critical
host: production-database-1
check: CPU overloaded
description: CPU usage above 95% for 5 minutes
responses:
'201':
description: Alert ingested successfully.
content:
application/json:
schema:
$ref: '#/components/schemas/AlertResponse'
examples:
SendAlert201Example:
summary: Default sendAlert 201 response
x-microcks-default: true
value:
_id: alert-abc123
status: ok
'400':
description: Invalid alert payload.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
servers:
- url: https://api.bigpanda.io
description: BigPanda API
/resources/v2.0/environments/{environment_id}/batch-resolve/alerts:
servers:
- url: https://api.bigpanda.io
description: US Region
- url: https://api.eu.bigpanda.io
description: EU Region
post:
summary: Resolve Alerts
deprecated: false
description: 'Sets the alert status to "OK" for a list of alerts.
> 🚧 **Authentication**
>
> All BigPanda APIs require Bearer Token Authorization in the call headers.
>
> This API uses the User API Key type of Authorization token. Your User API Key must be provided in the header, prefixed by the word `Bearer`.
>
> Example:
> `Authorization: Bearer [YOUR_USER_API_KEY]`
**Rate limit:** 1 call per second; up to 500 alerts per request.'
operationId: resolve-alerts
tags:
- Alerts
parameters:
- name: environment_id
in: path
description: The system id of a BigPanda environment
required: true
example: ''
schema:
type: string
examples:
- 63bd568809cb331300ffa555
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/resolve_alerts'
responses:
'202':
x-apidog-ordering: 0
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/generic202response'
headers: {}
x-apidog-name: ''
security:
- BearerUser131: []
x-publication-status: live
x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37769996-run
x-source-url: https://api-docs.bigpanda.io/resolve-alerts-37769996e0.md
x-source-page: Resolve Alerts
/resources/v2.0/tags:
servers:
- url: https://api.bigpanda.io
description: US Region
- url: https://api.eu.bigpanda.io
description: EU Region
get:
summary: Retrieve destination tags
deprecated: false
description: 'Retrieves destination tags in reverse order by most recent received time
in BigPanda.
## Authentication
All BigPanda APIs require Bearer Token Authorization in the call headers.
This API uses the User API Key type of Authorization token. Your User API Key must be provided in the header, prefixed by the word `Bearer`.
Example:
`Authorization: Bearer [YOUR_USER_API_KEY]`'
operationId: get-destination-tags
tags:
- Alerts
parameters:
- name: source_system
in: query
description: The ID of the integration that sent the tag.
required: false
example: ''
schema:
type: string
- name: page
in: query
description: Which set of results to return.
required: false
example: 0
schema:
type: integer
default: 1
examples:
- 4
- name: per_page
in: query
description: Number of results to show for each page.
required: false
example: 0
schema:
type: integer
default: 100
examples:
- 30
responses:
'200':
x-apidog-ordering: 0
description: '200'
content:
application/json:
schema:
$ref: '#/components/schemas/destination_tags'
headers: {}
x-apidog-name: ''
security:
- BearerUser131: []
x-publication-status: live
x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770018-run
x-source-url: https://api-docs.bigpanda.io/retrieve-destination-tags-37770018e0.md
x-source-page: Retrieve destination tags
components:
schemas:
AlertResponse:
title: Alert Response
description: Response after ingesting an alert.
type: object
properties:
_id:
type: string
description: Internal alert ID.
example: alert-abc123
status:
type: string
description: Ingestion status.
example: ok
AlertRequest:
title: Alert Request
description: Payload for ingesting a monitoring alert.
type: object
required:
- app_key
- status
- host
properties:
app_key:
type: string
description: BigPanda application key for routing.
example: abc123appkey
status:
type: string
description: Alert status.
enum:
- critical
- warning
- ok
- acknowledged
example: critical
host:
type: string
description: Hostname associated with the alert.
example: production-database-1
check:
type: string
description: Check or metric name that triggered the alert.
example: CPU overloaded
description:
type: string
description: Human-readable alert description.
example: CPU usage above 95% for 5 minutes
timestamp:
type: integer
description: Unix timestamp of the alert.
example: 1713000000
ErrorResponse:
title: Error Response
description: Standard error response.
type: object
properties:
error:
type: string
description: Error message.
example: resource not found
status:
type: integer
description: HTTP status code.
example: 404
comments:
type: string
description: An optional comment or short description.
x-apidog-folder: ''
examples:
- Marking for regional similarity
resolve_alerts:
required:
- ids
type: object
properties:
comments:
description: An optional comment to add to the resolve action. **May not be longer than 1000 characters.**
$ref: '#/components/schemas/comments'
ids:
type: array
description: A list of the unique identifiers for each alert to resolve
items:
type: string
examples:
- - 5d09d221aebaec1c43ccd448
- 5cff623a21169351a82cb5e2
x-apidog-orders:
- comments
- ids
x-apidog-folder: ''
x-apidog-ignore-properties: []
generic202response:
type: object
description: 'Call was successful.
'
properties:
status:
type: integer
examples:
- 202
data:
type: object
properties: {}
x-apidog-orders: []
x-apidog-ignore-properties: []
x-apidog-orders:
- status
- data
x-apidog-folder: ''
examples:
- status: 202
data: {}
x-apidog-ignore-properties: []
destination_tags:
type: array
description: List of tags in the reverse order from when they were received by BigPanda.
items:
$ref: '#/components/schemas/destination_tag'
x-apidog-folder: ''
destination_tag:
type: object
description: Schema representing a BigPanda alert tag as ingested through alert processing.
properties:
name:
type: string
description: Name of the alert tag.
_id:
type: string
description: System id for the tag in BigPanda
parent_source_system:
type: string
description: The integration tool sending the associated event.
source_system:
type: string
description: The name of the specific integration that processed the event.
last update:
type: integer
description: The time the event was last updated, in unix epoch seconds.
total_hits:
type: string
description: The total number of times the alert has been processed in BigPanda.
x-apidog-orders:
- name
- _id
- parent_source_system
- source_system
- last update
- total_hits
x-apidog-folder: ''
x--orders:
- name
- _id
- parent_source_system
- source_system
- last update
- total_hits
x--ignore-properties: []
securitySchemes:
bearerAuth:
type: http
scheme: bearer
description: BigPanda API Bearer token
BearerOrg121:
type: http
scheme: bearer
description: 'Format: "Bearer {Org Token}" BigPanda recommends adding
[Authentication](https://docs.bigpanda.io/reference/introduction#authentication-and-headers) headers only in the secure tool you use to make API calls
'
BearerUser131:
type: http
scheme: bearer
description: 'Format: "Bearer {User API Key}" BigPanda recommends adding
[Authentication](https://docs.bigpanda.io/reference/introduction#authentication-and-headers) headers only in the secure tool you use to make API calls
'
x-refined-from:
- bigpanda-openapi.yml
- bigpanda-alerts-api-openapi.yml