Skip to main content

Changelog

v2.4.0​

New Features​

Public API​

  • Cashflow — new GET /cashflow endpoint returning the cashflow of the authenticated company keyed by period start date (MONTH, WEEK or DAY). Each period bucket contains start/end balances (actual, prognosed, total and plan), sales and purchases totals, amounts per category, aggregated income and expense details, and non-financial KPIs, plus per-period overdraft and liquidity information. All amounts are returned with two decimals. The scenario (scenarioId, defaults to the base forecast) and the date range (from/to, defaulting to 6 periods back and 18 periods ahead, maximum 36 periods) are optional query parameters. Requires the CASHFLOW_READ scope.

v2.3.0​

Improvements​

  • Invoice filtering — GET /invoices now accepts an optional, repeatable externalId query parameter to filter the results by external identifier (up to 100 values per request, to stay within URL length limits).

v2.2.0​

New Features​

Public API​

  • Bank account transaction existence check — a new POST /bank-account-transactions/exists endpoint lets clients check whether transactions with given external IDs already exist for a bank account, useful for deduplication before a bulk create or reconciliation after a resend (up to 1000 external IDs per request).

Improvements​

  • Bulk transaction creation — the bulk create response now reports skippedCount and skipped details for transactions that were skipped because they already existed (matched by externalId).

v2.1.0​

New Features​

Partner API​

  • Subscription information on accounts — the Account object now includes a subscriptionInformation field exposing the full set of subscription limits and feature flags for the account. This covers numeric limits (maxAllowedUsers, maxAllowedBankAccounts, maxAllowedCompanies, etc.), add-on counts (bankAccountAddons, companyAddons, userAddons), the billing period (subscriptionPeriod: MONTHLY, YEARLY, or TWO_YEARS), and boolean feature flags such as consolidationAllowed, aiAnalyticsAllowed, ebicsAllowed, and others.

v2.0.0​

Initial release of API v2. See the Migration Guide (v1 → v2) for upgrade instructions.

Breaking Changes​

  • New base URLs — the URL path structure changed:
    • Public API: https://api.tidely.com/api/v1/open-api → https://api.tidely.com/public/v2
    • All clients must update their base URL to migrate
  • Pagination response format — paginated endpoints now return a consistent structure with the metadata fields number, size, totalElements, and totalPages alongside the data array
  • Invoices — the single unified import endpoint of v1 has been replaced by a full set of CRUD operations. Invoices can now be listed, retrieved, created (individually or in bulk), updated, and deleted independently. Clients relying on the v1 import endpoint must migrate to the new resource-oriented operations

New Features​

The API is now split into a Public API (API-key based, for end users) and a new Partner API (OAuth 2.0, for white-label partners and system integrators operating on behalf of multiple customers via the X-Account-Id header).

Public API​

  • Bank account management — full lifecycle management of bank accounts, including access to their balances
  • Bank account transaction management — full lifecycle management of transactions, with bulk creation support
  • Company access — read-only access to company data
  • Bulk operations — bulk creation for invoices and bank account transactions

Partner API​

  • Account and user provisioning — partners can create and manage Tidely Accounts (the end customers they serve) as well as the Users within those accounts, enabling fully programmatic onboarding
  • Multi-customer operation — operate on behalf of any managed customer by selecting the target account via the X-Account-Id header
  • Embedded integration — obtain short-lived init tokens that log a user directly into the embedded Tidely frontend without a login screen
  • Full Public API surface — the Partner API also exposes the same financial planning, invoice, bank account, and transaction capabilities as the Public API, scoped per customer account

Improvements​

  • Error responses — improved, consistent error format with a causes field listing individual validation errors and failure reasons

v1 Status​

v1 is now deprecated but remains operational with security patches and bugfixes. End of life has not been scheduled; at least 6 months notice will be given. The v1 documentation remains available at https://api.tidely.com/tidely-open-api/swagger-ui/index.html.