Camel Case syntax for DataScope Select API request

Anirudh Vishnubhatla

Hello Team,

Client has raised a concern with the JSON format of request sent and response received where when the client was trying to follow the JSON valid format of Camel case, the API request was giving an error.

Sample Query has been provided in the attached excel.

When client changes the initial syntax for the API request to camel case, they are getting an error.

JSON syntax being used:

{  "ExtractionRequest": {
Client's expectation:
{  "extractionRequest": {

The error that the client is receiving when modifying the API request is:

{    "error": {        "message": "Malformed request payload: Syntax error at Line 2, Char 23: expected valid json value \"extractionRequest\":"    }}

As per client, standard JSON request should accept Camel case as well. However, for our DSS API, this syntax is returning an error.

Client wants to know if we can make the request using the Camel case format on DSS API.

14514871 JSON Request.txt

Gurpreet

https://community.developers.refinitiv.com/discussion/comment/124584#Comment_124584

Hello Ranita,

1. JSON Standards in API Requests & Responses

The request fields should ideally follow camelCase, but DSS APIs only accept PascalCase.

The response fields are also in PascalCase and contain spaces, which deviates from standard JSON formatting.

There is no standard case format for JSON - please refer to the JSON specification document. Industry uses all types of string cases and they all are acceptable. For e.g. Google REST uses camelCase while X API uses snake_case.

There is no immediate plan to modify the DSS API structure.

Jirapongse

@Anirudh Vishnubhatla

Thank you for reaching out to us.

It looks like the Datascope Select's request message is case sensitive.

Please contact the DSS support team directly via MyAcount to verify this behavior.

Ranita

Hi,

We are working on integrations with DSS APIs and have observed that the request and response fields do not follow standard JSON conventions. Below are our key concerns:

1. JSON Standards in API Requests & Responses

• The request fields should ideally follow camelCase, but DSS APIs only accept PascalCase.
• The response fields are also in PascalCase and contain spaces, which deviates from standard JSON formatting.
• We would like to understand whether this issue exists only in the Dev environment or if it is the same in Production as well.
• Additionally, is there a possibility of modifying the API request and response structures in the near future to align with standard JSON practices?

2. Environment-Specific API Endpoints & Credentials

• Could you provide the endpoints for the Dev, Test, and Production environments that we need to integrate with?
• We specifically require the environment-specific endpoints and credentials for:
  • DSS On-Demand API
  • Authentication Token Retrieval API

3. Request for Developer Discussion

• Would it be possible to connect with a DSS API Developer to discuss these concerns in more detail?
• We would appreciate the opportunity to set up a meeting at a mutually convenient time to go over these issues.

Looking forward to your response.

Best regards,
Ranita Ghosh Dastidar,
On Behalf of Stanmore Resources, Australia

Jirapongse

https://community.developers.refinitiv.com/discussion/comment/124584#Comment_124584

• JSON Standards in API Requests & Responses

• Please contact the DSS product support team via MyAccount to verify this. Therefore, you can directly discuss this requirement with the product team. From my test, it looks like the Datascope Select's request message is case sensitive.

Environment-Specific API Endpoints & Credentials
As far as I know, we only provide the production enviornment (https://selectapi.datascope.refinitiv.com/RestApi/v1/).

Request for Developer Discussion
Please contact your LSEG account team or Sales team directly for any further discussions.
We provide documents, examples, and tutorials on the LSEG developers community.