Get list of datasets
GET/v2/datasets
Lists all of a user's datasets.
The response is a JSON array of objects, where each object contains basic information about one dataset.
By default, the objects are sorted by the createdAt field in ascending
order, therefore you can use pagination to incrementally fetch all datasets while new
ones are still being created. To sort them in descending order, use desc=1
parameter. The endpoint supports pagination using limit and offset
parameters and it will not return more than 1000 array elements.
Request
Query Parameters
ownedByMe: Return only datasets owned by the user.sharedWithMe: Return only datasets shared with the user by other users.
Number of array elements that should be skipped at the start. The default value is 0.
10Maximum number of array elements to return. The default value as well as the maximum is 1000.
99If true or 1 then the objects are sorted by the startedAt field in
descending order. By default, they are sorted in ascending order.
trueIf true or 1 then unnamed datasets are displayed. For performance reasons, both named and unnamed datasets that are empty will not be shown when this parameter is enabled. By default only named datasets are returned.
truePossible values: [ownedByMe, sharedWithMe]
Filter by ownership. If this parameter is omitted, all accessible datasets are returned.
ownedByMeStatus 200
Response Headers
{
"data": {
"total": 2,
"offset": 0,
"limit": 1000,
"desc": false,
"count": 2,
"items": [
{
"id": "wkzbqmufyuamgv3yf",
"name": "d7b9mdysbtx5l7xaj",
"userId": "tbXmWu7GCxnyYtSiL",
"createdAt": "2019-12-12T07:34:14.202Z",
"modifiedAt": "2019-12-13T08:36:13.202Z",
"accessedAt": "2019-12-14T08:36:13.202Z",
"itemCount": 7,
"cleanItemCount": 5,
"actId": null,
"actRunId": null
},
{
"id": "YiKoxjkaS9gjGTqhF",
"name": "eshop-items",
"userId": "tbXmWu7GCxnyYtSiL",
"createdAt": "2019-12-12T07:34:14.202Z",
"modifiedAt": "2019-12-13T08:36:13.202Z",
"accessedAt": "2019-12-14T08:36:13.202Z",
"itemCount": 2,
"cleanItemCount": 2,
"actId": null,
"actRunId": null
}
]
}
}
Schema
data object required
Common pagination fields for list responses.
- total integer required
The total number of items available across all pages.
Possible values:
Example:>= 02 - offset integer required
The starting position for this page of results.
Possible values:
Example:>= 00 - limit integer required
The maximum number of items returned per page.
Possible values:
Example:>= 11000 - desc boolean required
Whether the results are sorted in descending order.
Example:false - count integer required
The number of items returned in this response.
Possible values:
Example:>= 02 items object[] required
- id string requiredExample:
WkzbQMuFYuamGv3YF - name string requiredExample:
d7b9MDYsbtX5L7XAj - userId string requiredExample:
tbXmWu7GCxnyYtSiL - createdAt string<date-time> requiredExample:
2019-12-12T07:34:14.202Z - modifiedAt string<date-time> requiredExample:
2019-12-13T08:36:13.202Z - accessedAt string<date-time> requiredExample:
2019-12-14T08:36:13.202Z - itemCount integer requiredExample:
7 - cleanItemCount integer requiredExample:
5 - actId string | null nullable
- actRunId string | null nullable
- id string requiredExample:
- total integer required
Status 400
Bad request - invalid input parameters or request body.
{
"error": {
"type": "invalid-input",
"message": "Invalid input: The request body contains invalid data."
}
}
Schema
error object required
- type string requiredExample:
run-failed - message string requiredExample:
Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)
- type string requiredExample: