API reference

Canonical Orinel API routes for analysis, reports, and client delivery exports. Legacy Prisma-era report PDF routes return 501 — use the Orinel paths below.

Authentication

Browser requests use the Supabase session cookie after login. For programmatic access, create an API key in Settings → API keys and send Authorization: Bearer <key> or X-API-Key: <key>.

Analysis & reports (canonical)

• POST /api/orinel/analyze — Run full analysis pipeline (upload handoff, execution layer, delivery package). Primary integration for new reports.
• POST /api/orinel/report-pdf — Fetch slimmed report payload for client-side PDF render (includes delivery package section). Requires session + report ownership.
• POST /api/orinel/export/excel — Export client delivery workbook (xlsx, json, csv_pack). Body: { format, deliveryPackage }.
• POST /api/orinel/presentation/export — Deck export (pptx_native, copy_outline, pptx_json).
• POST /api/orinel/web-import/preview / POST /api/orinel/web-import/analyze — Public website table/CSV/JSON import only.

Data ingest & connectors

• POST /api/ingest/upload — Upload CSV (multipart: file, name?, project_id?).
• POST /api/connectors/create — Create SQL connector (Postgres, MySQL, SQL Server, public Sheets when configured).
• GET /api/connectors — List connectors. Snowflake / BigQuery registry entries are preview/metadata only until live drivers ship.

Legacy / workspace APIs

• GET /api/projects, GET /api/reports — List workspace objects.
• GET /api/health — Health check (no auth).
• GET /api/compliance/audit-export — Audit export (header X-Compliance-Key).

Enterprise demo script: /enterprise-demo. Base URL: your deployment origin (e.g. https://orinel.app). See Security for compliance handling.