Breaking - Moving address of websocket streaming (From December 2025)
The underlying architecture supporting websocket streaming is being upgraded. As a result, we are releasing a new address used for the websocket connection and re-authorization.
| Simulation | Live | |
|---|---|---|
| To be deprecated | streaming.saxobank.com/sim/openapi/streamingws | streaming.saxobank.com/openapi/streamingws |
| Newly released | sim-streaming.saxobank.com/sim/oapi/streaming/ws | live-streaming.saxobank.com/oapi/streaming/ws |
The current domain and addresses used for websocket connections will be deprecated after 3 months, on the 6th of December, 2025.
The /connect and /authorize end paths used on these addresses are unchanged
The delivered websocket data messages and control are identical between the deprecated and newly released version
HTTP Requests to create, update, and delete subscriptions are unchanged
Due to the possibility that the technical architecture changes may reject previously accepted (but invalid) requests to create or re-authorize websocket connections it is imperative that your application implements and tests these new domains well before the deprecation date. As always, it is highly recommended to first implement these changes on simulation first!
In the unlikely event that your team experiences difficulties migrating to the new domain and addresses
- Reviewing the exact implementation documentation provided here: Streaming
- Ensuring all relevant domains and addresses have been updated in your code-base.
- Ensuring that the origin of the issue is not an authentication issue.
- Review your own implementation to ensure no unexpected headers or query parameters are being included by mistake.
- Review our websocket samples, which have been updated for all of our language samples:
If you are unable to resolve the migration after the above steps, please reach out to our team with the following information:
- Your Application Name or Key
- Context to how the application is creating a websocket connection
- The status code returned from the failed connection
- All request and response headers when attempting the connection
Breaking - New Mandatory NatureOfBusinessWithCategory property for onboarding clients via OpenAPI (From December 2025)
A new field has been added to signups which will become required once this change is done. Read more about the field and how to correctly implement it here: Breaking Change - New Nature of Business with Category for IB Onboarding
Breaking - Removal of obsolete attributes on portfolio's Account resources (From September 2025)
On the endpoints:
- port/v1/accounts
- port/v1/accounts/{AccountKey}
The fields "DirectMarketAccess" and "DirectMarketExchangeIds" are being removed. They will not be replaced by other fields.
Breaking - Enforcement of pre-trade disclaimers (from May 2025)
Handling of pre-trade disclaimers will become mandatory for all OpenAPI apps from May 2025, so it's important to implement proper support for it in your OpenAPI Application as soon as possible.
Read more about this change here: Breaking Change - Pre-Trade Disclaimers on OpenAPI
Failure to properly handle pre-trade disclaimers in your application will lead to orders being rejected. Even if no disclaimers are present for your user at this time, they can be added at any time without warning.
RELEASED CHANGES
The list of completed changes can be found here