REDI CacheControl Cell Names List
Hello! I am using the C# example programs (REDIConsoleOrders from Github) as a template, and I am trying to subscribe to all system behavior for a group a traders. That is working as expected.
I am, however, confused about the names used to denote the "cells" available when calling CacheControl.GetCell. I have written a unit test that pulls all of the names listed in Appendix 2 (page 51) of the API document (version 2.4), and those work.
My confusion comes from the example code - it calls GetCell with fields that are not listed in the API documentation, and those work! Some examples are: "PriceDesc", "Leaves", and "Status". These do not cause errors like a call with a fake cell name would, which indicated to me that there are additional fields.
Is there a more accurate list of the fields available through CacheControl, or perhaps a method for enumerating them in code? I am looking to fulfill another API's requirements for fields, and any additional information I can pull from the trade activity would be helpful.
I am referencing the document "REDI API Specification, Version 2.4, dated 3 December 2019.
Thanks!
Best Answer
-
Hello @William McBurnett,
REDI Spec is the most comprehensive document on the subject. It's a work in progress, however, in that the most popular use case fields are included, not all.
One can further understand API usage from REDI Tutorials, the example on GitHub is a companion example.
I do not think the way exists to enumerate all table fields, and this set s not fully static, new versions bring improvements to the field availability.
To pinpoint a field you would like to use, I would suggest
- Going through REDIPlus desktop menu
- Management -> Message Monitor
- Select Order tab
- Right-mouse-click
- select Edit Fields option
- Add the field to your order layout and observe the value in the field for your existent orders/test orders.
This allows to determine if the field you have is what you are looking for or it is not. Once confirmed on the value, the field may not be called identically for API access, often is, if not, is usually close, and is possible to guess. If this is not the case, please let us know here and we will try to help identify the field name.
I hope this helps
1
Answers
-
Roger, that makes some sense. I will explore that.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛