Changelog

2026-11-16

Api-Version replaces Insurely-Version

  • The API version is now sent in the Api-Version header, for example Api-Version: 2026-04-01. It takes the same values as Insurely-Version and selects the version in the same way.
  • Insurely-Version keeps working for API versions up to and including 2026-04-01, so existing integrations do not need to change straight away.
  • Versions after 2026-04-01 accept only Api-Version. A request that sends Insurely-Version with a later version returns 400.
  • Send only one of the two headers. A request that sends both returns 400.

Action: rename the header to Api-Version in your requests. Nothing else about the request or the response changes.

2026-11-12

Changes made to BuyTransaction, SellTransaction, RedemptionTransaction and DividendTransaction

  • exchangeRate has been added. It is the exchange rate the bank used for the transaction, from the instrument's currency (the currency of dividendPerUnit on a dividend) to the currency of amount. For example 9.81 when a USD share is bought from a SEK account (1 USD = 9.81 SEK).

The field is absent when the provider does not supply a rate, and when the currencies are the same. The full transaction history from GET /collections/{collectionId}/wealth/transactions includes it too.

2026-11-11

Financial products

  • servicingBank has been added to the investment, pension, KF, general savings and loan products. Swedbank and the savings banks (sparbanker) share a platform, so a collection from se-swedbank can contain products from Swedbank as well as from one or more savings banks, depending on which banks the user is a customer of. servicingBank tells which bank the product comes from, for example { "id": "se-sparbanken-skane", "name": "Sparbanken Skåne" }. It is only populated for products collected from se-swedbank. The possible ids are listed on Wealth.ServicingBank. New ids can be added when savings banks join or merge, so don't treat the list as fixed.

2026-11-10

Changes made to TransactionInstrument

  • priceInInstrumentCurrency has been added. It is the price of the instrument in the currency it trades in, for example USD for a US share bought from a SEK account.

Changes made to DividendTransaction

  • quantity has been added. It is the number of units the dividend was paid on.
  • dividendPerUnit has been added. It is the dividend per unit, in the currency the dividend is declared in.

The new fields are absent when the provider does not supply them. The full transaction history from GET /collections/{collectionId}/wealth/transactions includes them too.

2026-10-29

Changes made to Holder

  • type has been added. It is PERSON or ORGANIZATION and tells whether a person or an organization owns the financial product. A sole proprietorship (enskild firma) is PERSON. The field is absent when the type could not be determined, and is currently only provided for capital insurances (KF).

2026-05-27

Financial Products

  • Restructured fees object (breaking) — The flat fee fields on Fees have been replaced by two mutually-exclusive sub-objects, PersonalizedFees and GenericFees: exactly one of fees.personalized / fees.generic is present per response (and fees is absent when no fee data exists), so its presence — not the removed feesCollected flag — now signals whether the figures are personalized to the holder or a generic mapping. See the migration guide for the field-by-field mapping from 2025-01-01.

2026-04-01

Collections API

  • Collections are now a top-level /collections resource (breaking) — collection endpoints no longer live under the product namespace. POST /wealth/collection becomes POST /collections (shared across products), with wealth data read from /collections/{collectionId}/wealth/data. The request body also moves from the untyped input map (plus consents / filter arrays) to a typed parameters array, which changes how each Swedish login method (BankID, email) is supplied. See the migration guide for the endpoint mapping, parameter shapes, and per-login-method changes.

Changes made to CollectionStatus

The following statuses have been added. No statuses have been removed.

  • AUTHENTICATION_ERROR — returned when authentication fails for a reason other than incorrect credentials, for example a rejected consent or an error raised by the company during sign-in.
  • LOGIN_METHOD_NOT_APPLICABLE — returned when the requested loginMethod cannot be used for the company.

Any exhaustive switch over the status enum needs a branch — or a default — for the new values. Every status, including those already returned by 2025-01-01, is described in the collection statuses table.

User Management API

New endpoints for managing users and sessions:

New schemas: UserResponse, CreateUserRequest, SessionResponse

New PSD2 Banking Data Support

This version introduces PSD2 Account Information Service (AIS) support for collecting banking data:

Consent Management

New consent lifecycle for PSD2 data collection:

  • Consent - Consent record with status tracking, expiration, and scope
  • CreateConsentRequest - Create PSD2 AIS consents with company, login method, and parameters
  • ConsentStatusResponse - Poll consent status with auth instructions (BankID QR code or autostart token) and recommended polling interval
  • ConsentError / ConsentStatusError - Structured error handling for consent failures
  • Consent status flow: INITIATED → AWAITING_AUTHORIZATION → AUTHORIZED | REVOKED | EXPIRED | FAILED

New Parameters

  • Psd2AisConsentParameter - Handle AIS consent when initiating PSD2 collections
  • SwedishBankIdParameter - Swedish BankID authentication for consent authorization
  • Support for stored consent handling for previously-authorized collections

Financial Products

  • Typed personalInformation — The personalInformation field on all financial product responses has changed from an untyped key-value map to a typed PersonalInformation object with named fields (personalInformation.personalNumber instead of personalInformation["PERSONAL_NUMBER"]). The object may be null when no personal data is available, and additional fields may be added in future versions.