Dashboard API
The endpoints the oprag web app calls with a signed-in Cognito session. Documented for completeness — an API key cannot reach them.
This is the oprag web app's own backend. It is documented because the API surface should not have blank regions and because it is useful to see what the product does with your data — not because it is an integration target. If you are building against oprag, the Integration API is your section.
How to get a token
Sign in to the dashboard through Cognito Hosted UI and read the access token from the session. OAuth & sign-in covers the flow, and Roles covers which role each endpoint needs — many are admin-only.
What a key needs a JWT for instead
- Reading or exporting leads
- Reading conversations
- Listing, uploading, or deleting documents
- Managing projects, keys, members, or billing
By resource
Resource grouping is kept inside this section: once you know these need a dashboard session, the useful next question is what they act on. Each page below is the complete reference for its resource, so four of them also carry the key-reachable endpoints that the Integration API collects — every endpoint states its own credential, and the count on each card is the JWT-only part.
company.Channels · 6 JWTWhere chat is exposed: the embeddable widget, its public configuration, and WhatsApp.Integrations · 12 JWTOutbound webhooks, the Slack bot and its channel mappings, and document-source connectors.| Page | Needs a JWT | Reachable with a key |
|---|---|---|
| Chat | 2 | 4 — see them |
| Documents | 16 | None |
| Projects | 13 | None |
| Keys | 5 | None |
| Conversations | 6 | 1 — see them |
| Leads & tickets | 5 | 2 — see them |
| Workspace | 17 | 1 — see them |
| Channels | 6 | 4 — see them |
| Integrations | 12 | 1 — see them |
| Platform | 0 | 3 — see them |
| OAuth & sign-in | 0 | 4 — see them |
Ready to ship?
Get started free