Changelog

Policy

• Within /v1 we ship backward-compatible changes only: new fields, new endpoints, new enum values, new error codes.
• Breaking changes go to /v2, with at least 12 months of overlap. Deprecated endpoints return the Deprecation and Sunset headers.
• CI compares openapi.json with the last release and rejects breaking changes.
• Changes to the billing rules are announced at least 30 days in advance.

2026-10 · v1 (private beta)

• Endpoints: entities, by-registration-number, by-vat, lookup, search, autocomplete, VAT and tax-number validation, reference, meta/status, usage.
• Sources: FURS PO, DEJ, FO (VAT only), MT/NP, VAT groups.
• RFC 9457 error codes with a page for each at /docs/errors/<code>.

2026-10 · v1.1

• Change feed GET /v1/changes and taxpayer history GET /v1/entities/{tax}/history (Growth and up), see Changes and history.
• Monitors (/v1/monitors, every plan) with e-mail alerts, see Monitors.
• Signed webhooks (Standard Webhooks, Starter and up) with zero-downtime secret rolling, see Webhooks.
• MCP server: list_changes, get_entity_history and list_monitors tools.

2026-10-20 · Test keys discontinued

• There is one kind of secret key. New keys start with mk_…; older mk_live_… keys keep working. Publishable mk_pub_ keys are unchanged.
• mk_test_… keys were revoked and return 401 test_keys_removed. The fictional dataset is gone; every key returns real data and is billed in units.
• Monitors and webhook endpoints are no longer split by environment: an org has one list and one set of endpoints (up to 10).
• GET /v1/usage: the key object no longer has env; it has channel (key or playground), and id is null for requests from the dashboard tester.
• The MCP server has no sandbox any more, and results no longer carry environment.
• To try requests, use the API tester in the dashboard: it runs on real data, uses no units and is limited to about 20 requests per minute.

2026-10 · Financial statements (AJPES)

• GET /v1/entities/{tax}/financials: key figures from AJPES annual reports (CC BY 4.0) for capital companies and cooperatives, newest year first, with a provenance stamp per statement. Never for sole proprietors: they return coverage.status: not_covered. 1 unit. See Financial statements.
• GET /v1/entities/{tax}?include=financials_latest: the newest summary on the entity, +1 unit when returned.
• Plan access: Free latest year (summary), Starter 5 years (summary), Growth 10 years (all figures), Pro and up also raw line items (include=items).
• New billing rows in billable units; new endpoint class financials in usage.
• MCP server: get_financials tool.

2026-10-20 · New plans

• Four plans replace the previous six: Hobby (free; the API and the dashboard keep the code free), Starter (€15 a month or €150 a year), Growth (€39 or €390) and Custom (by agreement, annual contract, invoice and bank transfer). The Pro, Business and Enterprise plans are retired; existing Pro and Business subscriptions moved to Custom with their limits unchanged.
• Monthly quotas: Hobby 100 units (at most 20 a day), Starter 2,500, Growth 10,000. Burst: 1, 5 and 15 requests a second. Natural persons (s.p.) a day: 20, 200 and 1,000. Monitors: Starter 50, Growth 500; the Hobby plan has none (adding one returns 403 plan_upgrade_required), so it has no e-mail alerts either. Secret keys: 1, 3 and 10. Team members: 1, 3 and 10. See Rate limits.
• Bulk lookup POST /v1/entities/lookup and the MCP tool lookup_entities need the Starter plan; on Hobby they return 403 plan_upgrade_required (0 units).
• Publishable mk_pub_ keys and webhooks are available from Starter. The change feed and history stay on Growth and up.
• AJPES financials: not on the Hobby plan (the endpoint, get_financials and include=financials_latest return 403 plan_upgrade_required), Starter last 3 years (summary), Growth and Custom all years with all figures and raw line items (include=items). This replaces the split in the “Financial statements” entry.
• Overage (monthly billing only, opt-in): Starter €8, Growth €5 per 1,000 units. Top-up packs: Starter +2,500 units for €12, Growth +10,000 units for €39.
• Hobby organisations that already watch companies keep them on the list (they can remove them) but no longer get alerts for them. (amended 2026-10-21)
• The unit rules are unchanged.
• The new limits apply to existing Starter and Growth subscriptions too. (updated 2026-10-21)

2026-10-21 · Unpaid subscriptions and default scopes

• When a subscription payment fails (Stripe status past_due, unpaid, or an unfinished payment on an existing subscription), the API and MCP return 402 payment_required right away, with a link to billing in the dashboard; there is no grace until the end of the paid period any more. The dashboard keeps working so you can settle the payment, and access returns as soon as the payment succeeds. The dashboard API tester returns 402 meanwhile too.
• New secret keys also get the monitors scope by default. Existing keys are unchanged. See Authentication.

2026-10-21 · ESEF reports and AJPES documents

• Large companies (banks, insurers, listed and other audited companies) that file no structured table with AJPES now have figures from their audited ESEF annual report (business year 2024 on). See Financial statements.
• New fields on years[]: basis (standalone or consolidated), source_format (ajpes_json or esef) and consolidated (the group’s consolidated statements of the same year, or null). figures stay the company’s own standalone statements.
• provenance.basis gains the value consolidated; for ESEF reports items uses T:ifrs-full:… and P:ifrs-full:… keys.
• New documents list: audited and consolidated reports AJPES publishes only as files (PDF, ZIP), linked to the company’s public page in AJPES JOLP.
• coverage.status gains documents_only; coverage gains detail_sl.
• Plan rules are unchanged (Hobi none, Starter 3 years summary, Growth and Custom all figures and include=items). The MCP tool get_financials returns the same object.

Planned

• v1.2: AJPES PRS data (CC BY 4.0) and GURS addresses.