Skip to main content
GET
List Data Objects
The List Data Objects endpoint returns all data objects within a specific dataset. Data objects are the actual records in your master data repository, containing field values that conform to the schema structure.

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. You can obtain this from the List Schemas endpoint.
string
required
The unique identifier of the dataset containing the data objects. You can obtain this from the List Datasets 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 data objects and pagination information.
array
required
An array of data objects. Each object contains dynamic fields based on the schema definition, plus system-generated metadata fields.
string
A pagination token for retrieving the next page of results. If this field is present, more data objects are available. Pass this value as the pageKey query parameter in your next request.

Example Response

Response with Validation Errors

Data objects may have validation errors if the data doesn’t conform to schema rules:

Empty Response

If the dataset has no data objects, the response will contain an empty items array:

Error Responses

Pagination

When a dataset contains many data objects, results are paginated. Use the nextPageKey from the response to fetch subsequent pages:

Best Practices

  1. Use pagination: Always handle pagination for large datasets. Don’t assume all data will fit in a single response.
  2. Cache schema information: Fetch the schema once to understand field names and types, then reuse it when processing data objects.
  3. Handle validation errors: Check the _errors array to identify data quality issues that need attention.
  4. Use version for updates: Store the _version value if you plan to update the data object later.

Create Data Object

Add new records to a dataset

Update Data Object

Modify existing records

Delete Data Object

Remove records from a dataset

Get Data Object by Primary Key

Fetch one record by its primary key value

Search Data Objects

Search across all datasets