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.
Free try on this page → when you need a key, Proceed to pay · API access.
/v1/tr/tebligat-clock
{
"type": "electronic",
"lawFamily": "hmk",
"basisDate": "2026-03-16",
"periodDays": 7,
"periodType": "itiraz"
}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
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. |
/v1/tr/tebligat-clock
{
"type": "electronic",
"lawFamily": "hmk",
"basisDate": "2026-03-16",
"periodDays": 7,
"periodType": "itiraz"
}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.trTebligatClock({"type":"electronic","lawFamily":"hmk","basisDate":"2026-03-16","periodDays":7,"periodType":"itiraz"});
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"]