TR Console
← Finance

Build Turkish IBAN

Builds a Turkish IBAN from a 5-digit bank code and account number, computing ISO 7064 check digits.

POST /v1/tr/iban/build · 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, pay to unlock full access.

POST/v1/tr/iban/build
Request
{
  "bankCode": "00062",
  "accountNumber": "0000005197864578"
}
no request sent yet
Response
Press Run to try free from your browser — no key needed. Next: Ödemeye geç · API erişimi.
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

Finance1

/v1/tr/iban/build Build Turkish IBAN deterministic 1 credit

Builds a Turkish IBAN from a 5-digit bank code and account number, computing ISO 7064 check digits.

A Turkish IBAN is TR + 2 check digits + 5-digit bank code + 1 reserved digit + 16-character account. This pads the account on the left, defaults the reserved digit to 0, computes the mod-97 check digits, and resolves the bank name from the same national table used by IBAN validation when the code is known. Unknown bank codes still produce a structurally valid IBAN with bankName null — existence at the bank is not claimed.

Parameters

bankCode* string 5-digit Turkish national bank / EFT code (e.g. 00062).
accountNumber* string Account number, up to 16 alphanumeric characters (padded left with zeros).
reserved string Reserved BBAN digit after the bank code. Defaults to 0.
POST/v1/tr/iban/build
Request
{
  "bankCode": "00062",
  "accountNumber": "0000005197864578"
}
no request sent yet
Response
Press Run to try free from your browser — no key needed. Next: Ödemeye geç · API erişimi.

Pricingone key covers every endpoint

Free try on this page → when you need a key, pay to unlock full 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 37 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/tr/iban/build \
  -H "content-type: application/json" \
  -H "x-api-key: fk_live_…" \
  -d '{"bankCode":"00062","accountNumber":"0000005197864578"}'

JavaScript

const res = await fetch("https://api.temsor.com/v1/tr/iban/build", {
  method: "POST",
  headers: { "content-type": "application/json", "x-api-key": KEY },
  body: JSON.stringify({"bankCode":"00062","accountNumber":"0000005197864578"})
});
const { data } = await res.json();

Python

import httpx
r = httpx.post("https://api.temsor.com/v1/tr/iban/build",
    headers={"x-api-key": KEY},
    json={"bankCode":"00062","accountNumber":"0000005197864578"})
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.