Lists Files contained in a Dataset. By default files are listed on the latest view of the default
branch - master for most enrollments.
See Datasets Core Concepts for details on using branches and transactions.
To list files on a specific Branch specify the Branch's name as branchName. This will include the most
recent version of all files since the latest snapshot transaction, or the earliest ancestor transaction of the
branch if there are no snapshot transactions.
To list files on the resolved view of a transaction specify the Transaction's resource identifier
as endTransactionRid. This will include the most recent version of all files since the latest snapshot
transaction, or the earliest ancestor transaction if there are no snapshot transactions.
To list files on the resolved view of a range of transactions specify the the start transaction's resource
identifier as startTransactionRid and the end transaction's resource identifier as endTransactionRid. This
will include the most recent version of all files since the startTransactionRid up to the endTransactionRid.
Note that an intermediate snapshot transaction will remove all files from the view. Behavior is undefined when
the start and end transactions do not belong to the same root-to-leaf path.
To list files on a specific transaction specify the Transaction's resource identifier as both the
startTransactionRid and endTransactionRid. This will include only files that were modified as part of that
Transaction.
Third-party applications using this endpoint via OAuth2 must request the following operation scope: api:datasets-read.
stringThe name of the Branch on which to list Files. Defaults to master for most enrollments.
stringThe Resource Identifier (RID) of the start Transaction.
stringThe Resource Identifier (RID) of the end Transaction.
integerThe page size to use for the endpoint.
stringThe page token indicates where to start paging. This should be omitted from the first page's request.
To fetch the next page, clients should take the value from the nextPageToken field of the previous response
and use it to populate the pageToken field of the next request.
objectlist<File>stringThe page token indicates where to start paging. This should be omitted from the first page's request.
To fetch the next page, clients should take the value from the nextPageToken field of the previous response
and use it to populate the pageToken field of the next request.
1
2
3
curl \
-H "Authorization: Bearer $TOKEN" \
"https://$HOSTNAME/api/v2/datasets/ri.foundry.main.dataset.c26f11c8-cdb3-4f44-9f5d-9816ea1c82da/files?branchName=master&startTransactionRid=ri.foundry.main.transaction.0a0207cb-26b7-415b-bc80-66a3aa3933f4&endTransactionRid=ri.foundry.main.transaction.0a0207cb-26b7-415b-bc80-66a3aa3933f4&pageSize=100&pageToken=v1.QnVpbGQgdGhlIEZ1dHVyZTogaHR0cHM6Ly93d3cucGFsYW50aXIuY29tL2NhcmVlcnMvP2xldmVyLXNvdXJjZSU1YiU1ZD1BUElEb2NzI29wZW4tcG9zaXRpb25z"1
2
3
4
5
6
7
8
9
10
{
"data": [
{
"path": "2020/09/30/trades.csv",
"updatedTime": "2020-09-30T12:34:56.789Z",
"transactionRid": "ri.foundry.main.transaction.0a0207cb-26b7-415b-bc80-66a3aa3933f4"
}
],
"nextPageToken": "v1.QnVpbGQgdGhlIEZ1dHVyZTogaHR0cHM6Ly93d3cucGFsYW50aXIuY29tL2NhcmVlcnMvP2xldmVyLXNvdXJjZSU1YiU1ZD1BUElEb2NzI29wZW4tcG9zaXRpb25z"
}