Skip to main content
GET
Health Check
Check API health status and comprehensive system status

Endpoints

WISTX provides three health and status endpoints:
  • GET /v1/health - Basic health check (simple status)
  • GET /v1/status - Comprehensive system status (all services)
  • GET /v1/status/uptime - Uptime statistics

Basic Health Check

GET /v1/health

Simple health check endpoint for quick status verification.

Response

Response Fields

string
required
Health status of the API. Returns "healthy" when the service is operational.

Get System Status

GET /v1/status

Comprehensive status check for all WISTX services including API, Database, Vector Search, Indexing, and Authentication.

Authorization

string
required
Bearer token for API authentication. Format: Bearer YOUR_API_KEY

Response

Response Fields

string
required
Overall system status. Possible values: operational, degraded, down
string
required
ISO 8601 timestamp of when the status check was performed
number
required
Duration of the status check in milliseconds
object
required
Status of individual services:
  • api - API service status
  • database - MongoDB database status
  • vector_search - Pinecone vector search status
  • indexing - Indexing service status
  • authentication - Authentication service status

Get Uptime Statistics

GET /v1/status/uptime

Get uptime statistics for WISTX services over a specified period.

Query Parameters

integer
Number of days to calculate uptime for. Range: 1-365. Default: 30

Authorization

string
required
Bearer token for API authentication. Format: Bearer YOUR_API_KEY

Response

Response Fields

integer
required
Number of days for uptime calculation
integer
required
Total number of status checks performed in the period
integer
required
Number of checks where status was operational
number
required
Uptime percentage calculated as (operational_checks / total_checks) * 100. Returns 0.0 if no historical data is available.
string
Informational message about uptime statistics. Present when no historical data is available or when there are issues retrieving statistics.
Historical Data Requirement: Uptime statistics require periodic status checks to be stored in the database. If no historical data exists, the endpoint will return total_checks: 0 and uptime_percentage: 0.0 with an explanatory message. For real-time status, use /v1/status instead.

Use Cases

  • Monitoring: Use /v1/status to monitor all WISTX services
  • Load Balancer Health Checks: Use /v1/health for simple health checks
  • Status Pages: Display comprehensive status using /v1/status
  • Uptime Tracking: Track service reliability using /v1/status/uptime
  • Alerting: Set up alerts based on status endpoint responses