API documentation Cobalt standards
Guys, is there any API documentation Cobalt standarts? I've found that DataRoom and many others use API Explorer which has generator tool for Java-based services only. Is there anything for .Net based? I've also found [guidelines][1] that suggest using Swagger. But it will be hardly incorporated into API explorer. What is the most modern way of providing REST service documentation? [1]:
https://thehub.thomsonreuters.com/docs/DOC-588087
https://thehub.thomsonreuters.com/docs/DOC-588087
Tagged:
1
Best Answer
-
Hey Pavel, You've found the two "standards" we have in TR, API Explorer and Swagger. If you are developing within the Cobalt ecosystem I highly recommend looking at API Explorer. It has some enhancements above and beyond Swagger to help you manage people consuming your APIs (eg: endpoint status like "under development", "released" and "deprecated") and ease of integrating some sort of authentication specific to TR like OnePass for example. It is actively supported by the Co-CommonModules-Dev development group. If you have a need that it doesn't support at the moment that team can help. As for .NET support, we are just finishing up .NET support. I'm not sure of all the details, but I'd reach out to the Co-CommonModules-Dev email group and someone there can help you. Like Swagger, there's a standard JSON structure to define your endpoint, so the only question is how to generate that JSON from various technologies. For more info on API Explorer you can also go to their [Hub Page][1] Swagger is a good and useful tool as well. It just follows a different paradigm than API explorer. This my guess, but if Swagger were to support some of the added features that many of the teams use on API Explorer, these two tools would converge in some way. [1]:
https://thehub.thomsonreuters.com/docs/DOC-6762554
Answers
-
This is not an answer, but a follow up question: Is there any standard as far as where the docs are located / how they are accessed. One central place would make the most sense, but that doesn't seem to be the case.1
-
"As for .NET support, we are just finishing up .NET support." - is there any time line or a page on the hub with details?0
-
Some updates on this. Guys have implemented tool and libraries for .Net support of API Explorer. More details here
https://thehub.thomsonreuters.com/docs/DOC-8729800
Categories
- All Categories
- 6 AHS
- 39 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 中文论坛