Skip to main content
FlowGuard exposes indexer visibility through backend admin routes. These are operator-facing diagnostics, not end-user product endpoints.

​
Current Production Endpoints

GET /api/admin/indexer/status
GET /api/admin/indexer/errors
POST /api/admin/indexer/resync
These routes provide health, sync, and resync controls for the running backend instance.

​
Separate Indexer Service

A separate service scaffold exists in backend/indexer/. Treat it as self-hosted infrastructure work rather than a required part of the standard FlowGuard app deployment. What is true today:
  • Core app flows (/api/streams, /api/payments, /api/airdrops, etc.) operate from the main backend database.
  • Admin indexer status routes are available from the main backend.
  • The standalone indexer package exists, but normal product usage does not depend on it.
  • Use /api/admin/indexer/status for operational monitoring.
  • Treat the standalone indexer as deployment-specific engineering work until your team validates it in your own environment.

​
Environment Notes

For local experimentation with indexer components, you will typically configure:
  • BCH_NETWORK
  • DATABASE_URL (for Postgres-backed indexer experiments)
Keep these separate from the default SQLite-backed backend setup unless you are intentionally running a multi-service architecture.