Saxo Bank to implement changes to use of Extended AssetTypes
Multi-asset investment specialist Saxo Bank has announced planned changes to the use of Extended AssetTypes in OpenAPI.
After introducing Extended AssetTypes more than two years ago, the company is now ready to deprecate the old AssetTypes and this means everybody will start receiving the new set of Extended AssetTypes starting from December 2023.
This will affect a lot of applications, so users are advised to make sure to carefully check whether or not their application will be impacted by this.
When your application calls OpenAPI, the API will check if your application has been configured to work with the new extended AssetType definition.
You will NOT be impacted by this if either:
- you already know that you receive the new AssetTypes today, i.e. Etf, Etn, Etc, Funds or Rights, then your app is already enabled for Extended AssetTypes and don’t need to make any changes.
- you don’t trade or hold any instrument with AssetType of Stock today. Only the AssetTypes listed in the table above will be impacted, so for other instruments it doesn’t matter; even if you haven’t been enabled for Extended AssetTypes yet.
- searching for the new AssetTypes returns any results: `GET ref/v1/instruments?AssetTypes=Etf,Etc,Etn,Fund,Rights,CfdOnEtf,CfdOnEtc,CfdOnEtn,CfdOnFund,CfdOnRights,SrdOnEtf` (make sure to use an access token belonging to your live application, NOT the 24 hour token from the developer portal).
- looking up the example instruments from the above tables returns the AssetType value listed under “Extended AssetType Definition”.
You WILL be impacted if any of the following is true:
- you know that you trade instruments of type ETF, ETN, ETC, Funds or Rights, but they have the AssetType “Stock” on OpenAPI.
- looking up the example instruments from the above tables returns the AssetType value listed under “Current AssetType Definition”.
The new asset type definition will be present across all OpenAPI endpoints.
The biggest difference and benefit of switching to Extended AssetTypes will be noted when searching for instruments. Limiting a search to just “Stock” will lead to a smaller search result. To get the old behavior (that we don’t expect you will want) your code will have to provide the full range of the new AssetTypes.
You can try out Extended AssetTypes with your app before it’s permanently enabled by adding a Pragma header to the request with the value “oapi-x-extasset” (i.e. ‘Pragma: “oapi-x-extasset”‘). This header has the same effect as the app setting for Extended AssetTypes, so you can test the behavior with your app.
Once – after thorough testing – you are ready to switch your application to the Extended AssetType definition, then:
- If you are a partner and Saxo has configured your application, please reach out to Saxo to request a configuration change.
- If you are an individual developer, please use the self service capability of the developer portal to create a new application.