A Better Way to Authenticate with the Divio API


Cristina Saiu
Marketing
You asked for more control. We listened.
Until now, the Divio Platform gave each user a single API token for authenticating requests via the CLI and Public API. It worked, but let’s be honest: managing one token across multiple environments, projects, or machines was far from ideal.
That’s changing.
We’re rolling out support for multiple access tokens per user. You can now create and manage several tokens tied to your account, each with its own label, purpose, and optional expiration date.
Less Rework. More Control.
Instead of reconfiguring everything just because one token needed to be rotated, you can now:
Create separate tokens for local dev, CI pipelines, or shared environments
Set optional expiration dates to limit token lifetime
Revoke individual tokens without breaking other setups
Label tokens for clarity and organization

Designed with Agencies in Mind
As agencies grow and workflows evolve, so do their security and access needs. Sharing a single API token across environments or teams might work early on, but it can quickly become limiting when you're managing multiple clients, developers, or CI pipelines.
With multiple access tokens, you can create more structured and reliable setups by assigning tokens per project, team, or workflow. It’s easier to label, rotate, and revoke access without causing disruption elsewhere. For digital agencies juggling parallel projects and fast-moving timelines, this gives your team the flexibility and control to move faster, with less friction.
Get Started at Your Own Pace
You’ll find the new token system under your user menu in the top-left corner of the dashboard, in the Access Tokens section. From there, you can create, label, and manage tokens however your workflow needs.
Prefer the CLI? It’s all fully documented in our docs.
If you run into any friction or want to walk through the setup, we’re just a message away.
Want to test it out?
Start your free trial or log in to explore it now.