We are building an OAC-powered analytics copilot that answers natural-language business questions with governed data.
Today, bearer-token calls can discover workbooks, but full server-to-server flow is blocked by missing supported APIs for data execution and lineage metadata.
UI endpoints (for example /ui/dv/ui/api/...) require session + CSRF, so they are not viable for backend OAuth integrations.
Workbook profile responses often return only basic metadata (id/name/path), without datasets, subject areas, or fields needed for query planning.
Export APIs are useful for PDF/PNG rendering, but not for structured row/column results and aggregations.
We need documented OAuth bearer-compatible REST endpoints for: query execution, async poll, workbook lineage (datasets/subject areas/fields), and machine-readable visual/query metadata.
These endpoints should be stable, versioned, and include clear error handling, limits/pagination, and audit-friendly response metadata.
This would unlock secure, governed enterprise copilots on OAC without brittle UI-dependent workarounds.
