Skip to main content
EN
Sign in Request access
← Whole catalogue

Turkey

Part of the catalogue. The same key, envelope and billing cover every other endpoint too.

Turkish Severance, Notice & Leave · Turkish Service-of-Process Clock · Turkish VAT & Withholding

  • 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/tr/labor
Request
{
  "startDate": "2025-08-01",
  "endDate": "2026-08-01",
  "monthlyGross": 33030
}
no request sent yet
Response
Press Run to try free — no key needed.
3endpoints
1API families
3deterministic endpoints
—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 rule carries its source

Checksums follow the published algorithms (TCKN/VKN, IBAN mod-97), and dated tables such as the severance ceiling, minimum wage and VAT withholding rates cite the regulation and the date they apply from. 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

Turkey3

/v1/tr/labor Turkish Severance, Notice & Leave deterministic 1 credit

Computes Turkish severance (kıdem), notice (ihbar) and annual-leave entitlement from service dates and the gross wage, using the official ceiling and minimum-wage tables for the given day.

Payroll and HR tools in Turkey chase a parameter that changes every January and July: the severance ceiling, the SGK cap, the minimum wage. This endpoint applies the statutory formulae (Labour Law 4857 arts. 17 and 53, former 1475 art. 14) to those tables. The ceiling is applied to the monthly wage, not the total. Stamp tax (0.759%) is deducted from severance; income tax is not — kıdem is exempt. Notice pay IS taxable; we return the gross and say so, because the actual withholding depends on the employee's cumulative tax base. What this will not tell you: whether the employee is entitled to severance at all. That depends on the reason for termination (retirement, just cause, marriage, military service…). Treating the number as "what is owed" is how you lose at trial.

Parameters

startDate* string Employment start date (YYYY-MM-DD).
endDate* string Termination date (YYYY-MM-DD). Inclusive of this day.
monthlyGross* number Gross monthly wage the severance is based on (giydirilmiş brüt).
asOf string Rate table date. Defaults to endDate.
age integer Employee age at termination — affects annual-leave entitlement (under 18 or 50+).
unusedLeaveDays number Unused annual-leave days, if you also want the unused-leave gross.
POST/v1/tr/labor
Request
{
  "startDate": "2025-08-01",
  "endDate": "2026-08-01",
  "monthlyGross": 33030
}
no request sent yet
Response
Press Run to try free — no key needed.
/v1/tr/tebligat-clock Turkish Service-of-Process Clock deterministic 1 credit

Computes the deemed-received date and the HMK deadline (with holiday shifting) for a Turkish notification, from the date the underlying event actually happened.

Turkish notification law (7201) ties the deadline clock to an event that is not "the date on the letter" — for electronic notification the UETS platform reports send, read AND reached dates, and only the reached date starts the clock (art. 7/a: deemed received 5 calendar days after reaching the address, whether or not it was opened). HMK adds two more rules on top: the day of notification itself does not count (art. 92 — the period starts the next day) and if the computed last day lands on a weekend or a full public/religious holiday, it moves to the next business day (art. 93); a half-day eve (arife) does not shift it. What this will not tell you: whether the notification was itself valid, or what a specific `periodType` (itiraz, temyiz, cevap…) is in days for your case — that number differs by statute and we do not guess it; supply `periodDays` yourself. Only the "hmk" law family is covered so far.

Parameters

type* "electronic" | "physical" | "vekil" | "ilanen" | "last_known_address" Notification method. Determines which event `basisDate` refers to and whether the deemed-received date is same-day or shifted.
lawFamily* "hmk" Body of procedural law the period is computed under. Only "hmk" (Code of Civil Procedure) is supported so far.
basisDate* string The date `basisLabel` describes for this type — for "electronic" this is the date UETS reports the message as reached, not sent or read.
periodDays* integer Length of the statutory or judicial period, in days, counted from `periodStart`.
periodType string Free-text label for the period (e.g. "itiraz", "temyiz"), echoed back only — not mapped to a day count.
ilanenDeemedDays integer Only valid with type "ilanen": number of days the competent authority set for the notice to become deemed received (TK 31), 7-15, default 7. Not the number of days for the underlying period.
hasAttorney boolean Whether the addressee has a registered attorney of record. When true and `type` is not "vekil", a TK 11 warning is added noting that service should have gone to the attorney.
subjectToJudicialRecess boolean Whether this matter is subject to the judicial recess (adli tatil, HMK 104) instead of being exempt. Only affects the result when `lawFamily` is "hmk" and the computed last day falls in the 20 July - 31 August window.
POST/v1/tr/tebligat-clock
Request
{
  "type": "electronic",
  "lawFamily": "hmk",
  "basisDate": "2026-03-16",
  "periodDays": 7,
  "periodType": "itiraz"
}
no request sent yet
Response
Press Run to try free — no key needed.
/v1/tr/vat Turkish VAT & Withholding deterministic 1 credit

Splits a Turkish amount into net, VAT and (optionally) withholding: who pays the seller, who remits the withheld VAT.

For invoice lines and checkout totals that have to show KDV dahil / hariç and, when the parties are in a withholding (tevkifat) situation, the split between what the buyer pays the seller and what the buyer remits to the tax office. Rates are 0, 1, 10 and 20 percent. Withholding is a fraction of the VAT (2/10 through 10/10), or a named code from the GİB partial-withholding list. The 2026 threshold (TRY 12,000 gross) is reported and compared with the amount, but `applies` is always null: whether withholding actually applies depends on the taxpayer status of both parties, which this endpoint does not know. Feeding it a fraction is not a legal opinion.

Parameters

amount* number The amount to tax. See amountIncludesVat.
amountIncludesVat boolean If true, `amount` is the gross (KDV dahil); if false, it is the net/matrah. default false
rate number | number | number | number VAT rate in percent. 0, 1, 10 or 20. default 20
withholding string Withholding fraction such as "5/10", or a code from the list (reklam, tasima, hurda, isgucu…).
POST/v1/tr/vat
Request
{
  "amount": 1000,
  "rate": 20
}
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 — 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.trLabor({"startDate":"2025-08-01","endDate":"2026-08-01","monthlyGross":33030});
console.log(r, r.$meta);

cURL

curl -s https://api.temsor.com/v1/tr/labor \
  -H "content-type: application/json" \
  -H "x-api-key: fk_live_…" \
  -d '{"startDate":"2025-08-01","endDate":"2026-08-01","monthlyGross":33030}'

JavaScript

const res = await fetch("https://api.temsor.com/v1/tr/labor", {
  method: "POST",
  headers: { "content-type": "application/json", "x-api-key": KEY },
  body: JSON.stringify({"startDate":"2025-08-01","endDate":"2026-08-01","monthlyGross":33030})
});
const { data } = await res.json();

Python

import httpx
r = httpx.post("https://api.temsor.com/v1/tr/labor",
    headers={"x-api-key": KEY},
    json={"startDate":"2025-08-01","endDate":"2026-08-01","monthlyGross":33030})
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.