API Changes

Deprecated endpoints

The following endpoints have been deprecated with connections. Use the recommended endpoint instead.

Action	Deprecated endpoint	Use this with connections instead
Create a single data source		Step 1: Ensure your system user has been granted access to the relevant object in the data platform. Step 2: Wait until the next object sync or manually trigger a metadata crawl using POST /data/crawl/{objectPath*}. Step 3: If the parent schema has activateNewChildren: false, PUT /data/settings/{objectPath*} with settings: isActive: true.
Bulk create data sources		Step 1: Ensure your system user has been granted access to the relevant object in the data platform. Step 2: Wait until the next object sync or manually trigger a metadata crawl using POST /data/crawl/{objectPath*}. Step 3: If the parent schema has activateNewChildren: false, PUT /data/settings/{objectPath*} with settings: isActive: true.
Edit a data source connection		No substitute. Data sources no longer have their own separate connection details but are tied to the parent connection.
Bulk edit data source's connections		No substitute. Data sources no longer have their own separate connection details but are tied to the parent connection.
Run schema detection (object sync)		POST /data/crawl/{objectPath*}
Delete a data source		DELETE /data/object/{objectPath*}
Bulk delete data sources		DELETE /data/object/{objectPath*}
Enable a single data source		PUT /data/settings/{objectPath*} with settings: isActive: true
Bulk enable data sources		PUT /data/settings/{objectPath*} with settings: isActive: true
Disable a single data source		PUT /data/settings/{objectPath*} with settings: isActive: false
Bulk disable data sources		PUT /data/settings/{objectPath*} with settings: isActive: false
Edit a data source name		No substitute. Data source names are automatically generated based on information from your data platform.
Edit a display name		No substitute. Data sources no longer have their own separate connection details but are tied to the parent connection.
Override a host name		No substitute. Data sources no longer have their own separate connection details but are tied to the parent connection.
Create an integration/connection		POST /data/connection
Update an integration/connection		PUT data/connection/{connectionKey}
Delete an integration/connection		DELETE data/object/{connectionKey}
Delete and update a data dictionary	PUT	No substitute. Data source dictionaries are automatically generated based on information from your data platform.
Update a data source owner		PUT /data/settings/{objectPath*} with settings: dataOwners
Response to a data source owner request		PUT /data/settings/{objectPath*} with settings: dataOwners

Impacted endpoints

If you have any automated actions using the following APIs, ensure you do the required change after the upgrade to ensure they continue working as expected.

Action	Impacted endpoint	Required change
Search for a data source	GET /dataSource/name/{dataSourceName} GET /dataSource	Data source names will change with the upgrade. Update {dataSourceName} in the request with the new data source name. Data sources names will change with the upgrade. Update the searchText in the payload with the new data source name.
Apply identification frameworks to data sources	PUT /sdd/template/apply	Data source names will change with the upgrade. Update the sources in the payload with the new data source names.
Run SDD on data sources	POST /sdd/run	Data source names will change with the upgrade. Update the sources in the payload with the new data source names.
Search schema names	GET /schemas	This endpoint will not search the schemas of connection data sources. Instead use the GET /data/object/{objectPath}.