Tether Health API

Server health and status checks

Operations 1

GET /api/v1/health Deep health check endpoint

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/tether-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 email required.

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

OpenAPI Specification

tether-health-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Tether Health API
  version: 1.0.0
  description: 'Operations tagged Health across 2 of this provider''s published API definitions: tether-health-api-openapi.yml, tether-wdk-indexer-openapi-original.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://wdk-api.tether.io
  description: Base URL declared by the provider in apis.yml (roadmap#122).
tags:
- name: Health
  description: Server health and status checks
paths:
  /api/v1/health:
    get:
      summary: Deep health check endpoint
      tags:
      - Health
      description: Checks Redis connectivity and blockchain indexer sync status. Returns HTTP 200 only when the overall status is `healthy`. Returns HTTP 503 for any non-healthy overall status (`degraded` or `unhealthy`), so readiness probes and load balancers can rely on the HTTP status code alone.
      responses:
        '200':
          description: Default Response
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                    - healthy
                    - degraded
                    - unhealthy
                    example: healthy
                  timestamp:
                    type: string
                    format: date-time
                  summary:
                    type: object
                    properties:
                      healthy:
                        type: integer
                        example: 10
                      unhealthy:
                        type: integer
                        example: 2
                      total:
                        type: integer
                        example: 12
                  checks:
                    type: object
                    properties:
                      redis:
                        type: object
                        properties:
                          status:
                            type: string
                            enum:
                            - healthy
                            - unhealthy
                            example: healthy
                      indexers:
                        type: object
                        additionalProperties:
                          type: object
                          properties:
                            status:
                              type: string
                              enum:
                              - healthy
                              - unhealthy
                              example: healthy
                            rpcLatencyMs:
                              type: number
                              example: 45
                            lag:
                              type: number
                              example: 3
                            db:
                              type: object
                              properties:
                                status:
                                  type: string
                                  enum:
                                  - healthy
                                  - unhealthy
                                  example: healthy
        '503':
          description: Default Response
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                    - healthy
                    - degraded
                    - unhealthy
                    example: healthy
                  timestamp:
                    type: string
                    format: date-time
                  summary:
                    type: object
                    properties:
                      healthy:
                        type: integer
                        example: 10
                      unhealthy:
                        type: integer
                        example: 2
                      total:
                        type: integer
                        example: 12
                  checks:
                    type: object
                    properties:
                      redis:
                        type: object
                        properties:
                          status:
                            type: string
                            enum:
                            - healthy
                            - unhealthy
                            example: healthy
                      indexers:
                        type: object
                        additionalProperties:
                          type: object
                          properties:
                            status:
                              type: string
                              enum:
                              - healthy
                              - unhealthy
                              example: healthy
                            rpcLatencyMs:
                              type: number
                              example: 45
                            lag:
                              type: number
                              example: 3
                            db:
                              type: object
                              properties:
                                status:
                                  type: string
                                  enum:
                                  - healthy
                                  - unhealthy
                                  example: healthy
    servers:
    - url: https://wdk-api.tether.io
      description: Base URL declared by the provider in apis.yml (roadmap#122).
components:
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-KEY
      description: API key obtained via the registration form. Include in the X-API-KEY header for all authenticated requests.
x-refined-from:
- tether-health-api-openapi.yml
- tether-wdk-indexer-openapi-original.yml