API endpoints
OpsDash exposes a small set of HTTP routes for integrations, webhooks, and scheduled jobs. In-app CRUD uses Server Actions, not public REST for most entities.
Lead capture
POST /api/lead-capture — create a lead with an API key (Sales plate, feature platform:lead-capture-api). Headers: Authorization: Bearer {API_KEY} or X-Api-Key.
Online payments
POST /api/invoice-portal/[token]/checkout — start a Stripe Connect “Pay Now” checkout for a customer invoice from the public portal (gated by invoicing:payments, Full Loop plate). The connected-account payment lifecycle is synced back via POST /api/webhooks/stripe/connect.
Webhooks & cron
The main SaaS billing webhook is POST /api/webhooks/stripe; the Connect payout webhook is POST /api/webhooks/stripe/connect. OAuth callbacks, inbound email, and cron routes are documented in the repository under docs/reference/api-endpoints.md (full list, headers, and error shapes).