Skip to main content

API Overview

Right Events does not expose one single public REST API. Instead, the codebase contains several HTTP-facing surfaces with different purposes.

1. Next.js API routes​

These are defined under app/api/* and are the main HTTP endpoints exposed by the web app.

Important groups include:

  • app/api/health
  • app/api/ai/*
  • app/api/email/*
  • app/api/orders/*
  • app/api/payments/*
  • app/api/qr
  • app/api/wallet/*
  • app/api/webhooks/*
  • app/api/mobile/backend/*

2. Convex HTTP routes​

Defined in convex/http.ts, these include:

  • /health
  • /dp-hub/cron/refresh-trending
  • /dp-hub/cron/cleanup-expired-generated
  • /dp-campaign/cron/sync-phase-templates
  • /railway/deployments/ingest

These are operational or backend-facing routes rather than general public product APIs.

3. FastAPI backend​

The support backend in backend/server.py exposes routes used behind the mobile gateway and for selected backend integrations.

4. Mobile gateway contract​

For external mobile clients, the preferred surface is the gateway:

  • GET /api/mobile/backend/health
  • GET /api/mobile/backend/openapi
  • ANY /api/mobile/backend/{backend-path}

Current recommendation​

  • For web product features, keep using Convex calls from the frontend.
  • For external mobile consumers, use the mobile gateway.
  • For infrastructure hooks such as deploy ingest or cron-like maintenance, use Convex HTTP routes.