Zipline Ai

Zipline Ai health API

The health API from Zipline Ai — 2 operation(s) for health.

GitHub OpenAPI

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/zipline-ai/refs/heads/main/openapi/zipline-ai-health-api-openapi.yml

OpenAPI Specification

zipline-ai-health-api-openapi.yml Raw ↑ 
openapi: 3.0.3
info:
  title: Zipline AI Fetcher fetch health API
  version: v1
  description: HTTP surface of the Chronon fetcher service that powers Zipline AI online feature serving and schema inspection. These endpoints read from the online KV store and metadata uploaded during deploy, and are intended for online GroupBys and Joins. This document was generated by the API Evangelist enrichment pipeline from the provider's published documentation (https://zipline.ai/docs/setup/Fetcher_API); the provider does not publish an OpenAPI definition. Fetcher runs self-hosted within the customer's cloud, so the server host is deployment-specific.
  x-generated-by: api-evangelist-enrichment
  x-generated-method: generated
  x-source: https://zipline.ai/docs/setup/Fetcher_API
servers:
- url: http://localhost:9000
  description: Local sandbox default (docker-compose)
- url: https://{host}
  description: Self-hosted deployment host
  variables:
    host:
      default: zipline.example.com
tags:
- name: health
paths:
  /ping:
    get:
      tags:
      - health
      operationId: ping
      summary: Health check endpoint
      responses:
        '200':
          description: Service is healthy
  /config:
    get:
      tags:
      - health
      operationId: getConfig
      summary: Fetcher service configuration
      responses:
        '200':
          description: Fetcher service configuration