Use your own files from scripts

A personal token lets your own scripts use your files and file requests, for example a backup job that uploads a nightly export and emails you the link. It reaches only what you own and can’t do anything admin-related.

Create a personal token

1. In Dew, open My account and find API tokens.
2. Click New token. In New API token, enter a Name and choose its Permissions: the files and file requests permissions you need.
3. Choose when it Expires, up to a year from today.
4. Click Create token and copy the token, which starts with dewpt_. Dew shows it only once.

If your admin turned personal tokens off, API tokens says “Your administrator has turned off personal API tokens.” and there’s no New token button.

Use it

Personal tokens use the same requests as service account tokens, with your files instead of the service account’s:

curl -X PUT -H "Authorization: Bearer dewpt_<token>" --data-binary @export.csv https://files.example.com/api/file/export.csv

The send files and collect files guides work the same way, except for the activity feed, which needs a service account.

Check it worked

The file is on your My links page in Dew, and under API tokens in My account the token shows when it was last used instead of “Never used”.

When it stops working

• At its expiry date. Create a new one before then.
• When you change or reset your password, or an admin signs you out everywhere or deactivates you: Dew ends your personal tokens with your sign-ins.
• When your admin turns personal tokens off. Your tokens work again if they turn them back on.

Admins see every personal token on the Personal API tokens tab in System → Integrations and can revoke them.

If something doesn’t work

What you see	What to do
401 with “This API token has expired.”	Create a new token.
401 with “Invalid or missing credentials”	The token is wrong or was ended. Create a new one.
401 with “Personal API tokens are turned off on this server.”	Ask your admin to turn on Personal API tokens in Settings → General settings → Users & Access.
403 with “This API token doesn’t have permission for this action.”	Create a token with the permission the call needs.
403 with “This API token doesn’t have permission for this action.” or “Personal API tokens can’t be used for admin actions.” on a call under /api/admin/	Admin calls need a service account. Ask your admin.