API
API overview
Understand Retensis API surfaces, supported callers, and the complete route registry.
API surface types
| Type | Audience | Authentication |
|---|---|---|
| Product API | Retensis web and supported mobile clients | Supabase session cookie or supported bearer token |
| MCP | Compatible AI assistants | First-party OAuth bearer token |
| OAuth discovery and registration | MCP clients | Public metadata or client credentials |
| Webhooks | Stripe and RevenueCat | Provider signature |
| Operations | Vercel Cron and QStash | Cron, queue, or service authentication |
Not every route is a public developer API
The reference classifies internal and retired routes for completeness. Do not call internal product, cron, or webhook endpoints as an external integration contract.
Complete registry
The current application contains 102 API route modules. Use the searchable endpoint registry for method, path, access, status, and purpose.
Related documentation
API endpoint registry
All 102 API route modules, including product, OAuth, MCP, webhook, cron, and retired surfaces.
API authentication
Choose the correct Retensis authentication model for a product, mobile, MCP, webhook, or scheduled caller.
Errors, limits, and idempotency
Handle validation, authentication, plan, rate-limit, duplicate, and processing errors safely.