Cronitor P API

The P API from Cronitor — 1 operation(s) for p.

Operations 3

GET /p/{apiKey}/{monitorKey} Send a telemetry event (GET) #
POST /p/{apiKey}/{monitorKey} Send a telemetry event (POST) #
HEAD /p/{apiKey}/{monitorKey} Send a telemetry event (HEAD) #

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/cronitor-p-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

cronitor-p-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Cronitor Telemetry P API
  description: The Telemetry API is the core integration mechanism for recording job execution events (run, complete, fail, ok) to Cronitor monitors. Events are sent via GET, POST, or HEAD requests to the cronitor.link domain with the API key embedded in the URL path, enabling lightweight pings from any environment. Supports email integration and rate-limited event delivery.
  version: v1
  contact:
    name: Cronitor Support
    url: https://cronitor.io/docs/telemetry-api
  license:
    name: Proprietary
    url: https://cronitor.io
servers:
- url: https://cronitor.link
  description: Cronitor Telemetry server
tags:
- name: P
paths:
  /p/{apiKey}/{monitorKey}:
    parameters:
    - name: apiKey
      in: path
      required: true
      schema:
        type: string
      description: Cronitor API key with monitor:telemetry permission.
    - name: monitorKey
      in: path
      required: true
      schema:
        type: string
      description: Unique monitor key to send the event to.
    get:
      operationId: sendTelemetryEventGet
      summary: Send a telemetry event (GET)
      description: Records a job execution event. Use query parameters to specify the state and optional metadata.
      parameters:
      - name: state
        in: query
        required: true
        schema:
          type: string
          enum:
          - run
          - complete
          - fail
          - ok
        description: Job execution state.
      - name: env
        in: query
        schema:
          type: string
        description: Environment identifier (e.g. staging, production).
      - name: host
        in: query
        schema:
          type: string
        description: Server hostname.
      - name: message
        in: query
        schema:
          type: string
          maxLength: 2000
        description: URL-encoded status message.
      - name: metric
        in: query
        schema:
          type: string
        description: Metric value in format count:N, duration:N (seconds), or error_count:N.
        example: duration:45.2
      - name: series
        in: query
        schema:
          type: string
        description: Unique ID for correlating related events.
      - name: status_code
        in: query
        schema:
          type: integer
        description: Job exit code.
      responses:
        '200':
          description: Event recorded.
        '429':
          description: Rate limit exceeded. Per-endpoint limit is 5 req/s (burst 10); per-IP limit is 50 req/s (burst 250).
      tags:
      - P
    post:
      operationId: sendTelemetryEventPost
      summary: Send a telemetry event (POST)
      description: Records a job execution event via POST. The request body is discarded; use query parameters for all event data.
      parameters:
      - name: state
        in: query
        required: true
        schema:
          type: string
          enum:
          - run
          - complete
          - fail
          - ok
      - name: env
        in: query
        schema:
          type: string
      - name: host
        in: query
        schema:
          type: string
      - name: message
        in: query
        schema:
          type: string
          maxLength: 2000
      - name: metric
        in: query
        schema:
          type: string
      - name: series
        in: query
        schema:
          type: string
      - name: status_code
        in: query
        schema:
          type: integer
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              description: Body is accepted but discarded.
      responses:
        '200':
          description: Event recorded.
        '429':
          description: Rate limit exceeded.
      tags:
      - P
    head:
      operationId: sendTelemetryEventHead
      summary: Send a telemetry event (HEAD)
      description: Records a job execution event via HEAD request. Useful for minimal- overhead pings.
      parameters:
      - name: state
        in: query
        required: true
        schema:
          type: string
          enum:
          - run
          - complete
          - fail
          - ok
      - name: env
        in: query
        schema:
          type: string
      - name: message
        in: query
        schema:
          type: string
          maxLength: 2000
      - name: metric
        in: query
        schema:
          type: string
      - name: series
        in: query
        schema:
          type: string
      - name: status_code
        in: query
        schema:
          type: integer
      responses:
        '200':
          description: Event recorded.
        '429':
          description: Rate limit exceeded.
      tags:
      - P