curl --request POST \
--url https://developer.synq.io/api/executions/v2/by-id \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"executionIds": [
"<string>"
]
}
'{
"executions": {}
}BatchGetExecutions retrieves multiple executions by their IDs. This is useful when you already know the execution IDs and want to fetch their details.
curl --request POST \
--url https://developer.synq.io/api/executions/v2/by-id \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"executionIds": [
"<string>"
]
}
'{
"executions": {}
}Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
BatchGetExecutionsRequest requests specific executions by ID.
Execution IDs to retrieve.
1 - 100 elementsSuccess
BatchGetExecutionsResponse contains the requested executions.
Map of execution ID to EntityExecution. Only includes executions that were found and accessible.
Show child attributes
EntityExecution represents a single execution event on an entity. This is a public representation of internal Run data, excluding sensitive metadata.
Show child attributes
Unique identifier for this execution.
Primary entities affected by this execution. These are the main entities this execution ran on or modified.
Identifier is a unique reference to an entity in SYNQ system. Entity identifiers are designed to closely mimic identifiers used by data platforms and tools. To construct an identifier, you need to know the kind of the entity and the ids that you would normally use to identify it in the data platform or tool. For example, to identify a table in BigQuery, you would need to know the project, dataset, and table names.
Show child attributes
SYNQ paths of primary entities affected by this execution.
Target entities referenced by this execution. These are secondary entities that were targets of the execution.
Identifier is a unique reference to an entity in SYNQ system. Entity identifiers are designed to closely mimic identifiers used by data platforms and tools. To construct an identifier, you need to know the kind of the entity and the ids that you would normally use to identify it in the data platform or tool. For example, to identify a table in BigQuery, you would need to know the project, dataset, and table names.
Show child attributes
SYNQ paths of target entities referenced by this execution.
Additional entity references. These are other entities referenced during the execution.
Identifier is a unique reference to an entity in SYNQ system. Entity identifiers are designed to closely mimic identifiers used by data platforms and tools. To construct an identifier, you need to know the kind of the entity and the ids that you would normally use to identify it in the data platform or tool. For example, to identify a table in BigQuery, you would need to know the project, dataset, and table names.
Show child attributes
SYNQ paths of additional entity references.
Type of execution (e.g., query, job, test run).
EXECUTION_TYPE_UNSPECIFIED, EXECUTION_TYPE_DELETION, EXECUTION_TYPE_SCHEMA_CHANGE, EXECUTION_TYPE_SQL_DEFINITION_CHANGE, EXECUTION_TYPE_BQ_QUERY_JOB, EXECUTION_TYPE_BQ_LOAD_JOB, EXECUTION_TYPE_BQ_COPY_JOB, EXECUTION_TYPE_BQ_EXTRACT_JOB, EXECUTION_TYPE_BQ_QUERY_LOG, EXECUTION_TYPE_LOOKER_USAGE_REPORT, EXECUTION_TYPE_DBT_INVOCATION, EXECUTION_TYPE_DBT_NODE_INVOCATION, EXECUTION_TYPE_DBT_NODE_FRESHNESS, EXECUTION_TYPE_DBT_CLOUD_JOB_RUN, EXECUTION_TYPE_DBT_CLOUD_JOB_RUN_STEP, EXECUTION_TYPE_DATABOX_FRESHNESS, EXECUTION_TYPE_GIT_COMMIT, EXECUTION_TYPE_CLICKHOUSE_QUERY_LOG, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_SELECT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_DROP, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CREATE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CREATE_TABLE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_INSERT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_MERGE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_UPDATE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CREATE_TABLE_AS_SELECT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_DELETE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_SHOW, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CREATE_VIEW, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_MULTI_STATEMENT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_ROLLBACK, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_TRUNCATE_TABLE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_COMMIT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_BEGIN_TRANSACTION, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_UNKNOWN, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_SET, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_RENAME_TABLE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_GRANT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_ALTER_TABLE_ADD_COLUMN, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_USE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_COPY, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CALL, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_ALTER_TABLE_DROP_COLUMN, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_ALTER_TABLE_MODIFY_COLUMN, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_RENAME_COLUMN, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_DROP_ROLE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_DESCRIBE_QUERY, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CREATE_CONSTRAINT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_EXPLAIN, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CREATE_ROLE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_ALTER, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_DESCRIBE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_PUT_FILES, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_GET_FILES, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_ALTER_SESSION, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_LIST_FILES, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_EXTERNAL_TABLE_REFRESH, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_REFRESH_DYNAMIC_TABLE_AT_REFRESH_VERSION, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_REMOVE_FILES, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_EXECUTE_TASK, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_ALTER_TABLE, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_EXECUTE_STREAMLIT, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_CREATE_TASK, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_UNLOAD, EXECUTION_TYPE_SNOWFLAKE_QUERY_LOG_DROP_TASK, EXECUTION_TYPE_SNOWFLAKE_TASK_EXECUTION, EXECUTION_TYPE_SNOWFLAKE_TASK_GROUP_EXECUTION, EXECUTION_TYPE_REDSHIFT_QUERY_LOG, EXECUTION_TYPE_DATAHUB_DATA_PROCESS_INSTANCE, EXECUTION_TYPE_DATAHUB_USAGE_REPORT, EXECUTION_TYPE_SYNQ_CUSTOM_ENTITY_EXECUTION, EXECUTION_TYPE_SYNQ_CUSTOM_ENTITY_LOG, EXECUTION_TYPE_SYNQ_CUSTOM_ENTITY_MEASUREMENT, EXECUTION_TYPE_TABLEAU_USAGE_REPORT, EXECUTION_TYPE_TABLEAU_EXTRACT, EXECUTION_TYPE_AIRFLOW_DAG, EXECUTION_TYPE_AIRFLOW_TASK, EXECUTION_TYPE_ANOMALY_INTEGRATION_RUN, EXECUTION_TYPE_ANOMALY_MONITOR_RUN, EXECUTION_TYPE_ANOMALY_MONITOR_CORRECTION, EXECUTION_TYPE_ANOMALY_MONITOR_SEGMENT_RUN, EXECUTION_TYPE_ANOMALY_MONITOR_SEGMENT_CORRECTION, EXECUTION_TYPE_ANOMALY_MONITOR_FETCH_RUN, EXECUTION_TYPE_SQL_TEST_RUN, EXECUTION_TYPE_DATABRICKS_QUERY_LOG, EXECUTION_TYPE_DATABRICKS_JOB_RUN, EXECUTION_TYPE_DATABRICKS_JOB_TASK_RUN, EXECUTION_TYPE_SQLMESH_PROJECT_EXECUTION, EXECUTION_TYPE_SQLMESH_MODEL_EVALUATION, EXECUTION_TYPE_SQLMESH_AUDIT_CHECK, EXECUTION_TYPE_TRINO_QUERY_LOG Status of the execution.
EXECUTION_STATUS_UNSPECIFIED, EXECUTION_STATUS_OK, EXECUTION_STATUS_WARN, EXECUTION_STATUS_ERROR, EXECUTION_STATUS_CRITICAL Whether this execution was skipped.
Human-readable message describing the execution result. This typically contains error messages, warnings, or success information.
When the execution record was created in SYNQ.
When the execution actually started.
When the execution finished.
IDs of parent executions, if this is a nested execution. For example, a task execution might have a parent DAG execution.
Duration of the execution in seconds. Only populated if both started_at and finished_at are present.