Scoped API Keys
If you manage DNS zones for several customers through our DNS API, you previously only had a single API key per account, valid for every zone at once. That became awkward as soon as a key needed to be handed to one specific customer, for example for automatic Let’s Encrypt certificate renewal via DNS-01. From now on you can keep these cleanly separated.
In the client area under Account > Update Account Details, next to the existing API key, you will now find the Manage API Keys button. Use it to create as many additional keys as you like, each limited to the domains you select.
Setting up a scoped key
Open your account details in the client area and click Manage API Keys next to the API key field. Give it a label, select one or more domains, and decide whether the key should only be used for automatic certificate renewal or should also allow full DNS management of those domains. The generated key is shown once, note it down right away.
New client area interface: select domains and create a restricted key on the spot
Who benefits most
This is especially useful for service providers managing domains on behalf of their own customers: instead of handing out the full account key, each customer gets a key limited to their own domain. It also helps limit the blast radius of automated DNS-01 certificate renewal (for example with win-acme or acme.sh) to exactly the domain it needs.
You can find more on the DNS API itself in our DNS API knowledge base article.
New client area interface: select domains and create a restricted key on the spot