Pomo

Pomo Health API

The Health API from Pomo — 8 operation(s) for health.

Documentation GitHub OpenAPI

Operations 8

GET /health/live Liveness Check #

GET /health/ready Readiness Check #

GET /health Health Check #

GET /health/detailed Detailed Health Check #

GET /health/database Database Health Check #

GET /health/events Check Event System Health #

GET /health/events/redis Check Redis Health #

GET /health/events/sse Check Sse Health #

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/pomo-health-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

openapi: 3.2.0
info:
  title: GPT Backend Health API
  version: 0.1.0
servers:
- url: https://api.usepomo.ai
  description: Base URL declared by the provider in apis.yml (roadmap#122).
tags:
- name: Health
paths:
  /health/live:
    get:
      summary: Liveness Check
      description: 'Kubernetes liveness probe - is the process alive?


        This should always succeed if the process is running.

        Failing this causes container restart.'
      operationId: liveness_check_health_live_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Health
  /health/ready:
    get:
      summary: Readiness Check
      description: 'Kubernetes readiness probe - can the app accept traffic?


        Checks database connectivity and auth configuration. Failing

        this removes the pod from the service load balancer.'
      operationId: readiness_check_health_ready_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Health
  /health:
    get:
      summary: Health Check
      description: 'Standard health check for load balancers.


        Quick check that the app can respond and database is accessible.

        Includes database latency and pool utilization.'
      operationId: health_check_health_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Health
  /health/detailed:
    get:
      summary: Detailed Health Check
      description: 'Detailed health check for debugging and monitoring.


        Comprehensive check of all system components:

        - Database connectivity and latency

        - Connection pool status

        - Critical tables existence

        - Redis connectivity and latency'
      operationId: detailed_health_check_health_detailed_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      security:
      - HTTPBearer: []
      tags:
      - Health
  /health/database:
    get:
      summary: Database Health Check
      description: 'Database-specific health check.


        Provides detailed information about the database status,

        including connection pool statistics and configuration.'
      operationId: database_health_check_health_database_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      security:
      - HTTPBearer: []
      tags:
      - Health
  /health/events:
    get:
      summary: Check Event System Health
      description: Check health of the event system
      operationId: check_event_system_health_health_events_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Health
  /health/events/redis:
    get:
      summary: Check Redis Health
      description: Check Redis connectivity
      operationId: check_redis_health_health_events_redis_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Health
  /health/events/sse:
    get:
      summary: Check Sse Health
      description: Check SSE connections
      operationId: check_sse_health_health_events_sse_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Health
components:
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer