API reference
Every endpoint a Dew API token can call. To set up a service account and token, and for guides to common jobs, see Get started with the API.
Requests go to your Dew server, such as https://files.example.com, with a token in the Authorization: Bearer header. Every JSON response has success; successful ones carry data, failed ones error and a readable message.
| Area | What it covers |
|---|---|
| Files | Upload files, share them through links and download them. |
| Uploads | Resumable uploads in chunks, for large files and several files behind one link. |
| File requests | Ask people to send you files and download what they send. |
| Users | Users, invitations and desktop app sign-ins. Service account tokens only. |
| Groups | Groups, and who is on each domain’s access list. Service account tokens only. |
| Settings | Read domain, email, storage and single sign-on settings. Service account tokens only; changing settings is for people only. |
| Activity | What happens to files and file requests on the service account’s domains, on every plan. |
| Audit log | The full audit log, for a SIEM. Needs Enterprise. |
| Monitoring | Server health, system logs, access logs, license status and alerts. |
| Objects | The objects the API returns and accepts, field by field. |
The same reference is available as an OpenAPI file for Postman and code generators.
