Prometheus

Prometheus notifications API

Server notifications and events.

GitHub OpenAPI

Operations 1

GET /notifications Get notifications #

Documentation

📖
Documentation
https://prometheus.io/docs/prometheus/latest/querying/api/
📖
Documentation
https://prometheus.io/docs/prometheus/latest/querying/basics/
📖
Documentation
https://prometheus.io/docs/prometheus/latest/querying/operators/
📖
Documentation
https://prometheus.io/docs/prometheus/latest/querying/functions/
📖
Documentation
https://github.com/prometheus/alertmanager/blob/main/api/v2/openapi.yaml
📖
Documentation
https://prometheus.io/docs/alerting/latest/alertmanager/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/openapi/prometheus-io-notifications-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/json-schema/prometheus-query-result-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/json-schema/prometheus-target-schema.json

Other Resources

🔗
JSONLD
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/json-ld/prometheus-io-context.jsonld
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/examples/prometheus-query-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/examples/prometheus-query-range-example.json
🔗
Examples
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/examples/prometheus-targets-example.json
🔗
GraphQL
https://raw.githubusercontent.com/api-evangelist/prometheus-io/refs/heads/main/graphql/prometheus-io-graphql.md

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/prometheus-io-notifications-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.

GitHub Google LinkedIn

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

OpenAPI Specification

prometheus-io-notifications-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  version: 0.0.1
  title: Alertmanager admin Notifications API
  description: API of the Prometheus Alertmanager (https://github.com/prometheus/alertmanager)
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
servers:
- url: /api/v2/
tags:
- name: notifications
  description: Server notifications and events.
paths:
  /notifications:
    get:
      tags:
      - notifications
      summary: Get notifications
      operationId: get-notifications
      responses:
        '200':
          description: Notifications retrieved successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NotificationsOutputBody'
              examples:
                notifications:
                  summary: Server notifications
                  value:
                    data:
                    - active: true
                      date: '2026-01-02T16:14:50.046Z'
                      text: Configuration reload has failed.
                    status: success
        default:
          description: Error retrieving notifications.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                tsdbNotReady:
                  summary: TSDB not ready
                  value:
                    error: TSDB not ready
                    errorType: internal
                    status: error
components:
  schemas:
    Error:
      type: object
      properties:
        status:
          type: string
          enum:
          - success
          - error
          description: Response status.
          example: success
        errorType:
          type: string
          description: Type of error that occurred.
          example: bad_data
        error:
          type: string
          description: Human-readable error message.
          example: invalid parameter
      required:
      - status
      - errorType
      - error
      additionalProperties: false
      description: Error response.
    Notification:
      type: object
      properties:
        text:
          type: string
        date:
          type: string
          format: date-time
        active:
          type: boolean
      required:
      - text
      - date
      - active
      additionalProperties: false
      description: Server notification.
    NotificationsOutputBody:
      type: object
      properties:
        status:
          type: string
          enum:
          - success
          - error
          description: Response status.
          example: success
        data:
          type: array
          items:
            $ref: '#/components/schemas/Notification'
          example:
          - active: true
            date: '2023-07-21T20:00:00.000Z'
            text: Server is running
        warnings:
          type: array
          items:
            type: string
          description: Only set if there were warnings while executing the request. There will still be data in the data field.
        infos:
          type: array
          items:
            type: string
          description: Only set if there were info-level annotations while executing the request.
      required:
      - status
      - data
      additionalProperties: false
      description: Response body with an array of notifications.