Access tokens for your devices
November 19, 2026
Create a token with limited rights and use it as the password in your router or script.
Devices do not sign in with your account. They use an access token: a long secret that starts with thdns_. If a token ever leaks, you revoke just that token and nothing else changes.
Create a token
- Open the dashboard and go to the tokens.
- Give the token a name you will recognise, for example the name of the router.
- Choose the permission (see the table below).
- Choose which hostnames the token may use: all of your hostnames or only some.
- Optionally set an expiry date. Then create the token.
- Copy the token now. It is shown only once; afterwards only its first characters are visible.
| Permission | What the token can do |
|---|---|
| UPDATE | Update the IP address of its hostnames. Right for routers and scripts. |
| RECORDS | Update the IP address and manage the other records of its hostnames. |
| READ | Read only. It cannot change anything and cannot be used for IP updates. |
Use the token
In routers and tools, the token goes into the Password field. The Username field can hold any text; we suggest your hostname. In scripts you can also send the token as a Bearer header:
curl -fsS -H "Authorization: Bearer thdns_xxxxxxxx" "https://api.shiftdns.thunderhosting.com/nic/update?hostname=your-hostname"Treat a token like a password. Do not put it into links or share it. Use one token per device, so you can revoke a single device. An account can hold a limited number of tokens (20 for a free account).