Changelog

Notable changes to the Lexabit API are recorded here, newest first. Each service is versioned independently under /{service}/v1/…; a breaking change to a service means a new major version for that service, not the whole API.

We follow these rules for what's a breaking vs. non-breaking change:

• Non-breaking (no version bump): adding an endpoint, adding an optional request field, or adding a field to a response. Write clients that ignore unknown response fields so these never affect you.
• Breaking (new v2 for that service): removing or renaming a field, making an optional field required, or changing a field's type or meaning.

Unreleased

Changes merged but not yet released will be listed here.

v1 — Initial public release

The first public release of the Lexabit API. Product areas available at launch:

• Authentication — login, registration, token refresh/revoke, password reset.
• Company Intelligence — company search, lookup, detail subsets (information, financials, rating, shareholders, signatories, …), and bank/IBAN utilities.
• Account Tracking — PSD2 consent flow, account discovery/tracking, transaction sync, and counterparts.
• Entity Management — clients, cases, teams, groups, projects, and the shared profile/contact/address/media/invitation sub-resources.
• Product Management — product catalog, activation, credentials, and subscriptions.
• Access & Permissions — users, role assignment, and effective-permission checks.
• Data Registry — datasets and dataset profiles.

All endpoints share the standard response envelope, X-Scope scoping, and error codes documented in the guides.