GoodLeads Monitoring API

The monitoring API from GoodLeads — 3 operation(s) for monitoring.

GitHub OpenAPI

Operations 4

GET /api/v1/monitoring/alerts Monitoring Alerts #
GET /api/v1/monitoring/alerts/config List Alert Configs #
POST /api/v1/monitoring/alerts/config Upsert Alert Config #
GET /api/v1/monitoring/schedules Get Schedule Board #

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/goodleads-club:goodleads-club-monitoring-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

goodleads-club-monitoring-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Formation GTM Monitoring API
  description: GoodLeads Formation Data Platform — scored, enriched, campaign-ready leads.
  version: 0.1.0
tags:
- name: Monitoring
paths:
  /api/v1/monitoring/alerts:
    get:
      tags:
      - Monitoring
      summary: Monitoring Alerts
      description: 'Active threshold breaches and volume anomalies.


        Returns alerts where current metrics violate configured thresholds

        (e.g., phone fill below 45%) plus volume anomaly detection (>20% drop

        from 30-day baseline). Used by Anomaly Watch LIVE tile.'
      operationId: monitoring_alerts_api_v1_monitoring_alerts_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /api/v1/monitoring/alerts/config:
    get:
      tags:
      - Monitoring
      summary: List Alert Configs
      description: List all alert threshold configurations.
      operationId: list_alert_configs_api_v1_monitoring_alerts_config_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
    post:
      tags:
      - Monitoring
      summary: Upsert Alert Config
      description: Create or update an alert threshold configuration.
      operationId: upsert_alert_config_api_v1_monitoring_alerts_config_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AlertConfigRequest'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
      - APIKeyHeader: []
  /api/v1/monitoring/schedules:
    get:
      tags:
      - Monitoring
      summary: Get Schedule Board
      description: 'The Schedule Board''s data: every registered rule + the live drift check.


        Registry (the ledger Gib approves) always serves; the live EventBridge

        comparison is fail-soft — without AWS read access the board still shows

        the ledger, flagged `live_check: "unavailable"` instead of pretending.


        `overlap_issues()` (window-collision risk, 2026-09-03 PM finding) is a

        pure function of the registry alone — no AWS call — so it runs OUTSIDE

        the live-check try/except and is always present, even when

        `live_check: "unavailable"`.'
      operationId: get_schedule_board_api_v1_monitoring_schedules_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    AlertConfigRequest:
      properties:
        metric_name:
          type: string
          title: Metric Name
        threshold_value:
          type: number
          title: Threshold Value
        direction:
          type: string
          title: Direction
        state:
          anyOf:
          - type: string
          - type: 'null'
          title: State
      type: object
      required:
      - metric_name
      - threshold_value
      - direction
      title: AlertConfigRequest
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
  securitySchemes:
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key