Changelog

Solide Network APIs’ Changelog.

[2.3.0] - 2026-08-06

The shared count (page size) query parameter is now bounded to 1..500 on paginated endpoints. A request outside those bounds is rejected with 422.

[2.2.0] - 2026-08-05

Paginated list endpoints now use a new pagination type with multi-column sorting.

[2.1.0] - 2026-07-03

[FEAT] New GET /payments/idempotencyKey/{idempotencyKey} endpoint to retrieve a payment by the idempotencyKey supplied to POST /payments/request.

[2.0.0] - 2026-07-02

Uniformization of the PaymentAssetID usage across the API (as input & returned values). Information related to an asset’s associated currency or network should now always be collected from GET /assets.

[BREAKING] Using currency + network for requesting inquiries & payments (POST /payments/inquiry / POST /payments/requests) is not possible anymore; you must now use PaymentAssetIDs sourced from GET /assets.
[BREAKING] GET /payments/{id}
- platformFees now have a dedicated field including rate, amount & assetId.
- removed platformFees platformFeesCurrency & platformFeesNetwork fields in favor of platformFees.assetId.
[BREAKING] Settlement instructions (POST & GET /settlementInstructions) now identify the target asset via a PaymentAssetID.
[BREAKING] GET /deposits/fiat now returns a single composite assetId (e.g. "EUR:LU") per deposit operation instead of a bare currency field.
[BREAKING] GET /wallets/digital now returns a single composite assetId (e.g. "EURC:polygon") per entry instead of separate network + assetIds fields; one entry is returned per supported asset. POST /wallets/digital returns the single entry for the requested asset.
[BREAKING] GET & POST /wallets/fiat responses now return a composite assetId (e.g. "EUR:LU") per bank-details entry instead of a bare currency field.
[BREAKING] List filter query parameters are uniformized across endpoints to the nested filter.asset.id / filter.asset.currency shape (mutually exclusive). This replaces the previous flat filter.assetId / filter.currencyId parameters, as well as the digitalAssetId parameter on GET /wallets/digital.
[FEAT] The following endpoints, which previously only filtered by currency, now also accept filter.asset.id:
- GET /deposits/fiat
- GET /wallets/fiat

[1.1.0] - 2026-06-19

[BREAKING] A bic (ISO 9362 / SWIFT code) is now required when creating FIAT settlement instructions with bankDetailsType: IBAN; it is validated, stored, and returned alongside the iban. Settlement instructions created before this change are unaffected.

[1.0.0] - 2026-03-09

[FEAT] Introducing the broader concept of asset via /referenceData/assets, that identify a network + currency pair, which can hold a balance and details (bank details, or a wallet pubkey)
[FEAT] Added a type property to dinstinguish DIGITAL from FIAT currencies & networks via their respective /referenceData routes
[BREAKING] Removing /currencies & /digitalAssets routes; you can now use GET /referenceData/currencies + GET /referenceData/assets to achieve the same behavior
[FEAT] Added a capabilities field to GET /referenceData/currencies to identify deposit-enabled currencies
[FEAT] You can now get multiple balances by currency (1x balance per handled asset)
[CHORE] Paths / queries / payloads shapes upgraded to stick closer to REST principles and make them easier to use / understand
[CHORE] OpenAPI documentation enhancements & cleanup

[0.0.9] - 2026-02-09

Add endpoint to retrieve and filter the list of virtual account numbers (IBANS) by currency
Add support for inhouse account types (on top of individual and corporate)

[0.0.8] - 2025-11-13

Add support for crypto assets deposits (BTC/SOL/ETH)
Add new endpoint to retrieve auth token

[0.0.7] - 2025-10-14

Add paginated API to retrieve all settlement instructions

[0.0.6] - 2025-10-07

Add settlementInstructions API to create/get FIAT settlement instructions
Update payments API to retrieve step by step payment progress

[0.0.5] - 2025-09-28

[BREAKING] Add pagination mechanism to GET /transfers and /exchange/transactions