Set up Openprovider API access

Set up a dedicated Openprovider user so InfraNest can connect — for anyone who manages domains through Openprovider and wants to use InfraNest's Domains or DNS features with them.

Overview

• Openprovider doesn't issue API keys. Instead, InfraNest signs in as one of your Openprovider users, so what you're setting up here is a user, not a key.
• Four things have to be true before that user can connect. Openprovider reports three of them with the exact same error it uses for a wrong password — so if you skip one, you'll see "Authentication/Authorization Failed" and waste time retyping a password that was never the problem.
• Work through each section below in order, then connect the account.

Make a separate user for InfraNest

Don't use your own login for this. Two reasons:

• If someone leaves, or you rotate your own password, you can change that without breaking the connection.
• Your own account almost certainly has two-factor authentication on it, and a user with 2FA cannot use the API at all. Openprovider made 2FA mandatory for control-panel access in October 2025, so this is normal, not unusual.

1. In the Openprovider control panel, go to Account.
2. Add a new user for InfraNest.
3. Give it a password you haven't used anywhere else — you'll paste it into InfraNest, so it's worth being a value that does nothing else.

Switch API access on for that user

New users can't use the API until you allow it, and this setting is per user — turning it on for your own account does not turn it on for the new one.

1. Go to Account → Account Overview.
2. Find the user you just created and check the API access indicator. Green means on, red means off.
3. If it's red, select the username, choose Edit, tick API access Enabled, and select Update contact.

Do not set up 2FA on this user

Leave two-factor authentication off for the InfraNest user. A user with 2FA can sign in to the control panel but cannot obtain an API token — and the error you get says nothing about 2FA, so it's easy to miss.

WarningYour own account keeps its 2FA. This step applies only to the user you made for the API — don't remove 2FA from your main account.

Allow our IP address

Openprovider can restrict API access to particular addresses, and InfraNest connects from a fixed one.

1. Open the same user's settings and find the API white list.
2. Add the IP address InfraNest shows you on the connect screen.

Openprovider keeps this list per user and per access level, so you can allow our address for the API while your own control-panel logins stay restricted to your office.

NoteIf the whitelist is blocking us, Openprovider returns a different error — "Access denied" rather than "Authentication/Authorization Failed" — and InfraNest will tell you it's the IP address rather than the password.

Connect the account

1. Go back to InfraNest.
2. Open Integrations.
3. Select Openprovider.
4. Enter the username and password of the user you made.
5. Select Connect.

Troubleshooting

If it still won't connect, work through these in order — they're the four causes, most common first:

1. API access is off for that user. The most common cause, because it's off by default.
2. 2FA is set up on that user. Remove it, or make a user that never had it.
3. Our IP address is not on the whitelist. Openprovider's own advice is to clear the whitelist entirely until the connection works, then add addresses back.
4. The password is wrong. Genuinely the least likely of the four.