Webhooks and Integrations
Payment webhooks
The Next.js app currently exposes webhook handlers for:
/api/webhooks/paystack/api/webhooks/flutterwave/api/webhooks/stripe/api/webhooks/zavu
These handlers are responsible for reconciling provider callbacks into internal business logic.
Railway deployment ingest
Convex exposes /railway/deployments/ingest to persist deploy metadata into release history.
Authentication is enforced with DEPLOYMENT_INGEST_TOKEN.
DP maintenance routes
Protected maintenance routes in convex/http.ts include:
/dp-hub/cron/refresh-trending/dp-hub/cron/cleanup-expired-generated/dp-campaign/cron/sync-phase-templates
Authentication is enforced with DP_HUB_CRON_TOKEN.
Health endpoints
- Next.js health:
/api/health - Convex health:
/health - Mobile gateway health:
/api/mobile/backend/health - Optional backend health:
/healthonBACKEND_URL
Integration guidance
- Use Next.js routes for provider-facing webhooks.
- Use Convex HTTP routes for internal or platform-ops callbacks.
- Use the mobile gateway for controlled external client access to backend routes.