Retrieve data from an existing connection data source, identified by its ID. Requires a request body specifying the engagement and optional filter/pagination. Unlike the Connection /get-data endpoint, you do not specify a schema. The schema defined on the connection data source is used automatically.
api.connection-data-sources.readBearer authentication header of the form Bearer <token>, where <token> is your auth token.
Identifies the engagement that the resulting Data Table will be associated with.
Optional filter to apply to the data retrieval. If not set, all rows are returned unfiltered.
Maximum number of rows to return. If not set, all matching rows are returned.
x >= 0Number of rows to skip before returning results. If not set, results start from the first row.
x >= 0Accepted
Indicates the data integrity version to ensure data consistency.
The unique object identifier.
The date that the object was originally created.
The date that the object was last updated or modified.
Details about the user who created the object.
Details about the user who last modified or updated the object.
Indicates the type of job being run.
ANALYSIS_RUN, ANALYSIS_SOURCE_INGESTION, ADMIN_REPORT, DATA_TABLE_EXPORT, ANALYSIS_ROLL_FORWARD, GDPDU_UNPACK_JOB, ACCOUNT_GROUPING_EXPORT, ACCOUNT_MAPPING_EXPORT, DATA_TRANSFORMATION_JOB, CONNECTION_TEST, CONNECTION_TABLES, DATA_TABLE Indicates the current state of the job.
IN_PROGRESS, COMPLETE, ERROR Identifies the entity used in the job.
Identifies the entity type used in the job.
ORGANIZATION, ENGAGEMENT, ANALYSIS, ANALYSIS_RESULT, ANALYSIS_SOURCE, FILE_RESULT, GDPDU_UNPACK_JOB, ACCOUNT_GROUPING, ENGAGEMENT_ACCOUNT_GROUPING, FILE_MANAGER_FILE, CONNECTION_TEST_RESULT, CONNECTION_TABLES_RESULT, DATA_TABLE The reason why the async job failed.