Developers › Changelog

Changelog

The version is in the path (/api/v1/). What that promises, and what it does not.

What will not change within v1

  • Existing field names and their meaning.
  • Existing error codes and which HTTP status they carry.
  • Existing filter parameters — including the level-dependent behaviour documented on the filter page.
  • The shape of pagination and billing.

What may change without a new version

  • New fields, groups and filters. Parse defensively: ignore keys you do not recognise rather than failing on them.
  • Error message wording. Match on code, never on message.
  • Prices. Announced to affected customers before they take effect. Your invoice always uses the price that was in force at the time of the call — we keep price history for exactly this reason.
  • The data itself. Coverage grows and rows change as companies change. That is the product.

Releases

DateChange
2026-08-17v1 — first release. Company and decision-maker endpoints, free counts, cursor pagination, field-group pricing, 30-day repeat window, per-key quotas and spend cap.

Planned

  • OpenAPI description. Deliberately not shipped with v1: a hand-maintained specification that drifts from the implementation is worse than none, so it will come when it is generated from the same source as this documentation.
  • Webhooks for changes. Being able to hear that a decision-maker changed, rather than polling for it.

If either of those decides whether you can build what you want, say so — it moves them up the list.

Aloita kohderyhmän rajaus