Skip to main content
TR FR / API · Türkiye

Build on Türkiye filings programmatically.

A typed REST API over 925,584 filings from 715 Turkish listed companies — JSON metadata, Markdown body, and original PDF. Webhooks on every new release.

Public-company filings in Türkiye are supervised by Capital Markets Board of Türkiye (SPK). Reporting follows IFRS / Turkish Financial Reporting Standards (TFRS). Filings are most commonly published in Turkish and English. Major issuers are listed on BIST 100, BIST 30 and BIST 50. Calendar year.

Integrating Turkish filings programmatically

The FinancialReports API delivers SPK-supervised Turkish filings through the same single REST surface, one x-api-key header, and one shared rate-limit bucket used across all 42 covered markets. A Türkiye-only integration is a one-parameter filter (?country=TR) on the global filings endpoint — no separate KAP-tier API key, no parallel billing, no per-country infrastructure. The same endpoint returns a BIST 30 annual report, an özel durum açıklaması material-event disclosure, and a GİP admission document within the identical JSON envelope.

For live pipelines, the webhook subscription is the recommended path: subscribe once, receive a POST with full filing metadata within roughly 60 seconds of KAP publication. Turkish market hours and SPK disclosure timing mean the highest-volume periods cluster around the pre-market window and post-close announcements on Borsa İstanbul trading days. The webhook payload shape is identical across all covered markets, so a Turkish özel durum açıklaması arrives at your endpoint with the same JSON structure as a German ad-hoc or a French Informations Réglementées release. Country routing is handled server-side; consumer code stays market-agnostic.

Filing bodies are available as JSON metadata, Markdown via /api/filings/{id}/markdown/ (the processed text rendered on the public web pages), and original PDF for audit and archival use. A critical metadata field for Turkish data is the inflation-accounting flag: filings from 2023 onward for issuers applying TAS 29 carry a restatement indicator in the JSON payload, allowing downstream systems to route inflation-adjusted and nominal statements into separate processing branches without manual triage. The Markdown layer normalises KAP's variable PDF layouts — including the complex tabular structures common in Turkish banking and holding-company reports — into consistent, parseable text.

Common API integrations for Turkish data include backfilling BIST 30 / BIST 100 TFRS consolidated financials with inflation-adjustment context for EM quant research, triggering on özel durum açıklamaları for event-driven strategies (dividend announcements, Koç and Sabancı subsidiary transactions, regulatory approvals), monitoring KAP insider-transaction notifications, tracking GİP admissions and delistings, and feeding Turkish-language filings into emerging-market LLM pipelines. Trial keys are available on request; the web product is free and indexed for the public web, so coverage across the Borsa İstanbul universe is verifiable before integration.

Filings indexed
925,584
in Türkiye
Listed companies
715
Turkish issuers
Auth
x-api-key
single header
Webhook latency
< 1 min
from regulator publish

Reporting at a glance — Türkiye

Regulator, indices, accounting, language
Primary indices
BIST 100BIST 30BIST 50
Accounting standards
IFRS / Turkish Financial Reporting Standards (TFRS)
Reporting languages
TurkishEnglish
Fiscal year
Calendar year

Quick start — Türkiye filings

REST · JSON · Markdown · PDF
# 1. List filings for Türkiye, newest first
curl "https://api.financialreports.eu/api/filings/?countries=TR" \
    -H "x-api-key: $FR_API_KEY"

# 2. Pull full Markdown for one filing
curl https://api.financialreports.eu/api/filings/<id>/markdown/ \
    -H "x-api-key: $FR_API_KEY"

# 3. Filter by filing type — annual reports only
curl "https://api.financialreports.eu/api/filings/?countries=TR&type=10-K" \
    -H "x-api-key: $FR_API_KEY"

# 4. Filter by ISIN (single issuer)
curl "https://api.financialreports.eu/api/filings/?company_isin=DE000A1EWWW0" \
    -H "x-api-key: $FR_API_KEY"

Full API documentation ↗ · Interactive Swagger ↗

Sample Türkiye response

Real filings · live data

Get API access for Türkiye

Pricing · trial keys · enterprise
Get API access Talk to the team Read the docs ↗

Filings activity by year

Last 6 years · Turkish issuers
  • 2026 24,622
  • 2025 84,711
  • 2024 83,594
  • 2023 75,487
  • 2022 64,647
  • 2021 60,230

Reporting languages

Filing-by-filing distribution
  • Turkish 747,069
  • English 176,820
  • German 806
  • Portuguese 481
  • Italian 106

FAQ — Türkiye

Coverage, formats, integration
How do I authenticate API requests for Türkiye filings?
Send a single header — `x-api-key: $FR_API_KEY` — on every request. The same key works across all 42 covered markets; there's no per-country key.
What format does the Türkiye API return?
Filing metadata is returned as JSON. Full filing bodies are available as Markdown (one endpoint) and original PDF. The same payload shape is used across every covered market.
Do you provide webhooks for new Turkish filings?
Yes. Webhook subscribers receive a POST with full filing metadata within ~60 seconds of the regulator publishing the document.
Is there a rate limit on the Turkish API?
Standard plans are throttled to a generous request budget that suits typical research and dashboards. Bulk and high-throughput plans negotiate higher limits.
Is there a free tier for Türkiye data?
The web product (search, browse, single-filing read) is free and indexed for the public web. Programmatic API access is a paid plan; trial keys are available on request.