Health Check API

​

Check Service Health

GET /api/v1/health/services

​

Response

{
  "postgres": {"status": "up", "message": "Connected"},
  "mongodb": {"status": "up", "message": "Connected"},
  "minio": {"status": "up", "message": "Connected"},
  "activemq": {"status": "up", "message": "Connected"},
  "kafka": {"status": "up", "message": "Connected"},
  "qdrant": {"status": "not_configured"},
  "weaviate": {"status": "not_configured"},
  "milvus": {"status": "not_configured"},
  "chroma": {"status": "not_configured"},
  "pgvector": {"status": "not_configured"}
}

​

Status Values

​

Services Checked

• postgres — PostgreSQL database
• mongodb — MongoDB database
• minio — MinIO object store
• activemq — ActiveMQ message queue
• kafka — Apache Kafka

• qdrant — Qdrant vector database
• weaviate — Weaviate vector database
• milvus — Milvus vector database
• chroma — Chroma vector database
• pgvector — PostgreSQL with pgvector extension

​

Example

curl http://localhost:8080/api/v1/health/services

​

List Available Destinations

GET /api/v1/destinations/available

• Self-hosted destinations (mongodb, postgres, objectstore) are live-probed — a destination is listed only if the service is actually reachable. The presence of a Vault secret alone is not enough, because the compose stack seeds secrets even when a service is disabled.
• External SaaS destinations (snowflake, databricks) have no local service to probe, so they are listed when any Platform secret contains a complete set of credentials for that destination. Credential secret names are user-chosen per pipeline, so every Platform secret is scanned rather than a fixed name looked up.

​

Response

["mongodb", "postgres", "objectstore", "snowflake"]

​

Example

curl http://localhost:8080/api/v1/destinations/available

​

List Available Vector Stores

GET /api/v1/vector-stores/available

​

Response

["pgvector", "qdrant"]

​

Example

curl http://localhost:8080/api/v1/vector-stores/available