Skip to content

Meet us at COP31Read more

API documentation

Changelog

Every change to the Data API since version 2.0.0 on 27 May 2026, newest first. Changes that shipped without a new version number are listed by date. Changed behaviour is marked as such.

API version 2.4.1 · Updated 6 October 2026

Version 2.4.1

Clearer errors for malformed requests, and corrections to the sync guidance.

  • A request body that is not JSON, JSON containing NaN, Infinity or an invalid Unicode escape, an unparseable updated_since date, a since timestamp at the very edge of the calendar, and a report id, cursor or year outside its valid range now return 422 problem details instead of 500.
  • Changed: each entry in the errors list of a 422 carries type, loc and msg, and the list holds at most 50 entries. The value you sent is no longer echoed back.
  • The OpenAPI description served by the API points incremental sync at GET /reports/changes. The updated_since filter on GET /reports filters on the publication date and is not a change cursor.
  • The bulk-downloads guide now starts the first change-feed read about one hour before the first load began, and monthly reconciliation adds reports you do not hold as well as flagging reports that no longer appear.
  • The data model guide explains that filtering on the adjacent fiscal year cannot reach reports outside your licence window.
  • After the fiscal-year correction, the data model guide replaces its note on older two-year values with a one-line note on the few records still under review.

5 October 2026

Within version 2.4.0

Fiscal years corrected to the end-year convention.

  • Reports whose fiscal year was recorded as a two-year value or a start year now carry the year in which the fiscal year ends. Reports that changed come through the change feed as updates; reports that left your licence window are found by monthly reconciliation.
  • A handful of records still hold a two-year value while they are reviewed. The fcyear filter and licence windows read its first year.

2 October 2026

Within version 2.4.0

Public documentation, and faster paging.

  • Public documentation published on the website at /docs/api: guides, the data model, this changelog and a downloadable OpenAPI file.
  • GET /reports returns pages much faster for large watchlists and for ISIN filters. Results and their order are unchanged.
  • GET /reports/changes returns pages much faster. Results and their order are unchanged.
  • The interactive references served by the API at /api/v2/docs and /api/v2/redoc render in the browser.
  • The OpenAPI descriptions of report_fcyear and the fcyear filter follow the end-year convention: a fiscal year that spans two calendar years is tagged with the year in which it ends.

Version 2.4.0

The change feed, full delivery metadata on every report, and stricter request limits.

  • New GET /reports/changes: every report in your licence that was added, updated or withdrawn since a point in time, with a resumable cursor, at-least-once delivery and a settling delay of at least 15 minutes. Companies added to your licence replay their existing reports through the feed.
  • Every report carries metadata: the 50 field-guide columns exactly as in a bulk delivery file. Reports also gain company_lei and company_figi.
  • POST /companies/resolve reports an identifier that matches more than one company as ambiguous instead of picking one, accepts up to 1,000 identifiers per call and needs an active licence.
  • Changed: POST /companies/resolve returns company details only for companies in your licence. For a company outside it, entitled is false and company is null.
  • The isin filter on GET /reports also matches a company’s alternate ISINs.
  • More than 500 filter values, more than 20 language codes or an unknown framework code on GET /reports, and more than 1,000 keys on POST /reports/lookup, return 422 instead of being cut off or ignored.
  • Signed links are HTTPS only, valid for up to 15 minutes and never beyond your key’s own expiry. A link is issued only once the request is recorded against your key; otherwise the API returns 503 with Retry-After.
  • Responses carry Cache-Control: private, no-store by default; the field guide PDF stays publicly cacheable. Timestamps carry an explicit UTC offset. Unexpected errors return problem details without internal detail.
  • The per-key rate limit is counted across all of our servers when the shared counter is available, with a per-server fallback otherwise.
  • Changed: more ISINs are withheld, as described under "Some ISINs are withheld" in the data model guide. A licence covers only the report types and document classes described in the documentation.

24 to 30 September 2026

Within version 2.3.0

Bilingual reports and undated documents.

  • A bilingual report carries both language codes in report_lang, for example EN-DE, and the language filter matches either code.
  • Changed: report_edition is the string form of edition_number, kept for compatibility.
  • Undated documents carry report_year 0 and no fiscal year.

6 September 2026

Within version 2.3.0

The field guide schema (V3) on every report.

  • Reports gain the fields of schema V3: report_class, document_scope, content_sha256, period_start_date, period_end_date, fiscal_year_label, edition_number, standards_eu_taxonomy, standards_ungp, gri_level, sbti_status, assurance_provider, independent_assurance_report_included, nace_code and naics_code. Existing field names are unchanged.
  • New GET /meta/schema (the field dictionary in machine-readable form) and GET /meta/field-guide.pdf.
  • Changed: ISINs of US and Canadian issuers are withheld, as in bulk deliveries.

Version 2.3.0

Company identifiers and wider identifier resolution.

  • Companies carry lei, figi, cik and fiscal_year_end_month.
  • POST /companies/resolve accepts LEIs, FIGIs, CIKs, alternate ISINs, home-market symbols and exact company names or known aliases, as well as ISINs, MIC:TICKER pairs and company keys.

6 and 14 August 2026

Within version 2.2.0

Renamed and merged reports stay reachable.

  • A report that was merged into another or renamed stays reachable: its old report_id or report_key resolves to the current report, and the response names both the identifier you requested and the current one.

9 and 16 June 2026

Within version 2.2.0

Secondary listings and extended fields.

  • The mic filter matches a company’s secondary listings as well as its primary listing.
  • Reports gain extended datapoint, standards and quality fields that are filled only for full-corpus keys. For licence keys they are null.

Version 2.2.0

More report and company filters.

  • GET /reports adds the filters fcyear, industry, mic, exchange, isin, ticker, assurance, assurance_level, materiality_assessment and materiality_matrix, and a free-text search over company name and report title.

30 May to 2 June 2026

Within version 2.0.0

Record timestamps, batch lookup and markdown renditions. Announced at the time as 2.1.0; the API kept reporting 2.0.0 until version 2.2.0.

  • Every report carries created_at and updated_at.
  • New POST /reports/lookup resolves up to 1,000 report_key values to report_id values in one call.
  • Reports carry formats, the renditions your key may download. Full-corpus keys can download markdown renditions of reports through the format parameter of the download endpoint.
  • Much faster responses when several requests run at once.

Version 2.0.0

The first version of the Data API.

  • Licence-scoped access: each key sees the reports of the companies on its watchlist within its fiscal-year window. GET /entitlements and GET /watchlist describe the licence.
  • GET /reports with cursor pagination and filters on year, type, language, framework, country, sector and company key, plus updated_since, a publication-date filter; GET /reports/{report_id}; signed PDF links from GET /reports/{report_id}/download.
  • POST /companies/resolve maps ISINs, MIC:TICKER pairs and company keys to companies. GET /meta/frameworks, GET /meta/usage and GET /health.
  • Keys are sent as Authorization: Bearer or X-API-Key. Per-key rate limits are reported in X-RateLimit headers. Errors use RFC 9457 problem details.
  • Each report carries the 34 metadata fields of the delivery schema of the time.
  • Full-corpus keys: a key can be granted the whole catalogue instead of a watchlist, shown as full_access in GET /entitlements.
  • A report is listed only once its PDF is stored and available for download.