Data store status

Monitor data store and runtime metrics

The data store status endpoint provides real-time information about the event data store, configuration, and runtime metrics.

Get data store status

Request

GET /api/admin/data-store/status

Authentication

This endpoint requires admin authentication. Include one of the following:

• x-admin-key header with your admin key
• Authorization: Bearer <token> header with a valid admin session token
• Valid admin session cookie

This endpoint accepts credentials via x-admin-key header or Authorization: Bearer header interchangeably.

Response

Returns current data store status, configuration, and runtime metrics.

success · boolean · required

Whether the request succeeded

timestamp · string · required

ISO 8601 timestamp of the status check

store · object · required

Local event store status information

store.provider · string

Storage provider type (e.g., “postgres”, “vercel”)

store.providerLocation · string

Location identifier for the storage provider

store.hasStoreData · boolean

Whether the store contains data

store.keyCount · number

Number of keys in the store

store.rowCount · number

Number of rows in the event data

store.updatedAt · string | null

Last update timestamp

store.updatedBy · string

Identity of the last updater

store.origin · string

Origin of the data (e.g., “manual”, “import”, “sync”)

config · object · required

Data configuration status

config.dataSource · string

Configured data source (e.g., “store”, “remote”)

config.remoteConfigured · boolean

Whether a remote data source is configured

runtime · object · required

Runtime data source status

runtime.dataSource · string

Currently active data source in runtime

runtime.eventCount · number

Number of events currently loaded in runtime

runtime.lastFetchTime · string | null

Timestamp of last data fetch attempt

runtime.lastRemoteErrorMessage · string | null

Error message from last remote fetch (if any)

metrics · object · required

Runtime performance metrics

metrics.requestCount · number

Total number of data requests

metrics.cacheHits · number

Number of cache hits

metrics.cacheMisses · number

Number of cache misses

metrics.averageResponseTime · number

Average response time in milliseconds

Example response

{
  "success": true,
  "timestamp": "2026-02-28T10:30:00.000Z",
  "store": {
    "provider": "postgres",
    "providerLocation": "us-east-1",
    "hasStoreData": true,
    "keyCount": 3,
    "rowCount": 148,
    "updatedAt": "2026-02-28T08:15:00.000Z",
    "updatedBy": "[e-mail]",
    "origin": "import"
  },
  "config": {
    "dataSource": "store",
    "remoteConfigured": false
  },
  "runtime": {
    "dataSource": "store",
    "eventCount": 148,
    "lastFetchTime": "2026-02-28T10:29:55.000Z",
    "lastRemoteErrorMessage": null
  },
  "metrics": {
    "requestCount": 1250,
    "cacheHits": 1100,
    "cacheMisses": 150,
    "averageResponseTime": 45.2
  }
}

Error responses

error · string

Error message describing what went wrong

401 Unauthorized

{
  "success": false,
  "error": "Unauthorized"
}

500 Internal Server Error

{
  "success": false,
  "error": "Failed to fetch store status"
}

Use cases

Monitoring data freshness

Use the store.updatedAt and runtime.lastFetchTime fields to monitor when data was last updated and fetched.

Detecting configuration issues

Compare config.dataSource with runtime.dataSource to ensure the runtime is using the expected data source. Check runtime.lastRemoteErrorMessage for remote data fetch issues.

Performance monitoring

Use the metrics object to track cache hit rates and response times. A low cache hit rate may indicate inefficient caching or high data volatility.

This endpoint provides a lighter-weight alternative to the /api/admin/health endpoint when you only need store and runtime status without detailed validation and count comparisons.