v.2.17.0 - Test Environment

2026-11-24 - Planned deployment to Live

2026-11-12 - Test Environment

Added

Entities - Status Reasons

Partners can now read why an entity or one of its processes is in its current status, without having to keep every webhook they received.

• Documentation Location: API REFERENCE - Entities
• New Endpoint: GET /entities/status-reasons/{entityId} - the recorded status reasons of a natural person, legal entity or customer, newest first.
• Payload includes: scope (NATURAL_PERSON, LEGAL_ENTITY, ONBOARDING, IDENTIFICATION_VERIFICATION, OFFBOARDING), referenceId (the onboarding, offboarding or identification verification ID), status, reason (errorType, description), validationErrors (onboardings only), notificationType (for example CREATED, UPDATED, VALIDATION_ERROR, APPROVED, REJECTED) and timestamp.
• Paging: limit from 1 to 100 (default 20) and cursor. Use the cursor returned in pagination to read older records.
• Note: each record carries the same information as the webhook sent for that status change. The newest record per scope gives the reason for the current status. Records exist only for status changes made after this release; an unknown entity, or one whose status has not changed since, returns an empty list.

Traditional Assets - Filter by Several ISINs

Partners can now look up several traditional assets in one request instead of one request per ISIN.

• Documentation Location: API REFERENCE - Trading - Traditional Assets
• Endpoint: GET /traditional/assets
• New query parameter: isins - up to 100 ISINs as one comma-separated value, for example isins=IE00B4L5Y983,US0378331005. Repeated keys (isins=A&isins=B) and bracket notation (isins[]=A) are not supported.
• Note: ISINs that are unknown or do not match the other filters are left out of the response without an error. Results are sorted by ISIN and paged by limit, so send a limit at least as large as the number of ISINs to get all of them in one response. If isin and isins are both sent, an asset matching any of the given ISINs is returned. isins combines with all other filters.

Corporate Actions - Dividend with Options (DVOP)

Dividends with options (event type DVOP) now carry their own data: the options offered to the customer and, once confirmed, the option that was applied and its result.

• Documentation Location: API REFERENCE - Trading - Corporate Actions
• Endpoint: publishMT564 (PublishMT564Request) and publishMT566 (PublishMT566Request)
• Added field: dividendWithOptionsData on PublishMT564Request - responseDeadline, defaultOption, grossAmountPerShare and originalCurrency of the CASH option, ratioFrom and ratioTo of the STOCK option, and exchangeRate (required when originalCurrency is not EUR). When defaultOption is omitted, no option is marked as default.
• Added field: dividendWithOptionsResultData on PublishMT566Request - confirmedOption, and for a confirmed CASH option grossAmountPerShare, originalCurrency, taxPercent and exchangeRate; for a confirmed STOCK option ratioFrom, ratioTo, postedShares and fractionalCashAmount (cash in lieu of fractional shares).
• New enum value: OTHER on CorporateActionOptionEnum. It is reserved: the API does not return it and it cannot be submitted as an election. NONE, CASH and STOCK are unchanged.

Corporate Actions - New Event Types

Six more corporate action event types are now recognised and can appear in corporate action data.

• Documentation Location: API REFERENCE - Trading - Corporate Actions; API REFERENCE - Webhooks; API REFERENCE - Transaction History
• New enum values: SOFF, MRGR, CHAN, INSL, EXPR and RHTS on CorporateActionEventTypeEnum (corporate action endpoints, the corporate action webhook and corporate action items of the transaction history).
• Note: existing values are unchanged. If you validate the event type against a fixed list, add the new values so that responses and webhooks containing them are not rejected by your integration.

Changed

Entities - Trading Experience of Less Than One Year

A customer with less than one year of trading experience can now report 0 years.

• Documentation Location: API REFERENCE - Entities
• Endpoints: POST /entities/natural-persons/{naturalPersonId}/trading-profile/asset-types/{assetType} and PATCH /entities/natural-persons/{naturalPersonId}/trading-profile/asset-types/{assetType}
• Changed: yearsOfExperience in tradingExperience accepts 0, meaning less than one full year. This replaces the v.2.16.0 rule that it must be greater than 0 and that less than one year is reported as 1.
• Note: numberOfTrades and tradeVolume must still be greater than 0. A customer without trading experience still sends hasExperience: false and omits tradingExperience.

Entities - Invalid Paging Cursor

An entity list request with a cursor that does not belong to the requesting partner now returns a client error instead of a server error.

• Documentation Location: API REFERENCE - Entities
• Endpoint: GET /entities
• Behavior change: a cursor that was not issued to the requesting partner, or cannot be read, is rejected with 400 Bad Request. Before, the request failed with 500 Internal Server Error.
• Note: always pass back the cursor exactly as returned in pagination of your previous request.

Documentation

Tokenized Assets - Ex-Ante Receipt Still Being Generated (Preview)

The ex-ante cost disclosure PDF is generated asynchronously after the ex-ante is created. On Test, a request made before the PDF is ready now says so instead of answering 404.

• Status: active on the Test environment from this release. On Live the endpoint keeps answering 404 while the PDF is being generated; activation on Live will be announced in a later release.
• Available Endpoints:
  • GET /wawex/ex-ante/{exAnteId}/receipt - returns 202 Accepted with an empty body and a Retry-After header (seconds) while the PDF is still being generated. Retry after that many seconds until you receive 200 with the PDF. An unknown exAnteId, or one created by another partner, returns 404.
• Documentation Location: API REFERENCE - Trading - Tokenized Assets