Documentation Index
Fetch the complete documentation index at: https://mintlify.com/KingPsychopath/oooc-fete-finder/llms.txt
Use this file to discover all available pages before exploring further.
The health endpoint provides a comprehensive health check of the system, including data store connectivity, event counts, and configuration status.
Get system health status
Authentication
This endpoint requires admin authentication. Include one of the following:
x-admin-key header with your admin keyAuthorization: Bearer <token> header with a valid admin session token- Valid admin session cookie
Response
Returns comprehensive system health information including connectivity status, data counts, and warnings.
Whether the health check succeeded
ISO 8601 timestamp of the health check
Database and store connectivity statusconnectivity.postgresConfigured
Whether Postgres is configured
connectivity.postgresTable
Name of the Postgres KV store table
connectivity.postgresReachable
Whether Postgres is reachable
connectivity.eventStoreReachable
Whether the event store is reachable
connectivity.storeProvider
The active store provider (e.g., “postgres”, “vercel”)
connectivity.storeProviderLocation
Location identifier for the store provider
Data source configuration and modeConfigured data source mode
Currently active data source
Whether remote data source is configured
Event count metrics across different layersRow count from store metadata
Raw row count from CSV (excluding header)
Number of successfully parsed events
Current event count in runtime
Alias for liveRuntimeEvents
Data store status and metadataWhether the store contains data
Number of keys in the store
Identity of the last updater
Origin of the data (e.g., “manual”, “import”)
store.postgresEventTables
Postgres event table statisticsstore.postgresEventTables.rowCount
Number of rows in event tables
store.postgresEventTables.columnCount
Number of columns in event tables
store.postgresEventTables.meta
Event table metadata including updatedAt, updatedBy, origin, and checksum
Data validation warnings and mismatchesWarnings encountered during CSV parsing
Descriptions of count discrepancies between data layers
Runtime status informationLast time runtime data was checked
Last error message from remote data fetch (if any)
Example response
{
"success": true,
"timestamp": "2026-02-28T10:30:00.000Z",
"connectivity": {
"postgresConfigured": true,
"postgresTable": "app_kv_store",
"postgresReachable": true,
"eventStoreReachable": true,
"storeProvider": "postgres",
"storeProviderLocation": "us-east-1"
},
"mode": {
"configuredDataMode": "store",
"liveDataSource": "store",
"remoteConfigured": false
},
"counts": {
"storeMetadataRows": 150,
"csvRawRows": 150,
"parsedEvents": 148,
"liveRuntimeEvents": 148,
"liveEvents": 148
},
"store": {
"hasStoreData": true,
"keyCount": 3,
"updatedAt": "2026-02-28T08:15:00.000Z",
"updatedBy": "admin@example.com",
"origin": "import",
"postgresEventTables": {
"rowCount": 150,
"columnCount": 25,
"meta": {
"rowCount": 150,
"updatedAt": "2026-02-28T08:15:00.000Z",
"updatedBy": "admin@example.com",
"origin": "import",
"checksum": "abc123..."
}
}
},
"warnings": {
"parsingWarnings": [],
"countMismatches": [
"Parsed event count (148) differs from raw CSV rows (150); this usually means rows were filtered/invalid during parsing"
]
},
"runtime": {
"lastCheckTime": "2026-02-28T10:29:55.000Z",
"lastErrorMessage": null
}
}
Error responses
Error message describing what went wrong
{
"success": false,
"error": "Unauthorized"
}
{
"success": false,
"error": "Database connection failed"
}
This endpoint performs extensive validation and comparison of event counts across multiple data layers. Count mismatches are expected during data transitions and are reported in the warnings section rather than causing failures.