You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Article.md
+28-28Lines changed: 28 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
-
# A Generic and Step By Step Workflow for RDP Client File Store (CFS) Bulk File API
1
+
# A Generic and Step By Step Workflow for RDP Client File Store (CFS) File API
2
2
3
3
## <aid="intro"></a>Introduction
4
4
5
5
The Client File Store (CFS) is a capability of Refinitiv Data Platform (RDP) that provides authorization and enables access to content files stored in publisher repositories. LSEG provides various content file domains (aka *bucket*) for consumers such as:
6
-
-Bulk ESG data
6
+
-CFS ESG data
7
7
- Green Revenue data
8
8
- Symbology data
9
9
- Tick History
@@ -77,9 +77,9 @@ Please find more detail on the [CFS API User Guide](https://developers.lseg.com/
77
77
78
78
Before I am going further, there is some prerequisite, dependencies, and libraries that the project is needed.
79
79
80
-
### Access to the RDP with the your desire Bulk file permission
80
+
### Access to the RDP with the your desire CFS file permission
81
81
82
-
This project uses RDP access credentials with the CFS Bulk file permission.
82
+
This project uses RDP access credentials with the CFS file permission.
83
83
84
84
Please contact your LSEG representative to help you with the RDP account and the bucket permission.
85
85
@@ -187,7 +187,7 @@ The application then creates a request message in a JSON message format or URL q
187
187
188
188
### Step 2: Listing the packageIds using the Bucket Name
189
189
190
-
Now let me move on to the CFS APIs call. To request the CFS Bulk data, the first step is to send an HTTP ```GET``` request to the RDP ```/file-store/v1/packages?bucketName={bucket-name}``` endpoint to list all Package Ids under the input ```bucket-name```.
190
+
Now let me move on to the CFS APIs call. To request the CFS data, the first step is to send an HTTP ```GET``` request to the RDP ```/file-store/v1/packages?bucketName={bucket-name}``` endpoint to list all Package Ids under the input ```bucket-name```.
191
191
192
192
The HTTP Request structure is as follows:
193
193
@@ -473,7 +473,7 @@ Then you can continue to send requests to URL in ```@nextLink``` node to get the
473
473
474
474
Let’s leave the paging feature there.
475
475
476
-
### Step 4: Get the Bulk file URL on AWS S3
476
+
### Step 4: Get the file URL on AWS S3
477
477
478
478
Now let me turn to getting the file URL on Amazon AWS S3 service with the RDP ```/file-store/v1/files/{file ID}/stream``` endpoint.
That completes how to run an example Jupyter Lab notebook application.
710
710
711
-
### <a id="how_to_run_postman"></a>Run the Postman LSEG CFS Bulk API Workspace
711
+
### <a id="how_to_run_postman"></a>Run the Postman LSEG CFS API Workspace
712
712
713
-
Now let me turn to the Postman collection. The [RDP CFS Bulk Postman Workspace](https://www.postman.com/winter-water-515088/workspace/lseg-cfs-bulk-api-workspace) is a public workspace in Postman that demonstrates how to use CFS API. It contains the following collection and environment:
714
-
- **RDP CFS Bulk API Collection**: This collection contain all HTTP requests with the RDP CFS Bulk file API. The requests are in ordered from Step 1 to Step 5.
715
-
- **RDP CFS Bulk API Environment**: This environment contains all parameters consumers need forrequesting data with the requestsin RDP CFS Bulk API Collection (including the credential).
713
+
Now let me turn to the Postman collection. The [RDP CFS API Postman Workspace](https://www.postman.com/winter-water-515088/workspace/lseg-cfs-api-workspace) is a public workspace in Postman that demonstrates how to use CFS API. It contains the following collection and environment:
714
+
- **RDP CFS API Collection**: This collection contain all HTTP requests with the RDP CFS file API. The requests are in ordered from Step 1 to Step 5.
715
+
- **RDP CFS API Environment**: This environment contains all parameters consumers need forrequesting data with the requestsin RDP CFS API Collection (including the credential).
716
716
717
-
Users can fork these Postman items to their own workspaces. Please follow these five steps to fork the RDP CFS Bulk Postman Workspace to a Postman workspace.
717
+
Users can fork these Postman items to their own workspaces. Please follow these five steps to fork the RDP CFS Postman Workspace to a Postman workspace.
718
718
719
719
#### 1. Create a new Postman workspace
720
720
@@ -734,27 +734,27 @@ The new workspace will appear on the list.
734
734
735
735

736
736
737
-
#### 2. Open the LSEG CFS Bulk API Workspace
737
+
#### 2. Open the LSEG CFS API Workspace
738
738
739
-
The [LSEG CFS Bulk API Workspace](https://www.postman.com/winter-water-515088/workspace/lseg-cfs-bulk-api-workspace) is in the public workspace so you can search it in Postman by clicking on “Search Postman”.
739
+
The [LSEG CFS API Workspace](https://www.postman.com/winter-water-515088/workspace/lseg-cfs-api-workspace) is in the public workspace so you can search it in Postman by clicking on “Search Postman”.
740
740
741
741

742
742
743
-
And then, enter “LSEG CFS Bulk API”.
743
+
And then, enter “LSEG CFS API”.
744
744
745
-

745
+

746
746
747
-
Click on the LSEG CFS Bulk API to open the workspace.
747
+
Click on the LSEG CFS API to open the workspace.
748
748
749
749

750
750
751
-
This LSEG CFS Bulk API workspace will be added to the workspace list.
751
+
This LSEG CFS API workspace will be added to the workspace list.
752
752
753
753

754
754
755
-
#### 3. Fork the RDP CFS Bulk API Collection
755
+
#### 3. Fork the RDP CFS API Collection
756
756
757
-
Select the LSEG CFS Bulk API workspace from the workspace list, and thenselect“...” menu of the RDP CFS Bulk API collection and choose the "Create a fork"command to fork this collection.
757
+
Select the LSEG CFS API workspace from the workspace list, and thenselect“...” menu of the RDP CFS API collection and choose the "Create a fork"command to fork this collection.
@@ -768,7 +768,7 @@ The forked collection will be created in the selected workspace.
768
768
769
769
#### 4. Fork the Environment
770
770
771
-
Select the LSEG CFS Bulk API workspace from the workspace list, and thenselect“...” menu of the RDP CFS Bulk Environment and choose the "Create a fork"command to fork this environment.
771
+
Select the LSEG CFS API workspace from the workspace list, and thenselect“...” menu of the RDP CFS Environment and choose the "Create a fork"command to fork this environment.
@@ -782,7 +782,7 @@ The forked environment will be created in the selected workspace. Input the ```U
782
782
783
783
#### 5. Running Postman Collection
784
784
785
-
The first step is run the "Step 1" Get Access Token using Password Grant (Machine ID)" request, please make sure that the environment on the top right corner is pointed to the RDP CFS Bulk Environment.
785
+
The first step is run the "Step 1" Get Access Token using Password Grant (Machine ID)" request, please make sure that the environment on the top right corner is pointed to the RDP CFS Environment.
786
786
787
787

788
788
@@ -810,14 +810,14 @@ That covers how to run an example Postman collection.
810
810
811
811
## Next Steps
812
812
813
-
That brings me to the end of this CFS Bulk API workflow project. The CFS Bulk API is a powerful API that allows developers to download the content file dynamically via a straightforward sequence of HTTP RESTful API calls. The demonstration code is written in Python but the concept of the API calls steps are the same for other programming languages.
813
+
That brings me to the end of this CFS API workflow project. The CFS API is a powerful API that allows developers to download the content file dynamically via a straightforward sequence of HTTP RESTful API calls. The demonstration code is written in Python but the concept of the API calls steps are the same for other programming languages.
814
814
815
815
At the same time, the [Refinitiv Data Platform (RDP) APIs](https://developers.lseg.com/en/api-catalog/refinitiv-data-platform/refinitiv-data-platform-apis) provide various LSEG data and content for developers via an easy-to-use Web-based API. The APIs are easy to integrate into any application and platform that supports the HTTP protocol and JSON message format.
816
816
817
817
You may interested in the following resources for more detail about the CFS data usage:
818
818
- [Find environmental footprint of your bond portfolio](https://developers.lseg.com/en/article-catalog/article/Environmental_footprint_of_bond_portfolio) article
819
-
- [RDP APIs Green Revenues CFS Bulk file Workflow](https://github.com/LSEG-API-Samples/Example.RDP.Python.GreenRevenuesBulk) - a dedicate Green Revenue CFS workflow
- [RDP APIs Green Revenues CFS file Workflow](https://github.com/LSEG-API-Samples/Example.RDP.Python.GreenRevenuesBulk) - a dedicate Green Revenue CFS workflow
"### Step 2: Listing the Package Ids using the Bucket Name\n",
177
175
"\n",
178
-
"To request the CFS Bulk data, the first step is to send an HTTP ```GET``` request to the RDP ```/file-store/v1/packages?bucketName={bucket-name}``` endpoint to list all Package Ids under the input ```bucket-name```.\n",
176
+
"To request the CFS data, the first step is to send an HTTP ```GET``` request to the RDP ```/file-store/v1/packages?bucketName={bucket-name}``` endpoint to list all Package Ids under the input ```bucket-name```.\n",
179
177
"\n",
180
178
"The HTTP Request structure is as follows:\n",
181
179
"\n",
@@ -454,7 +452,7 @@
454
452
"id": "4d14e355-e213-47ca-a6f4-956bb4c9de0d",
455
453
"metadata": {},
456
454
"source": [
457
-
"### Step 3.5: Listing the FileSets using the Bucket Name - Paging\n",
455
+
"# Step 3.1: Listing the FileSets using the Bucket Name - Paging\n",
458
456
"\n",
459
457
"By default, the ```/file-store/v1/file-sets``` endpoint always returns 25 results per request. You can adjust the number of return results via the ```pageSize``` query parameter, the maximum number is **100**.\n",
460
458
"\n",
@@ -571,6 +569,8 @@
571
569
"source": [
572
570
"Based on the response data above, you see the API returns **2 entries** per request as set via ```pageSize=2``` parameter. \n",
573
571
"\n",
572
+
"# Step 3.2: Listing the FileSets using the Bucket Name - nextLink\n",
573
+
"\n",
574
574
"The ```@nextLink``` node contains the URL for requesting the next page of query as follows:\n",
575
575
"\n",
576
576
"```HTTP\n",
@@ -589,6 +589,7 @@
589
589
"metadata": {},
590
590
"outputs": [],
591
591
"source": [
592
+
"# Step 3.2: Listing the FileSets using the Bucket Name - nextLink\n",
592
593
"if '@nextLink' in response.json():\n",
593
594
" next_link = response.json()['@nextLink']\n",
594
595
" #step 3.5 - list Package IDs from bucket name - with pageSize 2 - navigate to next link\n",
@@ -681,9 +682,9 @@
681
682
"source": [
682
683
"Then you can continue to send requests to URL in ```@nextLink``` node to get the next page results.\n",
683
684
"\n",
684
-
"**Note**: The ```/file-store/v1/packages?bucketName={bucket-name}``` endpoint on the **step 2** above also supports the Paging feature with the same ```pageSize``` query parameter and ```@nextLink``` node.\n",
685
+
"**Note**: The ```/file-store/v1/packages?bucketName={bucket-name}``` endpoint on the **step 2** above also supports the Paging feature with the same ```pageSize``` query parameter and ```@nextLink``` node too.\n",
685
686
"\n",
686
-
"### Step 4: Get the Bulk file URL on AWS S3\n",
687
+
"### Step 4: Get the file URL on AWS S3\n",
687
688
"\n",
688
689
"The next step is getting the file URL on Amazon AWS S3 service with the RDP ```/file-store/v1/files/{file ID}/stream``` endpoint.\n",
689
690
"\n",
@@ -819,9 +820,9 @@
819
820
"id": "8bbc63cd-7399-4be5-80db-4df57dd88901",
820
821
"metadata": {},
821
822
"source": [
822
-
"Now you get the CFS Bulk file that you can extract and read the file.\n",
823
+
"Now you get the CFS file that you can extract and read the file.\n",
823
824
"\n",
824
-
"That is all for the RDP CFS Bulk File workflow."
825
+
"That is all for the RDP CFS File workflow."
825
826
]
826
827
},
827
828
{
@@ -980,7 +981,7 @@
980
981
"id": "710b7155-4e15-4ec6-a0a7-abb088477823",
981
982
"metadata": {},
982
983
"source": [
983
-
"That’s all I have to say about the CFS Bulk API workflow."
984
+
"That’s all I have to say about the CFS API workflow."
984
985
]
985
986
},
986
987
{
@@ -994,8 +995,8 @@
994
995
"\n",
995
996
"You may interested in the following resources for more detail about the CFS data usage:\n",
996
997
"- [Find environmental footprint of your bond portfolio](https://developers.lseg.com/en/article-catalog/article/Environmental_footprint_of_bond_portfolio) article\n",
997
-
"- [RDP APIs Green Revenues CFS Bulk file Workflow](https://github.com/LSEG-API-Samples/Example.RDP.Python.GreenRevenuesBulk) - a dedicate Green Revenue CFS workflow\n",
"- [RDP APIs Green Revenues CFS file Workflow](https://github.com/LSEG-API-Samples/Example.RDP.Python.GreenRevenuesBulk) - a dedicate Green Revenue CFS workflow\n",
"And much more on the [Developer Portal](https://developers.lseg.com/en) website."
1001
1002
]
@@ -1007,7 +1008,7 @@
1007
1008
"source": [
1008
1009
"## <a id=\"references\"></a>References\n",
1009
1010
"\n",
1010
-
"That brings me to the end of my generic CFS Bulk file workflow project. For further details, please check out the following resources:\r\n",
1011
+
"That brings me to the end of my generic CFS file workflow project. For further details, please check out the following resources:\r\n",
1011
1012
"\r\n",
1012
1013
"* [Refinitiv Data Platform APIs page](https://developers.lseg.com/en/api-catalog/refinitiv-data-platform/refinitiv-data-platform-apis) on the [Refinitiv Developer Community](https://developers.lseg.com/) website.\r\n",
1013
1014
"* [Refinitiv Data Platform APIs Playground page](https://apidocs.refinitiv.com/Apps/ApiDocs).\r\n",
0 commit comments