Calendar
Part of the catalogue. The same key, envelope and billing cover every other endpoint too.
Turkish Business Days
- 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/business-days
{
"start": "2026-03-16",
"addDays": 10
}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
Calendar1
/v1/tr/business-days
Turkish Business Days
deterministic
1 credit
Adds business days or counts them between two dates, accounting for Turkish public and religious holidays including half-day eves.
Ramadan and Sacrifice feasts follow the Hijri calendar and cannot be derived reliably by formula, so announced dates are read from a table; years without an official announcement are returned with `confirmed:false` rather than guessed silently. For delivery promises, SLA clocks, payment terms and shipping estimates.
Parameters
| start* | string | Start date (YYYY-MM-DD). |
| addDays | integer | Add/subtract this many business days (not calendar days). |
| end | string | If set, count business days between start and this date. |
| countHalfDaysAsWork | boolean | Count Arife half-days as working days? default true |
/v1/tr/business-days
{
"start": "2026-03-16",
"addDays": 10
}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.trBusinessDays({"start":"2026-03-16","addDays":10});
console.log(r, r.$meta);cURL
curl -s https://api.temsor.com/v1/tr/business-days \
-H "content-type: application/json" \
-H "x-api-key: fk_live_…" \
-d '{"start":"2026-03-16","addDays":10}'JavaScript
const res = await fetch("https://api.temsor.com/v1/tr/business-days", {
method: "POST",
headers: { "content-type": "application/json", "x-api-key": KEY },
body: JSON.stringify({"start":"2026-03-16","addDays":10})
});
const { data } = await res.json();Python
import httpx
r = httpx.post("https://api.temsor.com/v1/tr/business-days",
headers={"x-api-key": KEY},
json={"start":"2026-03-16","addDays":10})
data = r.json()["data"]