Stocks become Stocks, ETFs, ETCs and ETNs
Currently, all apps are build for the "old" list of AssetTypes. Saxo plans to introduce more AssetTypes. This can be a breaking change, so this is not something just being released. Many endpoints use AssetTypes. The application must be flagged as "Ready for Extended AssetTypes".
You can test if this is the case by sending an extra header, the "Pragma" header oapi-x-extasset.
After a successful test, your app can be converted, so the AssetTypes are extended by default.
If you have no plans for your application to support the new asset types, then the only thing you have to do, is to properly handle the situations where a client has an order or position in an instrument, which is only represented by the new extended asset type, like SRD, or Warrant.
If you plan to migrate your application to support the extended asset types, there are certain steps you can take to make the migration as smooth as possible.
Using the oapi-x-extasset header
It is possible for an application configured for the old definition of AssetType to instruct OpenAPI to act as if the application was configured for the extended asset type definition.
This is done by adding a header named 'Pragma' with the value 'oapi-x-extasset' in the request. Below are some examples of this.
Response:
Click button to launch function.
JS code:
Click button to show code.