API result fields in a different order

Hello Team,
A client is asking why the instruments and fields received from an extraction, in some case they are shuffled or in a different order as when the API was made.
Example:
API call sent with MXN=, EUR=, GBP=, COP= in this order, and the results came back with GBP=, MXN=, EUR=, COP=
Thanks in advance!
Answers
-
Hello @Harold.Alfaro
The question isn't clear - are you referring to multiple calls, one for each instrument, or a single API call with multiple instruments. Please share the API call details,
0 -
Hi Gurpreet, sorry if it wasn´t clear enough.
It´s a single API call with multiple instruments where the call was sent with the instruments in a specific order and when the results came back, they were in a different order.
Same thing with the fields… Let´s say I send an API call with the following fields in this order: Instrument ID, Trade Date, Close Price, and when the results came back it shows Trade Date, Instrument ID, Close Price.
Hope this clarifies.
0 -
Since you haven't posted the API call, I presume that you are using the IdentifierList with multiple InstrumentIdentifiers. The data from identifiers might be in different order, since there might be multiple rows of data associated with each. I tried a quick test with the TimeAndSales ExtractionRequest, and see that the field order was preserved.
If there is a request to change the message structure, you should raise it up to the product team for the product enhancement.
0 -
Here is an example
From what you are saying, the system will retrieve the data as it is found in the server and not how it is requested in the API call. Am I correct?
0 -
I tried the exact request message, and received the fields and instruments in the order as requested. What is the response message that you are getting?
Either way, trying to rely on the order while extracting data for an instrument would be a poor programming choice. The app should get the instrument name from the response JSON object, and then extract the pricing data from that same object.
1 -
Thank you, Gurpreet!
No error or warning messages in the extraction notes.
I think I was able to figure out the client´s request… There are two legacy RICs that are not current and those are the ones showing in a different order.
API results put those RICs (HKR= and VEF=) at the end of the results when in fact they aren´t at the moment of submitting the request.
The reason for those instruments moved to the end, is because there is no current data available? Can you confirm?
0 -
Yes, that seems to be the reason.
0 -
Thank you!
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 37 Alpha
- 167 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 707 Datastream
- 1.5K DSS
- 633 Eikon COM
- 5.3K Eikon Data APIs
- 14 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 6 Trading API
- 3K Elektron
- 1.5K EMA
- 259 ETA
- 570 WebSocket API
- 41 FX Venues
- 16 FX Market Data
- 2 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 26 Messenger Bot
- 4 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 284 Open PermID
- 47 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 25 RDMS
- 2.2K Refinitiv Data Platform
- 8 CFS Bulk File/TM3
- 901 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 27 DACS Station
- 126 Open DACS
- 1.1K RFA
- 108 UPA
- 196 TREP Infrastructure
- 232 TRKD
- 921 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 106 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛