TR Try tools
← Finance

Turkish e-Invoice Builder

Builds a UBL-TR e-Invoice or e-Archive XML document from plain JSON, computing every total and validating the parties.

POST /v1/tr/invoice/build · 3 credits

  • 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/invoice/build
Request
{
  "series": "ABC",
  "sequence": 123,
  "issueDate": "2026-07-26",
  "supplier": {
    "name": "Örnek Yazılım A.Ş.",
    "taxNumber": "4840847211",
    "taxOffice": "Kadıköy",
    "street": "Moda Cad.",
    "buildingNumber": "12",
    "district": "Kadıköy",
    "city": "İstanbul"
  },
  "customer": {
    "name": "Alıcı Ticaret Ltd. Şti.",
    "taxNumber": "3250566341",
    "taxOffice": "Beşiktaş",
    "city": "İstanbul"
  },
  "lines": [
    {
      "name": "Yazılım geliştirme hizmeti",
      "quantity": 10,
      "unitCode": "HUR",
      "unitPrice": 1500,
      "vatRate": 20
    }
  ]
}
no request sent yet
Response
Press Run to try free — no key needed.
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

Finance1

/v1/tr/invoice/build Turkish e-Invoice Builder 3 credits

Builds a UBL-TR e-Invoice or e-Archive XML document from plain JSON, computing every total and validating the parties.

Selling into Türkiye means issuing a UBL-TR document whose element order is fixed by schema and whose totals must agree to the kuruş, or the integrator rejects it. This endpoint takes the invoice as ordinary JSON and returns the XML. Totals you send are ignored on purpose — line amounts, per-rate VAT subtotals and the payable amount are all recomputed here, because a rounding difference of one kuruş is the most common rejection. VKN and TCKN checksums are verified, and the amount is written out in Turkish words as invoices require. It does not sign the document and does not transmit it: the financial seal and the submission to the tax authority belong to your certificate and your integrator. What comes back is a document ready to enter that step.

Parameters

profile "TEMELFATURA" | "TICARIFATURA" | "EARSIVFATURA" TEMELFATURA: no formal objection flow. TICARIFATURA: buyer may accept/reject. EARSIVFATURA: buyer is not an e-Invoice user. default "TEMELFATURA"
invoiceTypeCode "SATIS" | "IADE" default "SATIS"
id string Invoice number. Omit and supply `series` to have it built from the series and sequence.
series string Three-letter series code, used with `sequence`.
sequence integer Sequence number within the series and year.
uuid string Document UUID (ETTN). Generated when omitted.
issueDate* string
issueTime string
currency string ISO 4217. Anything other than TRY requires `exchangeRate`. default "TRY"
exchangeRate number Units of TRY per one unit of `currency`.
supplier* object
customer* object
lines* object[]
notes string[] default []
amountInWords boolean Adds the payable amount written out in Turkish words as a note, the way invoices require. default true
despatchDocumentId string Delivery note number, if the goods shipped separately.
orderReferenceId string
POST/v1/tr/invoice/build
Request
{
  "series": "ABC",
  "sequence": 123,
  "issueDate": "2026-07-26",
  "supplier": {
    "name": "Örnek Yazılım A.Ş.",
    "taxNumber": "4840847211",
    "taxOffice": "Kadıköy",
    "street": "Moda Cad.",
    "buildingNumber": "12",
    "district": "Kadıköy",
    "city": "İstanbul"
  },
  "customer": {
    "name": "Alıcı Ticaret Ltd. Şti.",
    "taxNumber": "3250566341",
    "taxOffice": "Beşiktaş",
    "city": "İstanbul"
  },
  "lines": [
    {
      "name": "Yazılım geliştirme hizmeti",
      "quantity": 10,
      "unitCode": "HUR",
      "unitPrice": 1500,
      "vatRate": 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, 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 68 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/invoice/build \
  -H "content-type: application/json" \
  -H "x-api-key: fk_live_…" \
  -d '{"series":"ABC","sequence":123,"issueDate":"2026-07-26","supplier":{"name":"Örnek Yazılım A.Ş.","taxNumber":"4840847211","taxOffice":"Kadıköy","street":"Moda Cad.","buildingNumber":"12","district":"Kadıköy","city":"İstanbul"},"customer":{"name":"Alıcı Ticaret Ltd. Şti.","taxNumber":"3250566341","taxOffice":"Beşiktaş","city":"İstanbul"},"lines":[{"name":"Yazılım geliştirme hizmeti","quantity":10,"unitCode":"HUR","unitPrice":1500,"vatRate":20}]}'

JavaScript

const res = await fetch("https://api.temsor.com/v1/tr/invoice/build", {
  method: "POST",
  headers: { "content-type": "application/json", "x-api-key": KEY },
  body: JSON.stringify({"series":"ABC","sequence":123,"issueDate":"2026-07-26","supplier":{"name":"Örnek Yazılım A.Ş.","taxNumber":"4840847211","taxOffice":"Kadıköy","street":"Moda Cad.","buildingNumber":"12","district":"Kadıköy","city":"İstanbul"},"customer":{"name":"Alıcı Ticaret Ltd. Şti.","taxNumber":"3250566341","taxOffice":"Beşiktaş","city":"İstanbul"},"lines":[{"name":"Yazılım geliştirme hizmeti","quantity":10,"unitCode":"HUR","unitPrice":1500,"vatRate":20}]})
});
const { data } = await res.json();

Python

import httpx
r = httpx.post("https://api.temsor.com/v1/tr/invoice/build",
    headers={"x-api-key": KEY},
    json={"series":"ABC","sequence":123,"issueDate":"2026-07-26","supplier":{"name":"Örnek Yazılım A.Ş.","taxNumber":"4840847211","taxOffice":"Kadıköy","street":"Moda Cad.","buildingNumber":"12","district":"Kadıköy","city":"İstanbul"},"customer":{"name":"Alıcı Ticaret Ltd. Şti.","taxNumber":"3250566341","taxOffice":"Beşiktaş","city":"İstanbul"},"lines":[{"name":"Yazılım geliştirme hizmeti","quantity":10,"unitCode":"HUR","unitPrice":1500,"vatRate":20}]})
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.