I have a client with the Contact name: Daniel Clayton and Account Name: UNIVERSITY OF WARWICK.
This is for Case 16490207.
The client is having trouble with their API Script, yet upon confirming client has delay access to the RIC ABT and KHC.
What we have suggested for querying delayed instruments, the delayed RIC format should be used. Kindly update the script to use:
/ABT
/KHC
Below is what client had mentioned:
----
Below are the request bodies and the relevant excerpts from the scripts that actually made the two Discovery Symbology calls. I have removed authentication, headers, local paths and execution-control details. The excerpts are therefore not executable as pasted. Both calls went through the Workspace Desktop API’s local /api/rdp/discovery/symbology/v1/lookup route. Neither used a RIC as its input.
ABT — quote PermID to ISIN history
The exact request body was:
{"from":[{"objectTypes":["anyquote"],"identifierTypes":["PermID"],"values":["55838984319"]}],"to":[{"identifierTypes":["ISIN"]}],"type":"auto","showHistory":true}
The relevant executed script lines were:
# Authentication, safeguards and local paths omitted
time.sleep(1.25)
request = build_exact_sdk_request(Request, BODY)
service.request(request)
# Relevant lines in build_exact_sdk_request;
# the body-length and hash check between these lines is omitted
body = staged_body_path.read_bytes()
return sdk_request_class(
url=[redacted local Workspace proxy URL], method="POST",
headers=[redacted request headers],
data=body, json=None, auto_retry=False, timeout=30,
)
The response on 14 October 2026 was HTTP 200 but returned output: [], item error USER_NOT_ENTITLED_FOR_IDENTIFIER for ISIN, and top-level error ACCOUNT_NOT_ENTITLED_TO_IDENTIFIER_TYPES. The response identified the input as EdfQuote/PermID. Its provider requestId was 731ce279-2257-46dd-a711-3ae0bc44af34; the transport x-request-id was 18eecd66-0a1f-4d95-99f2-80771c06614f. The response carried effectiveAt=2026-10-14T06:21:17.738Z.
KHC — quote PermID to instrument ISIN at a historical instant
The exact request body was:
{"from":[{"identifierTypes":["PermID"],"objectTypes":["EdfQuote"],"values":["21566906321"]}],"to":[{"identifierTypes":["Isin"],"objectTypes":["EDInstrument"]}],"type":"auto","effectiveAt":"2023-01-04T16:00:00.000Z"}
The relevant executed script lines were:
# Authentication, safeguards, headers and local paths omitted
time.sleep(1.25)
request = Request(url=[redacted local Workspace proxy URL], method="POST",
headers=[redacted request headers],
data=BODY, json=None, auto_retry=False, timeout=30)
service.request(request)
The response observed on 14 October 2026 at approximately 09:47:08 UTC was HTTP 200 but returned output: [], item error USER_NOT_ENTITLED_FOR_IDENTIFIER for Isin, and top-level error ACCOUNT_NOT_ENTITLED_TO_IDENTIFIER_TYPES. Its provider requestId was 00a22f37-1d01-4f92-b694-7c54dd1820a1; the transport x-request-id was 736404c1-623a-419a-a50c-3d5a6262bb99. The returned effectiveAt=2023-01-04T16:00:00.000Z is the requested historical instant, not a returned ISIN relationship.
These were script-run calls. We have the saved request and response records, but no verified contemporaneous Workspace UI screenshot of either execution, so I do not want to present another image as though it captured these calls.
--------
Can you please confirm on why the client is experiencing the error and what should be the correction done for this? Thank you and we really appreciate your assistance on this.
