← Turkey

Turkish Service-of-Process Clock

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

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

Try an endpoint Read the spec

POST/v1/tr/tebligat-clock

{
  "type": "electronic",
  "lawFamily": "hmk",
  "basisDate": "2026-03-16",
  "periodDays": 7,
  "periodType": "itiraz"
}

no request sent yet

Press Run to call the live API from your browser.

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

Turkey1

/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

{
  "type": "electronic",
  "lawFamily": "hmk",
  "basisDate": "2026-03-16",
  "periodDays": 7,
  "periodType": "itiraz"
}

no request sent yet

Press Run to call the live API from your browser.

Pricingone key covers every endpoint

Free

credits: 2,000
Rate limit: 2/s

Try it now

Starter

$19/mo

credits: 50,000
Rate limit: 10/s

Get a key

most picked

Pro

$79/mo

credits: 300,000
Rate limit: 30/s

Get a key

Scale

$299/mo

credits: 2,000,000
Rate limit: 100/s

Get a key

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 31 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/tebligat-clock \
  -H "content-type: application/json" \
  -H "x-api-key: fk_live_…" \
  -d '{"type":"electronic","lawFamily":"hmk","basisDate":"2026-03-16","periodDays":7,"periodType":"itiraz"}'

JavaScript

const res = await fetch("https://api.temsor.com/v1/tr/tebligat-clock", {
  method: "POST",
  headers: { "content-type": "application/json", "x-api-key": KEY },
  body: JSON.stringify({"type":"electronic","lawFamily":"hmk","basisDate":"2026-03-16","periodDays":7,"periodType":"itiraz"})
});
const { data } = await res.json();

Python

import httpx
r = httpx.post("https://api.temsor.com/v1/tr/tebligat-clock",
    headers={"x-api-key": KEY},
    json={"type":"electronic","lawFamily":"hmk","basisDate":"2026-03-16","periodDays":7,"periodType":"itiraz"})
data = r.json()["data"]