What is the COUNT field parameter in get_timeseries for currencies? Or how do i get currency pair...

... volume?
I am searching for currency pair daily traded volume data via the python api. I use the cross rates from the MONEY CROSS/1 guide for all pairs of the currencies: ['AUD','CHF','CNY','EUR','GBP','HKD','INR','JPY','RUB','USD']
The get_timeseries function which i used so far to get currency price time series, does not return VOLUME. i discovered the parameter COUNT which can be inserted for fields. i thought it might be related. can i use it as an equivalent to traded volume (the absolute value does not matter only the proportion relative to other currency pairs must be correct)?
If not, how can i get daily volume, or even better average monthly volume for each currency pair via the python api?
thanks
Best Answer
-
FX instruments such as spot and cross exchange rates are primarily traded over the counter. The quotes you see in FX RICs such as EUR= are indicative rates contributed to Thomson Reuters by market participants (primarily banks). These quotes do not represent actual transactions and that's why there's no volume associated with them. The field COUNT in the timeseries represents the number of quotes received within the time interval. It has nothing to do with traded volume, but in lieu of traded volume data it is the best indicator of the intensity of market activity you can find.
0
Answers
-
Hey Alex,
thanks for your reply. Ok, so what i would like to do now is to find the main (volume-based) trading partner currency for each of the main currencies listed above. I do this by pulling the COUNT-time series for all available currency pairs for each main currency. Then, i take the average over time, in order to get for each currency pair the average daily traded "volume" (AV). I select the currency pair with the highest AV for each main currency, as the "main partner", as listed in the table.
As you can see in the table, it turns out, that each of the currencies has as main partner GBP, which is surprising. I would have thought of EUR, USD in most cases. Do you think it is realistic? Probably, this is due to submission of many HFT orders in GBP?
Would there be any other way to get the real volume-based main trading partners for the bold currencies in the table?
Thank you
Best,
JC
0 -
No, your conclusion is not realistic. You're right that for most currencies the main "trading partner" is USD. The main flaw I can see in your methodology is the RICs you used. "*=R" RICs for cross exchange rates such as "GBPAUD=R" are not contributed by market participants, but calculated by Thomson Reuters from the spot rates. Note that in your calculation GBPEUR and EURGBP pairs get the same number of updates, although only EURGBP is conventional and actively traded in the FX market. If the number of updates per day on "GBPAUD=R" is an indicator of anything, then it's an indicator of market activity in GBPUSD and AUDUSD currency pairs, not in GBPAUD. Even then it's not a good indicator because Thomson Reuters applies a level of throttling when calculating cross exchange rates. To gauge market activity in GBPAUD or another currency pair you need to use "*=" RICs, e.g. "GBPAUD=". These quotes are directly contributed to Thomson Reuters by market participants.
I'm not aware of any source that could provide actual traded volumes for currency pairs in the FX market. Maybe SWIFT has this data. I'm not sure. I certainly cannot think of any market data vendor that could supply this.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 685 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 252 ETA
- 556 WebSocket API
- 38 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 652 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- 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
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛