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

2025.3.3 API Release Notes

New APIs

OAuth 2.0 API Endpoints

The new OAuth 2.0 API endpoints are introduced to support User-Initiated Authorization, Token Lifecycle Management, and Client Management, providing secure and standards-compliant authorization flows for third-party integrations. These APIs enable modern OAuth-based authentication patterns, allowing seamless integration with external clients and systems, including MCP clients.

Users can easily discover and understand how to use these OAuth 2.0 endpoints through an improved onboarding experience tailored for user-initiated authorization flows, such as the authorization_code and refresh_token grant types. The following endpoints are available:

• /oauth/v1/authorize
• /oauth/v1/token
• /integration/core/v1/oauth/clients
• /integration/core/v1/oauth/clients/{client_id}
• /integration/core/v1/oauth/clients/{client_id}/rotate-secret

Note: These endpoints are specifically designed for user-initiated authorization flows (e.g., authorization_code and refresh_token grants).

For machine-based authorization flows (such as the client_credentials grant), refer to the Authenticate API Calls with OAuth 2.0 section in the Alation User Documentation. Then, see the OAuth 2.0 API for instructions on creating and using a JSON Web Token (JWT). (AL-201177)

Updates to Existing APIs

Improved Dataflow Reliability in Dataflow API

Adds validations in the POST Dataflow API endpoint and DELETE Dataflow API endpoint to ensure that dataflows are created and deleted correctly, preventing empty dataflow scenarios and improving lineage accuracy.
The path of a dataflow object between a source and target is now validated.
The validation ensures that the requested object types (otypes) for the path are on the same hierarchical level (e.g., Table-Table or Column-Column). (AL-207697)

Catalog Admin Support for BI V2 Public APIs

Allows catalog and source administrators to access the BI API endpoints with the following Alation conf feature flags:

• alation.public_api.gbmv2.allow_editing_for_catalog_admin: If enabled (set to true), catalog administrators are able to use the public API editing endpoints if they are a BI administrator for the source.
• alation.public_api.gbmv2.allow_editing_for_source_admin: If enabled (set to true), catalog administrators are able to use the public API editing endpoints if they are a BI administrator for the source. (AL-194290)

Context API Now Defaults to Claude Sonnet 4

The Context API now utilizes Claude Sonnet 4 through AWS Bedrock by default, providing improved performance. (AL-209529)

Bug Fixes

• Fixed an issue where the Delete Lineage API (V3) endpoint returned a success response even when invalid or dummy values were passed for source and target keys. When a request includes incorrect values, the system will check the database and return an error if the specified path does not exist. Although a job ID will be returned, the error must be checked via the Jobs Status API. The dataflow_key parameter in the API is now optional.
  • If dataflow_key is omitted, all related dataflows for that edge will be deleted.
  • If a dataflow_key is provided but the edge has multiple associated dataflows, the system will indicate that the edge was not deleted because other dataflows are still linked to it. (AL-199315)
• Fixed the issue where updating custom fields failed using the Documents API endpoint. (AL-208223)
• Fixed an issue where retrieving the columns using the Lineage V2 API calls was throwing a UI webserver error. (AL-209547)
• Fixed an issue where the Delete Lineage API endpoint call gave the result “no links found” message. (AL-200814)