OpenAPI

Chart service has few v0 endpoints with sole purpose to support ChartFeedExtenstion (CFE). These are used by ITBS or CFE team as there is no involvement of OpenApi in these other than providing a platform to do configuration changes in CFE. 

These can be called as below, using a http client like fiddler, postman, curl or powershell. Http header x-internal-ip with value 1 should be added to all requests that are internal to saxo network.

  • FlushInstrument - This endpoint can be called within Saxo network only. It allows anonymous calls so an access token is not needed to call it.
    • Sample url: http://<servername>/sim/openapi/chart/chart/FlushInstrument?symbol=<symbol>

  • FlushTopic - This endpoint can be called within Saxo network only. It allows anonymous calls so an access token is not needed to call it.
    • Sample url: http://<servername>/sim/openapi/chart/chart/FlushTopic?topic=<int>
      The topic in above request is a integer from an enum in CFE which represents asset class.

  • SetTraceStatus - This endpoint can be called within Saxo network only. It allows anonymous calls so an access token is not needed to call it.
    • Sample url : http://<servername>/sim/openapi/chart/chart/SetTraceStatus?status=<boolean>&symbol=<symbol>&horizon=<horizon>
      status should be true to enable trace and false to disable it.
      symbol is the instrument symbol to enable/disable trace on.
      horizon represents time horizon for which trace is toggled.
  • GetClientConfig - This is a public endpoint. It allows anonymous calls so an access token is not needed to call it.
    • Sample url: http://<servername>/sim/openapi/chart/chart/GetClientConfig
      Returns client configuration data from CFE.
  • ChartStatus - This endpoint can be called within Saxo network only. It allows anonymous calls so an access token is not needed to call it.
    • Sample url: http://<servername>/sim/openapi/chart/chart/ChartStatus
      Return CFE status data.

Chart v0 is supposed to removed so these have been marked as obsolete in documentation, but are still used. Ideally OpenApi should not be involved in configuration of CFE and it should be done using some other tool to manage applications like CAAdmin / FOC etc. However, this is done historically and should at some point be transferred to ChartFeed team.