Locked out of your installation by IP address

If your server's IP address has changed since you first registered, or you need to add new IPs to your integration, you will start receiving this error:

User credentials are incorrect. Incorrect API key or IP address.

This page explains why this happens and how to fix it.

---

Why this happens

When you register a device-server, the IP address you call from is whitelisted for that credential. Only requests from an ACTIVE whitelisted IP are accepted. If your server's IP has changed, or you need to add new IPs, you will be blocked until the new IPs are added to your credential's whitelist.

---

Option 1 — Add the new IP to your existing credential

If you can still make API calls from one of your currently whitelisted IPs, you can add new IPs directly using the credential IP management endpoint. No new installation or device-server is needed.

You will need your credential ID. You can retrieve it by listing your credentials:

▎ GET /v1/user/{userID}/credential-password-ip

Once you have it, add each new IP by posting to:

▎ POST /v1/user/{userID}/credential-password-ip/{credentialID}/ip

To deactivate an old IP you no longer use, update its status:

▎ PUT /v1/user/{userID}/credential-password-ip/{credentialID}/ip/{ipID}

Note: the IP address itself cannot be modified — only its status (ACTIVE or INACTIVE). To replace an IP, deactivate the old one and add the new one.

Reference : Whitelisting and Updating IP addresses

---

Option 2 — Fully locked out (can't call from any registered IP)

If you no longer have access from any of your registered IPs, you need to create a new credential using your existing qSEAL certificate and register a new device-server with the correct IPs.

This is the same process as registering a new certificate — your existing qSEAL certificate can be reused and bunq will automatically link the new credential to your existing TPP account. Follow the steps in Rotating your qSEAL Certificate.

▎ Note: The old device-server does not need to be deleted. Your new credential is entirely independent and its IP rules are not affected by the old device-server.

---