App resources
REST endpoints for every app in the Avura suite.
Every app in the platform is backed by the same /api/* REST surface and JSON conventions described above. These routes primarily power the Avura web client; an org-wide token (one without a domain pin) can call them too, subject to its read/write scope.
| Area | Base path |
|---|---|
/api/mail | |
| Calendar | /api/calendar/events, /api/calendar/booking-links |
| Chat | /api/chat/* |
| Drive | /api/drive |
| Docs | /api/docs |
| Sheets | /api/sheets |
| Slides | /api/slides |
| eSign | /api/esign/requests |
| Contacts | /api/contacts |
| Issues | /api/issues |
| Automation | /api/automation/* |
| Members & tokens | /api/members, /api/tokens |
These are not domain-pin-restricted, so only an org-wide token can reach them — domain-pinned tokens are limited to the Domains, DNS, and external-dns paths above, plus /api/tokens for delegating child tokens inside their own subtree (see API tokens).