Create an API token
Create a personal API token for scripts and tools such as rclone, choose what it can access, and revoke it when you no longer need it.
An API token lets a script or a tool, such as rclone, access your Drime account without your password. You choose what each token can do, and you can revoke it at any time.
Personal tokens are for your own scripts, backups and tools, working on your own account. An app that other Drime users connect to their accounts uses OAuth instead, and must never ask for their password: see the Drime API documentation.
#Create a token
At the top right, click your avatar, then Settings.
Click Developers.
In API access tokens, click Create token.

In Token name, give the token a name you will recognise.
Use the tool or the computer that uses it, for example "rclone on my NAS". The name must be 3 to 100 characters long.
Under Permissions, choose what the token can do.
All: full access to all resources.
Read Only: read-only access to all resources.
Restricted: access only to the resources you pick, each set to No Access, Read or Write.
See Choose the right permissions.

Click Create.
Click Copy to copy the token, then click Done.
The button shows Copied! once the token is in your clipboard.

The token then appears in API access tokens, and works right away. It does not expire: it works until you delete it.
#Choose the right permissions
Give a token only what it needs.
Permission | What the token can do |
|---|---|
All | Everything your account can do through the API. |
Read Only | Read every resource listed below, but change nothing. |
Restricted | Only the resources you set to Read or Write. Everything left on No Access is refused. |
A Restricted token lists these resources: Files (including versions and trash), Folders, Sharing, Workspaces, Vault, Sign, Whiteboards, File requests, Send & Track, Contacts, Tags and Analytics. Analytics (storage usage) can only be read, so its choices are No Access and Access. Hover the help icon next to a resource to see what it covers.
Only an All token can reach your account, security and billing settings. Read Only and Restricted tokens never can.
A token's permissions cannot be changed after it is created. To change them, create a new token with the right permissions, update your tool, then delete the old token.
#Use the token
Send the token in the Authorization header of every request:
Authorization: Bearer YOUR_ACCESS_TOKENThe Documentation link next to API access tokens opens the Drime API documentation. To use a token with rclone, see Rclone, Drime CLI and WebDAV.
#See and delete your tokens
API access tokens lists the tokens you created and the ones the Drime apps create for themselves: Drime Desktop, Drime Mobile and the browser extension. Each row shows:
the token's name, or the app and its platform, for example Desktop app · Windows;
its permission, for example All access;
when it was last used, or Never used.
If you have none, the section shows You have no personal access tokens yet.
To revoke a token:
Click Delete token (the bin icon) at the end of its row.

Click Delete to confirm.
The dialog warns: This token will be deleted immediately and permanently. Once deleted, it can no longer be used to make API requests. Token deleted appears, and any tool using that token stops working at once.
You can also sign out the Drime apps from See and sign out your sessions and devices.
#If it doesn't work
What you see | What to do |
|---|---|
API access tokens is not in Developers | API access is not enabled for your account. Contact Drime support. |
You lost the token | It cannot be shown again. Delete it, then create a new one. |
Create shows an error under Token name | The name must be 3 to 100 characters long. |
| The token is missing, wrong or was deleted. Check the |
| The token is Read Only or Restricted and lacks that resource. Create a token with that resource set to Read or Write (the message names it), or with All. |
| This part of the API, such as account or billing settings, needs an All token. |
| Your account itself is not allowed to do this, whatever the token. |
#Next steps
Was this helpful?