Changelog

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.

User Management API

New endpoints for managing users and sessions:

• POST /users - Create a user with an externalId mapping to your system
• GET /users - Find a user by externalId
• GET /users/{userUuid} - Get user by UUID (supports both API key and JWT)
• DELETE /users/{userUuid} - Anonymize a user (soft delete)
• POST /users/{userUuid}/sessions - Create a JWT session token scoped to the user
• GET /users/{id}/collections - Get all collections for a user
• GET /users/{id}/consents - Get all consents for a user

New schemas: UserResponse, CreateUserRequest, SessionResponse

New PSD2 Banking Data Support

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

• Psd2SavingsAccount - Savings accounts accessible via PSD2
• Psd2CheckingAccount - Checking/current accounts via PSD2
• Psd2CreditCard - Credit card products via PSD2

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.