See Finding Your Alation Version for help determining which version of Alation you're using.

2026.7.2.0 API Release Notes

Update: Native Data Quality API

Added support for ownership, approval, and service account tracking on monitors, along with new metadata fields for monitors, tables, and checks.

This update enables integrations to identify who owns and approves a monitor, which service account executes its queries, and the origin and pause state of monitors and checks, without relying on separate lookups.

New schemas

• Owner: Represents a user or user-group principal responsible for a resource. Includes id and otype fields.
• Approver: Represents an approver for a resource. Includes approver_id and approver_type fields.
• ServiceAccountBinding: Maps a data source (ds_id) to the service account (service_account_id) used for query execution.

Monitor schema: new fields

You can now read the following fields on a monitor:

• monitor_properties (read-only): Raw monitor properties, including template variables.
• created_by (read-only): ID of the user who created the monitor.
• creation_type (read-only): Origin of monitor creation. Values are 0 (Unknown), 1 (UI), 2 (API), 3 (SDK), and 4 (Standards).
• is_paused (read-only): Indicates whether scheduled execution is currently paused.
• service_account_bindings (read-only, conditional): Returned only when requested using a query parameter. See GET /monitor: new query parameter.

You can now read and write the following fields on a monitor:

• owners: Array of Owner objects.
• approvers: Array of Approver objects.

GET /monitor: new query parameter

• Endpoint: /monitor
• New capability: Optionally include service account bindings in the response.

Added the include_service_accounts query parameter. When set to "true", the response includes service account bindings for each monitor.

PATCH /monitor: updated capability

• Endpoint: /monitor
• New capability: Update owners, approvers, and service account bindings on an existing monitor.

The endpoint description and the MonitorPatchRequest schema have been updated to document support for the following fields:

• owners
• approvers
• service_account_bindings

Validation and behavior

• These fields follow replace-on-present semantics: if included in a PATCH request, the existing value is fully replaced rather than merged.

Table schema: new field

• dbtype (read-only): The underlying database type (for example, snowflake or postgresql).

TableCheck and Check schemas: new fields

• is_paused: Indicates whether the check's scheduled execution is paused.
• enabled: Indicates whether the check is active.

Update: Lineage API v2

Added support for filtering results by external_id, so you can retrieve dataflows scoped to a specific data source, BI server, or API namespace without paginating through the full catalog.

Previously, isolating dataflows for one data source, BI server, or API namespace meant fetching the entire dataflow catalog and filtering client-side. These lookup parameters push that filtering to the server, reducing response size and the number of paginated requests needed for targeted lookups.

Seven new optional query parameters are available on the Get Dataflow Objects endpoint:

Example

Fetch every dataflow whose external_id belongs to a given SQL source namespace:

GET /integration/v2/dataflow/?external_id__startswith=sql/3_

Compatibility

• Additive only. These parameters are optional and can be freely combined with the endpoint's existing filters (keyField, limit, skip, excludeTemp, excludeGone), as well as the optional request-body payload for filtering by object IDs or external IDs.
• No breaking changes. If none of the new parameters are supplied, the endpoint's existing behavior and response shape are unchanged.