question

Upvotes
Accepted

Mapping logic between input column name (request) and output column name (csv) in Tick History API

Hi Team,


May we know the mapping logic between input column name (request) and output column name (csv) in Tick History API?


As this is API, it has programmatic rules in place on your side which determine the column order on your return payload. Also, the dev team constructs a CSV file with the available input column names which are numbered, could it be that the numeric of this indicate the order that the payload will arrive it?


May we know the logic on how you determine your column order on the return please.


Thank you.

#productapitrth-rest-apicsv
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
78.6k 248 52 74

@heatherashley.francisco

Thank you for reaching out to us.

If you would like to know the internal logic in Tick History, please contact the Refinitiv Tick History support team directly via MyRefinitiv.

However, it is better to rely on the column headers in the CSV file instead of the numbered columns

1692584303642.png



1692584303642.png (30.5 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.