2.14.0 Test Environment Current

v.2.14.0 - Test Environment

2026-10-13 - Planned deployment to Live 2026-09-29 - Test Environment

2026-10-13 - Planned deployment to Live

2026-09-29 - Test Environment

Added

Quarterly Depository Account Statement and Ex-Post Cost Statement Document Types

Two periodic customer documents are now generated for depository accounts. Both use the standard document channel: the partner gets a document webhook and downloads the file through the documents API.

  • Documentation Location: API REFERENCE - Documents
  • New enum value: DEPOSITORY_ACCOUNT_STATEMENT on DocumentTypeEnum - quarterly statement of holdings, generated after each quarter ends for every active depository account and dated the last day of that quarter.
  • New enum value: EX_POST on DocumentTypeEnum - annual ex-post cost statement per depot. It lists the one-off and ongoing costs charged in the previous calendar year, with a breakdown per security.
  • Note: Download both with GET /documents/{documentId}/file. No new endpoint is required. Clients that validate documentType against a fixed list should add the two values.

eWP Transaction Fee - Fee Trigger Events

eWP (BART) buy and sell orders are now charged a variable transaction fee. Fee instances expose the new trigger events and can be scoped to a single digital asset.

  • Documentation Location: API REFERENCE - Products
  • Endpoint: GET /products/fees/instances
  • New enum values: TRADE_EWP_BUY and TRADE_EWP_SELL on FeeTriggerEventEnum.
  • Added field: assetType (DigitalAssetTypeEnum, optional) on the fee instance - the asset type the fee applies to.
  • Added field: symbol (string, optional) on the fee instance, e.g. BART. An instance with an assetType and no symbol is the default fee for every symbol of that asset type. An instance with a symbol takes precedence over that default for the same feeTriggerEvent.
  • Behavior change: the eWP ex-ante cost disclosure (POST /wawex/ex-ante) now includes the transaction fee. A BUY shows the entry fee and the expected exit fee, and a SELL shows the redemption fee. On a SELL, the payout is the gross order amount minus the fee and tax.

Changed

Fee Instance feeRatio Precision and Meaning

feeRatio accepts four decimal places, and its description explains how the value is applied.

  • Documentation Location: API REFERENCE - Products
  • Endpoint: GET /products/fees/instances
  • Changed: feeRatio on the fee instance and on its scales - multipleOf relaxed from 0.01 to 0.0001.
  • Changed: description of feeRatio - event-based (trade) fees apply it as a fraction of the order amount (0.0025 = 0.25 %), periodic fees apply it as a percentage. It was previously described as a percentage in all cases.
  • Note: Stored values and fee calculation are unchanged. Only the documented interpretation for trade fees is corrected. Partners that display a trade fee's feeRatio as a percentage should multiply it by 100.

API Rate Limiting

Authenticated partner endpoints are now rate limited. This protects the platform from traffic spikes.

  • Documentation Location: API REFERENCE - all sections
  • Endpoints affected: every authenticated partner endpoint, including the tokenized-asset (/wawex/...) endpoints.
  • Behavior change: each partner can send up to 60 requests per minute to each endpoint, counted in fixed one-minute windows. All API clients of one partner share the same counter. The limit applies separately to every endpoint, so calls to different endpoints do not add up.
  • Behavior change: a request over the limit is rejected with 429 Too Many Requests, a Retry-After header (seconds until the window resets) and the standard error body (message: "rate limit exceeded").
  • Note: Handle 429 by waiting for Retry-After before retrying. Spread bulk jobs (for example mass order placement or polling) over time instead of sending them in one burst.

Two data corrections on the Entities API. The response schema does not change.

  • Documentation Location: API REFERENCE - Entities
  • Changed: createdOn on natural persons and legal entities is now the date the entity was created for your partner, not the date it was first created on the platform. A person or company onboarded by more than one partner now shows each partner its own date.
  • Changed: legalEntityStatus values that had wrongly reverted to CREATED are corrected to match the customer's actual status. Queries filtered by legalEntityStatus can return different results after deployment.

eWP Ex-ante Disclaimer - Holding Period

The eWP ex-ante disclaimer text now matches the 1-year cost projection introduced in v.2.13.0.

  • Documentation Location: API REFERENCE - Trading - Tokenized Assets
  • Endpoint: POST /wawex/ex-ante
  • Changed: metaInfo.disclaimer for eWP symbols now states a holding period of 1 year, matching costs.holdingPeriod.years. It previously referred to five years. Tracker-certificate and traditional-asset disclaimers are unchanged.