---
title: Validate IBAN API
slug: validate-iban
url: https://apyhub.com/apyhub/service/validate-iban
provider: ApyHub
categories: [Verification Kit]
tags: [bank-account, iban, bank-account-validation, account-number, payment-validation]
auth: api_key
version: 1.0.0
service_type: sync
endpoints: 1
atoms: 5
mcp: true
alias: finance-validator-iban
---

# Validate IBAN API

Validate an IBAN and get back the country, BBAN and printable format in one call. Covers every SEPA country. Free tier, no credit card needed.

## Endpoints

| Method | URL | Description | Atoms |
| --- | --- | --- | --- |
| POST | `https://api.eu.apyhub.com/apyhub/validate-iban` | What it does Validates an IBAN submitted in the request body and returns a JSON object under data.… | 5 |

## Endpoint reference

### Validate an IBAN

`POST https://api.eu.apyhub.com/apyhub/validate-iban` · 5 atoms · accepts `application/json` · returns `application/json`

| Parameter | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `iban` | body | string | yes | The IBAN to validate. Example: `FR7630006000011234567890189`. |

#### Quickstart

Validate an IBAN by sending it in a simple JSON body.

```bash
curl -X POST "https://api.eu.apyhub.com/apyhub/validate-iban" \
  -H "apy-token: $APY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"iban":"FR7630006000011234567890189"}'
```

#### What you'll get back

Returns a JSON object with a `data` field. `data` can be either an object with IBAN details and a `valid` flag, or a boolean `false` when the IBAN is invalid.

```json
{
  "data": {
    "bban": "30006000011234567890189",
    "iban": "FR7630006000011234567890189",
    "valid": true,
    "country_code": "FR",
    "sepa_country": true,
    "printable_format": "FR76 3000 6000 0112 3456 7890 189"
  }
}
```

## About

## What it does

The IBAN Validation API checks whether an IBAN is real and gives you back its parts. Send the IBAN, get back the country code, the BBAN, whether it belongs to a SEPA country, and a printable format for showing back to the user.

Validation runs two checks. The structure has to match the format that country uses, and the check digits have to pass the mod-97 calculation. Together they catch typos, transposed characters and made-up numbers before a payment leaves your system.

Use it on payment forms, supplier onboarding, payout setup and back-office cleanup of stored bank details. A failed transfer costs a fee and a support ticket. A rejected form field costs nothing.

The `sepa_country` flag tells you which payment rules apply, so you can branch between SEPA and international transfer logic in the same code path.

One limitation worth stating plainly: a valid IBAN is a well-formed IBAN. It does not confirm the account is open, or that it belongs to the person who typed it. For that, use the [Advanced IBAN Validation API](https://apyhub.com/quadlem/service/iban-validation) from Quadlem. For SWIFT and BIC codes, use the [Validate SWIFT/BIC API](https://apyhub.com/apyhub/service/validate-swift-bic-code).

## Usage

Base URL: `https://api.eu.apyhub.com` (default region — see
`GET https://apyhub.com/api/public/regions` for the rest).

Authenticate with an ApyHub API key in the `apy-token` header.
Full docs and a live playground: https://apyhub.com/apyhub/service/validate-iban
