SDK and API Changelog

This page tracks API-level changes introduced in each Acceldata SDK release. For each release, the tables below document the request payload and response structure before and after the change for every affected endpoint.

Use this page to assess the impact of upgrading to a new SDK version, update downstream integrations, or validate that your implementation handles new or modified fields correctly.

For SDK version compatibility with the Control Plane and Python, see Compatibility Guidelines for Control Plane, SDK, and Python Versions.

How to Read This Page

Each release section lists the APIs grouped by category. For each API:

Status indicates whether the API is Enhanced, New, Deprecated, or has No changes in that release.
Payload — Previous shows the request payload structure before the release. A dash (—) indicates no payload is required or no change occurred.
Payload — Now shows the request payload structure after the release.
Response — Previous shows the response structure before the release.
Response — Now shows the response structure after the release.

Only APIs with changes include full before/after detail. APIs with No changes are listed by name for completeness.

26.5.0

Datasource APIs

API	Status
Start Crawler	No changes
Get Crawler Status	No changes

Asset APIs

API	Status
Get Asset Details (by ID and UID)	No changes
Get Asset Types	No changes
Get Asset Metadata	No changes
Get All Tags	No changes
Add Tag to an Asset	No changes
Add Labels to an Asset	No changes
Get Asset Labels	No changes
Add Custom Metadata	No changes
Sample Data	No changes

Profiling APIs

API	Status
Trigger Profiling — Full	No changes
Trigger Profiling — Incremental (ID / Datetime)	No changes
Trigger Profiling — Selective (ID / Datetime)	No changes
Cancel Profiling	No changes
Get Latest Profile Status	No changes
Get Profile Result Status	No changes

Policy APIs

API	Status
Get Executions	No changes
List All Policies	No changes
Get Policy	No changes

Data Quality / Reconciliation APIs

API	Status
Trigger Policy Execution	No changes

Pipeline APIs

Unchanged Pipeline APIs

API	Status
Create Pipeline	No changes
Create Job	No changes
Create Pipeline Run	No changes
Create Root Span	No changes
Get Root Span	No changes
Create Child Span	No changes
Send Event	No changes
Update Pipeline Run	No changes
Get Latest Pipeline Run	No changes
Get Pipeline Runs	No changes
Delete Pipeline	No changes

Get Pipeline (get_pipelines)

Status: Enhanced

SDK method: torch_client.get_pipelines()

Payload — Previous

No request payload. This is a read-only method with no parameters.

Payload — Now

No change. No request payload required.

Response — Previous

The pipelineSummary object did not include the uid field.

JSON
    
xxxxxxxxxx
 
{  "pipelineSummary": {    "id": 30470,    "name": "demo_do_not_end_pipeline_run",    "meta": {      "codeLocation": "https://git.example.com/repo",      "owner": "Demo",      "team": "demo_team"    }  },  "assetNodesCount": 1,  "functionalNodesCount": 2,  "latestRunResult": "SUCCESS",  "totalRunsCount": 7}
Copy

Response — Now

The pipelineSummary object now includes the uid field.

JSON
    
xxxxxxxxxx
 
{  "pipelineSummary": {    "id": 30470,    "name": "demo_do_not_end_pipeline_run",    "meta": {      "codeLocation": "https://git.example.com/repo",      "owner": "Demo",      "team": "demo_team"    },    "uid": "adoc.airflow.pipeline.hetro"  },  "assetNodesCount": 1,  "functionalNodesCount": 2,  "latestRunResult": "SUCCESS",  "totalRunsCount": 7}
Copy

New field details

Field	Type	Description
`pipelineSummary.uid`	string	Stable, unique identifier for the pipeline. Use this field for consistent referencing across systems.

This change is fully backward compatible. Existing integrations that do not consume the uid field will continue to function without modification. Upgrade to SDK 26.5.0 or later to access this field.

Last updated on

Was this page helpful?