IBAN-Test API FAQ

What does an API request look like?

Use your API token as a Bearer token in the HTTP header.

Authorization: Bearer YOUR_API_TOKEN

Base URL:

https://www.iban-test.eu/api/IbanTest

Validate an IBAN:

GET /v2/iban/validate/{iban}

curl -H "Authorization: Bearer YOUR_API_TOKEN" \
  "https://www.iban-test.eu/api/IbanTest/v2/iban/validate/DE89%203704%200044%200532%200130%2000"

Validate a BIC:

GET /v2/bic/validate/{bic}

curl -H "Authorization: Bearer YOUR_API_TOKEN" \
  "https://www.iban-test.eu/api/IbanTest/v2/bic/validate/COBADEFFXXX"

Validate a bank account:

GET /v2/bank-account/validate?bankcode=37040044&accountnumber=532013000

Generate an IBAN:

GET /v2/iban/generate?countrycode=DE&bankcode=37040044&accountnumber=532013000

The complete technical reference with parameters, response fields and test functionality is available in the API documentation.

What does the API return?

All API endpoints return JSON. The result contains error, code, message and endpoint-specific details.

{
  "error": false,
  "code": 2100,
  "message": "IBAN is valid",
  "details": {}
}

Validation details can include bank information, BIC information, account validation results or generated IBAN data, depending on the endpoint and country.

For the current status codes, parameters and response schemas, see the API documentation.

Why is my API access locked or disabled?

This can happen when your available API quota has been reached, when an API token is invalid, or when suspicious or abusive usage is detected.

If you only reached your quota, you can wait for the next reset or upgrade to a package with a higher request volume.

If your access appears to be blocked for another reason, please contact support through the contact form.

Yes. The IBAN-Test API is designed for automated validation in forms, shops, SaaS products, SEPA mandates and back-office processes.

Typical use cases include validating bank details during checkout, registration, before a direct debit or before importing larger payment data sets.

This helps catch typos and invalid bank details early instead of discovering them through failed payments or returned direct debits.