What encoding to assume for files retrieved from CFS API?

ibby
ibby Newcomer
edited April 8 in Eikon Data APIs

Hi,

What encoding should be assumed for .txt.gz files retrieved from the Client File Store (CFS) API?

E.g., a request made to the following endpoint: https://api.refinitiv.com/file-store/v1/files/{fileId}/stream?doNotRedirect=true

… returns response headers:

x-amz-id-2: REDACTED
x-amz-request-id: REDACTED
Date: Fri, 04 Apr 2025 14:03:21 GMT
Last-Modified: Mon, 09 Dec 2024 11:35:19 GMT
ETag: REDACTED
x-amz-server-side-encryption: AES256
x-amz-version-id: REDACTED
Accept-Ranges: bytes
Content-Type: binary/octet-stream
Content-Length: 225930
Server: AmazonS3

… decompress response bytes content with gzip lib results in bytes content…

… decode bytes content with encoding (which one?) results in text content…

UTF-8 seems to work, but it would be prudent to have some guarantee of encoding, even if it's just in your API docs…

Answers

  • Hello @ibby

    Let me check with the CFS API team and get back to you.

  • Hello @ibby

    The CFS API team confirms that the file is encoding in UTF-8 format.