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

2025.3.1 API Release Notes

Updated

Aggregated Context API

The underlying Large Language Model (LLM) used for question rewriting in the Aggregated Context API endpoint has been upgraded from Sonnet 3 to Sonnet 3.7. This enhancement improves the accuracy and relevance of the context provided by the API.

Note: This upgrade is active in all regions except for Canada. Administrators can manage the model configuration via Alation feature flag. (AL-203437)

New Parameter to Exclude Deleted Object Reference

Added a new query parameter to exclude the deleted object references in the following API endpoints:

Folder API endpoint, Document API endpoint, Relational Integration Schema API endpoint, Relational Integration Table API endpoint, and Relational Integration Column API endpoint: Introduces a new query parameter exclude_deleted_ref=true to exclude deleted object references.
Native Data Sources API endpoints (GET Native Data Sources and GET Native Data Sources by ID) and Data Sources API (OCF) endpoints (GET OCF Data Sources and GET OCF Data Sources by ID): Introduces a new query parameter exclude_suspended=true to exclude suspended owner IDs.
User API endpoints (GET V1 Users and GET V2 Users): Introduces a new query parameter exclude_suspended=true to exclude suspended users. (AL-188856)

Get Lineage Information API

The Get Lineage API endpoint has been optimized to use a new backend model, improving performance while keeping the response format unchanged. Existing integrations continue to work as before.

A new optional query parameter has been added for more flexibility:
excludeChildren

Default: false returns lineage for the requested object and its children (for example, a table and its columns).
When set to true: returns lineage only for the requested object (for example, just the table) without child-level lineage.

This allows choosing between detailed lineage (including children) or a simpler parent-level view.

Note: The new parameter is available when the following feature flags are enabled: lineage-service.dataflow_migration.run_successfully and lineage-service.features.enable_new_get_lineage_public_api_impl. (AL-201452)

Table Name Support in BI Datasource Column API Endpoints

The BI Source API endpoints have been enhanced to include the table_name attribute for BI datasource columns.

GET Requests: The GET BI Datasource Column endpoint now returns the table_name field in the response. The endpoint also supports a new query parameter for case-insensitive filtering by table_name.
POST Requests: The POST BI Datasource Column endpoint now accepts the table_name field in the request body.

Note: This functionality is controlled by a feature flag (alation.feature_flags.add_table_name_for_bi_ds_column) which is enabled by default. (AL-202256)