Get data for USD1MFSR=

I could replicate the Error: socket hang up issue on my machine. I set up a proxy on my local machine by using https://mitmproxy.org/.

Then, I configured postman to connect to this local proxy. Next, I sent an extraction request to the DSS via the local proxy. While the postman was waiting for the response, I shut down the local proxy.

Finally, I got the following error.

You may check with the proxy team if the proxy cut the connection.

Otherwise, You may try using the postman without the proxy.

All comments

For the Error: socket hang up issue, it could be a network or proxy issue. Please contact your local IT support team to verify the connection.

For the EndOfDayPricingExtractionRequest, I checked the description in Notes in the response and found the "row suppressed for lack of 'ICE LIBOR' permission". Please contact your Customer Success Manager to verify the permission.

Dear @Jirapongse thank you for your answer.

I'm afraid it is not a proxy issue. We are able to receive response for IntraDayPricing and EndOfDayPricing just not for USD1MFSR=.

We have contacted @Zlatko.Zlatkov before posting here and we have all the required permissions.

Sorry. I am unable to replicate the "socket hang up" issue. I can retrieve the data properly.

It could be a network issue.

For the EndOfDayPricingExtractionRequest, I got the same message in the response.

You can contact the Refinitiv DataScope Select support team directly via MyRefintiv to verify the "socket hang up" issue and the meaning of the 'ICE LIBOR" permission.

I tried again and got the results back. I don't know what to say... Maybe it's the time of calling due to embargo... I'll try to call again a couple of times during the day... Thank you very much for helping.

oh well... i just tried again multiple times and most of the time I receive socket hang up. I'm guessing it's due to Refinitivs servers overload? Is there a platform where we can report such behavior in order for them to check?

raksina.samasiri

hi @mitja.mavser ,

As mentioned by @Jirapongse in the comment above,

You can contact the Refinitiv DataScope Select support team directly via MyRefintiv to verify the "socket hang up" issue and the meaning of the 'ICE LIBOR" permission.

It may relate to the Embargo period. Please add {"OnlyNonEmbargoedData":true} in the condition.

{
    "ExtractionRequest": {
        "@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.IntradayPricingExtractionRequest",
        "ContentFieldNames": [
            "Bid Price",
            "Ask Price"
        ],
        "IdentifierList": {
            "@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
            "InstrumentIdentifiers": [
                {
                    "Identifier": "USD1MFSR=",
                    "IdentifierType": "Ric"
                }
            ]
        },
        "Condition": {"OnlyNonEmbargoedData":true}
    }
}

I'm afraid we didn't receive any solution even from support and decided to find another provider. Thank you all for trying to help.

raksina.samasiri

Hi @mitja.mavser,

As checked in the case you raised, a single quote is missing at almost the end of the URL you used to request the data, like, https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractWithNotesResult(ExtractionId='xxxxxxxxx')

Could you please try calling it again with the single quote and let me know if the error still persists.

I tried to reproduce an error (both with and without "Condition": {"OnlyNonEmbargoedData":true}, as suggested by Jirapongse) but I haven't got an error "socket hang up" (I've retried several times). However, I tried with the "Condition": {"OnlyNonEmbargoedData":true} and the Notes in response mentioned that this instrument has no report data. I could raise the support ticket to the content team to verify the no report data of this RIC if you'd like.

Hope this could help

raksina.samasiri

Plus, I tried retrieving the same data using The DSS web GUI (here's more detail about it) and got the same Notes, that the instrument has no reported data.

For more detail about this note, you may check this thread