TR Try tools
← Validation

IBAN Validation

Validates an IBAN from any of 70+ countries: checksum, country length and in-country account structure, and resolves the bank and branch codes.

POST /v1/iban/validate · 1 credit · deterministic

  • No account needed to try any endpoint on this page.
  • Deterministic endpoints answer from cache in single-digit milliseconds.
  • Every response carries a receipt: credits charged, cache status, duration.

Free try on this page → when you need a key, Proceed to pay · API access.

POST/v1/iban/validate
Request
{
  "iban": "DE89 3704 0044 0532 0130 00"
}
no request sent yet
Response
Press Run to try free — no key needed.
1endpoints
data points banked
time series
median response

Why this exists

Built for hostile input

A Turkish address arrives as "Cd." or "Cad." or "Caddesi", with the flat number glued to the building number. Generic parsers drop half of it silently. This one tells you what it could not place.

Every number carries its provenance

Each archived point stores the source URL and a content hash of the page it came from, and the archive is committed to a Merkle root anchored in Bitcoin. Every commitment — with its cutoff, leaf count and anchors — is published at /proof, so you can check for yourself how current the latest one is. The bulletins themselves are public and anyone can read them; what this adds is that a number you quote can be shown to be the number we held on that date, and that it has not been edited since.

You only pay for work

Repeated inputs come from cache and cost zero credits. If a response ever fails its own schema, the call is refunded automatically.

Endpointsexpand any row to see the parameters and call it live

Validation1

/v1/iban/validate IBAN Validation deterministic 1 credit

Validates an IBAN from any of 70+ countries: checksum, country length and in-country account structure, and resolves the bank and branch codes.

Most free libraries stop at the mod-97 checksum. That only says the digits are self-consistent — not that the number could exist in that country. This checks the country's BBAN structure too, so a wrong-length or wrong-shaped account is rejected before your payment file reaches the bank. When only the two check digits are wrong, the correct ones are computed and returned as a suggestion, because that is what people actually mistype. Turkish, Dutch and Belgian IBANs additionally resolve to a bank name when the national code is in our table; otherwise bankName is null. This is not a SWIFT directory.

Parameters

iban* string IBAN, with or without spaces.
expectCountry string Expected country code (ISO 3166-1 alpha-2).
POST/v1/iban/validate
Request
{
  "iban": "DE89 3704 0044 0532 0130 00"
}
no request sent yet
Response
Press Run to try free — no key needed.

Pricingone key covers every endpoint

Free try on this page → when you need a key, Proceed to pay · API access.

Credits are consumed per call and cache hits are free. Requests without a key run on a narrow per-IP demo quota so you can evaluate before signing up.

The API key is e-mailed the moment payment clears. Upgrades keep the same key, so your integration is never broken.

Want to finish the integration before paying?

Use it from an AI assistantthe same catalogue, exposed as MCP tools

Every endpoint is also published over the Model Context Protocol, so Claude, ChatGPT or your own agent can call it directly — no glue code, no wrapper functions. The assistant sees the same input schemas and the same metering.

Currently 68 tools. New endpoints appear automatically; nothing to update on your side.

claude_desktop_config.json

{
  "mcpServers": {
    "temsor": {
      "url": "https://api.temsor.com/mcp",
      "headers": { "x-api-key": "fk_live_…" }
    }
  }
}

Quickstart

Official client: npm install temsor-api · npmjs.com/package/temsor-api

Node.js

import Client from "temsor-api";

const api = new Client({ apiKey: KEY });
const r = await api.${(() => {
  const first = apis[0];
  return first.slug.split(/[/-]/).map((p, i) => (i === 0 ? p : p[0].toUpperCase() + p.slice(1))).join('');
})()}(${esc(JSON.stringify(apis[0].examples[0]?.input ?? {}))});
console.log(r, r.$meta);

cURL

curl -s https://api.temsor.com/v1/iban/validate \
  -H "content-type: application/json" \
  -H "x-api-key: fk_live_…" \
  -d '{"iban":"DE89 3704 0044 0532 0130 00"}'

JavaScript

const res = await fetch("https://api.temsor.com/v1/iban/validate", {
  method: "POST",
  headers: { "content-type": "application/json", "x-api-key": KEY },
  body: JSON.stringify({"iban":"DE89 3704 0044 0532 0130 00"})
});
const { data } = await res.json();

Python

import httpx
r = httpx.post("https://api.temsor.com/v1/iban/validate",
    headers={"x-api-key": KEY},
    json={"iban":"DE89 3704 0044 0532 0130 00"})
data = r.json()["data"]
temsor API

Small, precise APIs behind one key and one response envelope. New endpoints ship on the same key.

References OpenAPI 3.1MCP manifestService health
Response contract

{ ok, data, meta }

{ ok:false, error }

Tell us what broke

Wrong answer, missing field, an endpoint you wish existed — it reaches a person, not a queue.