IPA Financial Contracts for Fx Cross api - error responses
I am using the IPA Financial Contracts for Fx Cross api to resolve Fx prices.
I have made the same request (see payload below) several times over a period of 2-3 hours. Sometimes I receive an error response, sometimes I get a successful response.
The error response was: QPS-Pricer.8020:Market data: No Fx Spot Point available. Fx Spot is N/A for the cross code 'GBPUSD'.
Do you know what this message means and why I might get it periodically?
I am testing the system with many requests (in the region of 3000 fx prices).
The payload is this:
{
"instrumentDefinition": {
"fxCrossCode": "USDGBP",
"fxCrossType": "FxForward",
"instrumentTag": "12908240928_USDGBP",
"legs": [
{
"fxLegType": "FxForward",
"endDate": "2024-03-05"
}
]
},
"instrumentType": "FxCross",
"pricingParameters": {
"isIntraday": true,
"priceSide": "Ask",
"valuationDate": "2023-12-15T16:17:01"
}
}
Many Thanks...
Best Answer
-
Hello @david.p.newman ,
It seems the Fx spot USDGBP was not found during the pricing.
Next time please Add ErrorMessage in the request fields we will get more details about the error.
Also, if you have the request id we can look into the logs:
{ "outputs": [ "Headers", "Data", "Statuses" ], "fields": [ "FxSpot", "ErrorCode", "ErrorMessage" ], "universe": [ { "instrumentDefinition": { "fxCrossCode": "USDGBP", "fxCrossType": "FxForward", "instrumentTag": "12908240928_USDGBP", "legs": [ { "fxLegType": "FxForward", "endDate": "2024-03-05" } ] }, "instrumentType": "FxCross", "pricingParameters": { "isIntraday": true, "priceSide": "Ask", "valuationDate": "2023-12-15T16:17:01" } } ] }
1
Answers
-
Okay, thanks for the info. I will start tracking the request id from now on so we can get better information about what went wrong.
I didn't make it clear in my initial message that I was including the "ErrorMessage" in the request fields. The code and the message were as per my initial message.
The error code and message:
QPS-Pricer.8020: Market data: No Fx Spot Point available. Fx Spot is N/A for the cross code 'GBPUSD'.
Here is the full payload:{
"fields": [
"InstrumentTag",
"ValuationDate",
"InstrumentDescription",
"FxOutrightCcy1Ccy2",
"ErrorCode",
"ErrorMessage",
"FxCrossScalingFactor",
"FxSpot",
"FxCrossType"
],
"outputs": [
"Data",
"Headers"
],
"universe": [
{
"instrumentDefinition": {
"fxCrossCode": "USDGBP",
"fxCrossType": "FxForward",
"instrumentTag": "12908240928_USDGBP",
"legs": [
{
"fxLegType": "FxForward",
"endDate": "2024-03-05"
}
]
},
"instrumentType": "FxCross",
"pricingParameters": {
"isIntraday": true,
"priceSide": "Ask",
"valuationDate": "2023-12-15T16:17:01"
}
}
]
}0 -
Hi, you referred to the request id in your message. Is this the http header "x-tr-requestid"? There is also an operationid on the async api (i.e. specified in the location header). Is this useful for analysing issues with your team also? Which is best? Many Thanks.
0 -
Just noticed that in the async method the "operationid" is the same as the "requestid" in the initiating request. We will look to capture that and get back to you. Thanks.
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 中文论坛