Validation
Part of the catalogue. The same key, envelope and billing cover every other endpoint too.
E-mail Verification · IBAN Validation · Phone Number Validation · Turkish Postal Code · Turkish ID & Number Validation
- 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.
/v1/email/verify
{
"email": "[email protected]"
}Press Run to try free — no key needed.Why this exists
Built for hostile input
A phone number arrives with spaces, a trunk zero and no country code; an IBAN arrives with one digit transposed. Generic validators answer yes or no and move on. These tell you what was wrong and what the input most likely meant.
Every rule carries its source
Checksums follow the published algorithms (IBAN mod-97, national BBAN structures, E.164 numbering plans). When an answer cannot be verified, the response says so instead of guessing — a structurally valid number is never presented as a registry match.
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
Validation5
/v1/email/verify
E-mail Verification
1 credit
Checks an e-mail address: syntax, whether the domain can actually receive mail, disposable and role-account detection, and typo correction.
No SMTP probing. Most competitors connect to the target server and try RCPT TO, which sounds thorough but produces a confident-looking number you cannot trust: most servers are catch-all, the big providers refuse to answer, and doing it in bulk gets the probing IP blacklisted. We report only what is provable — whether the domain has a mail exchanger, whether it is a known disposable service, whether the mailbox belongs to a role rather than a person, and whether the domain looks like a typo of a common one (gmial.com → gmail.com). Addresses are also normalised, so Gmail dots and +tags stop creating duplicate signups.
Parameters
| email* | string | E-mail address to check. |
| rejectFreeProviders | boolean | default false |
| rejectRoleAccounts | boolean | default false |
/v1/email/verify
{
"email": "[email protected]"
}Press Run to try free — no key needed.
/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). |
/v1/iban/validate
{
"iban": "DE89 3704 0044 0532 0130 00"
}Press Run to try free — no key needed.
/v1/phone/validate
Phone Number Validation
deterministic
1 credit
Validates and normalises any phone number to E.164, with structural checks for every country calling code.
For signup and checkout flows that need to store one canonical form and reject typos early. Any common input (spaces, dashes, brackets, 00 or + prefix, a stray national trunk zero) comes back as E.164 plus national notation, with the country resolved from the calling code. Numbers without an international prefix use `defaultCountry` (US when omitted), so (415) 555-0134 and +1 415 555 0134 store the same. One thing this endpoint deliberately does not claim: the current mobile operator. Numbers are portable in most markets, so a prefix says where a number was first allocated, not where it lives today. Competing APIs report the prefix owner as "the operator" and customers pick SMS routes on that basis. Where we know the original allocation we return it as `originallyAllocatedTo` with the caveat attached, because a confident wrong answer costs more than an honest gap. Countries without a full numbering plan here are validated structurally and say so in `warnings`.
Parameters
| phone* | string | Phone number in any common format. |
| defaultCountry | string | ISO 3166-1 alpha-2 country to assume when the number has no international prefix. Defaults to US. |
/v1/phone/validate
{
"phone": "(415) 555-0134"
}Press Run to try free — no key needed.
/v1/tr/postal-code
Turkish Postal Code
deterministic
1 credit
Validates a 5-digit Turkish postal code and resolves the province from the first two digits (plate map).
PTT postal codes are five digits; the leading pair matches the province plate code for the 81 provinces. This endpoint checks the shape, maps 01–81 to the province name, and returns null with confidence none when the prefix is outside that range — it does not invent a district. District-level resolution needs the full PTT directory and is out of scope here.
Parameters
| postalCode* | string | Turkish 5-digit postal code, with or without spaces. |
/v1/tr/postal-code
{
"postalCode": "34710"
}Press Run to try free — no key needed.
/v1/tr/validate
Turkish ID & Number Validation
deterministic
1 credit
Validates Turkish national ID, tax number, IBAN, licence plate, IMEI, barcodes, KEP, MERSİS, postal code and ISBN from one endpoint, with type auto-detection.
Goes past a yes/no: resolves the bank behind an IBAN, the province behind a licence plate and the GS1 country prefix behind a barcode. Pure local computation — no upstream service is called, so latency is microseconds and the answer never changes for the same input.
Parameters
| value* | string | Value to validate. |
| type | "auto" | "tckn" | "vkn" | "iban" | "plate" | "imei" | "gtin" | "kep" | "mersis" | "postal" | "isbn" | Omitted → inferred from the format. default "auto" |
/v1/tr/validate
{
"value": "TR33 0006 1005 1978 6457 8413 26"
}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.
No monthly fee: sign in, add prepaid credits ($10, $25 or $50) and use the same key across every endpoint. You pay $0 when idle.
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 — business-data and voice/call-ops agent tooling (call archive search · promises · redaction · whisper) on one surface. Claude, ChatGPT or your own agent can call them directly: same schemas, same metering, when quiet, no glue code.
Currently 43 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.emailVerify({"email":"[email protected]"});
console.log(r, r.$meta);cURL
curl -s https://api.temsor.com/v1/email/verify \
-H "content-type: application/json" \
-H "x-api-key: fk_live_…" \
-d '{"email":"[email protected]"}'JavaScript
const res = await fetch("https://api.temsor.com/v1/email/verify", {
method: "POST",
headers: { "content-type": "application/json", "x-api-key": KEY },
body: JSON.stringify({"email":"[email protected]"})
});
const { data } = await res.json();Python
import httpx
r = httpx.post("https://api.temsor.com/v1/email/verify",
headers={"x-api-key": KEY},
json={"email":"[email protected]"})
data = r.json()["data"]