Extended AssetTypes
This sample demonstrates the change which will happen once Extended AssetTypes are rolled out, and is meant to help test and verify the new behavoir in your application before the change happens.
You can find more information about the change here: https://www.developer.saxo/openapi/learn/extended-assettypes
You can request to get Extended AssetTypes by sending an extra header, the "Pragma" header oapi-x-extasset. This header makes the app behave like it is on Extended AssetTypes.
After a successful test, you can create a new app, so the AssetTypes are extended by default.
Using the oapi-x-extasset header
It is possible for an application that is not yet enabled for Extended AssetTypes to instruct OpenApi to act as if the application was configured for the Extended AssetType 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. This header can be used for validation, but also to have groups of customers on Extended AssetTypes, and others on the legacy AssetTypes.
Response:
Click button to launch function.
JS code:
Click button to show code.