← Turkey

Turkish Severance, Notice & Leave

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.

POST /v1/tr/labor · 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.

Try free Proceed to pay · API access Read the spec

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.

1endpoints

1API families

1deterministic 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

Turkey1

/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.

Pricingone key covers every endpoint

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

Proceed to pay · API access All plans →

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"]