TR Try tools
← Whole catalogue

Time Series

Part of the catalogue. The same key, envelope and billing cover every other endpoint too.

Time Series History · Turkey Fuel Prices

  • 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/series/history
Request
{}
no request sent yet
Response
Press Run to try free — no key needed.
2endpoints
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

Time Series2

/v1/series/history Time Series History 2 credits

Returns the accumulated history of public data series with change statistics and a source receipt for every point.

Currently ingesting the Turkish Central Bank daily FX bulletin (`tcmb.usd`, `tcmb.eur`, …), normalised to one unit so JPY-style 100-unit quotes stop biting. Leave `seriesId` empty to list the catalogue. `fillGaps` carries the last value across weekends and holidays; `includeEvidence` attaches the source URL and content hash for every point, so a value can still be defended years later.

Parameters

seriesId string Series id, e.g. `tcmb.usd`. Omit to list the catalogue.
from string Start date (inclusive).
to string End date (inclusive).
limit integer default 365
fillGaps boolean default false
includeEvidence boolean Include source URL and content excerpt for each point. default false
POST/v1/series/history
Request
{}
no request sent yet
Response
Press Run to try free — no key needed.
/v1/tr/fuel/prices Turkey Fuel Prices 2 credits

Petrol, diesel and heating-oil pump prices for all 81 Turkish provinces, including the price in force on any past date.

The distributor publishes today's pump price and a per-district history query, one district and one range at a time. This endpoint answers the question that actually costs money, in a single call: what was diesel in Ankara on 12 March? Pass `asOf` for the price in force on that day — if the distributor did not change prices that day, the previous price is carried forward and `effectiveFrom` says when it started, with `carriedForward: true`. Pass `from`/`to` to get the change events in a window, each with the percentage move. Every figure carries the source URL and a content hash of the page it was read from, so the number can still be defended in an audit years later. Leave `province` empty to list coverage.

Parameters

province string | number Province name or plate code — "Ankara", "istanbul" or 34. Leave empty to list covered provinces.
product "benzin" | "motorin" | "motorin_ekstra" | "gazyagi" | "kalorifer" | "fueloil" | "fueloil_yk" Fuel product. Omitted → every product available for that province.
asOf string Price in force on this date (YYYY-MM-DD). Omitted → latest known price.
from string With `to`: return the price changes in this window.
to string
includeDistricts boolean Adds districts whose pump price differs from the province reference price. default false
POST/v1/tr/fuel/prices
Request
{}
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/series/history \
  -H "content-type: application/json" \
  -H "x-api-key: fk_live_…" \
  -d '{}'

JavaScript

const res = await fetch("https://api.temsor.com/v1/series/history", {
  method: "POST",
  headers: { "content-type": "application/json", "x-api-key": KEY },
  body: JSON.stringify({})
});
const { data } = await res.json();

Python

import httpx
r = httpx.post("https://api.temsor.com/v1/series/history",
    headers={"x-api-key": KEY},
    json={})
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.