Skip to main content
GET
List Datasets
The List Datasets endpoint returns all datasets defined within a specific schema. Datasets are collections of data objects that share the same schema structure and represent actual data records in your master data repository.

Prerequisites

Authentication

Include your API key in the Authorization header.

Request

Path Parameters

string
required
The unique identifier of the business area. You can obtain this from the List Business Areas endpoint.
string
required
The unique identifier of the schema containing the datasets. You can obtain this from the List Schemas endpoint.

Query Parameters

string
A pagination token for retrieving the next page of results. This value is returned in the response as nextPageKey when more results are available.

Headers

string
required
Your Pretectum API key. Create one in the Pretectum app under Configuration → API Keys.
string
default:"application/json"
The response content type. Currently only application/json is supported.

Example Requests

Response

A successful request returns an object containing an array of datasets and pagination information.
array
required
An array of dataset objects within the schema.
string
A pagination token for retrieving the next page of results. If this field is present, more datasets are available. Pass this value as the pageKey query parameter in your next request.

Example Response

Response Without Pagination

When all datasets fit in a single response, no nextPageKey is returned:

Empty Response

If the schema has no datasets defined, the response will contain an empty items array:

Error Responses

Pagination

When a schema contains many datasets, results are paginated. Use the nextPageKey from the response to fetch subsequent pages:

Use Cases

Filtering Search Results by Dataset

Use the dataset names returned by this endpoint to filter your data object searches:

Monitoring Data Quality

Check the erroredRecordsCount to identify datasets with data quality issues:

Tracking Record Counts

Monitor the size of your datasets:

Best Practices

  1. Cache dataset lists: Dataset metadata changes less frequently than record data. Cache the response and refresh periodically.
  2. Filter by active datasets: Exclude datasets where deleted: true in user-facing interfaces.
  3. Use names for search filters: When filtering searches with the dataSet parameter, use the dataSetName field value.
  4. Handle pagination: Always check for nextPageKey in responses and fetch all pages if needed.
  5. Monitor error counts: Regularly check erroredRecordsCount to identify data quality issues early.

List Schemas

Get schema IDs for dataset queries

List Business Areas

Get business area IDs

Search Data Objects

Search within specific datasets

API Keys

Obtain authentication token