To enable programmatic control over its objects, the
- Connections: Get information about connections
- Datasets: Create, list, update, and delete operations on datasets
- Swap datasets
- Jobs and Results:
- Launch job
- Get job status
- Publish job results
- Create dataset from results
- Get profile metadata:
- Quality bar status
- Schema (column names and types)
- Users: Create, list, delete
HTTP protocol identifier. The protocol should be
Name of the
Port number over which you access the d-s- platform. By default, this value is
API version number.
|Name of the API endpoint to use.|
|Internal identifier for the specific resource requested from the endpoint. This value defines the object against which the requested operation is performed.|
If applicable, the association identifiers the API endpoint that is requested using the context determined by the
Associations can also be referenced by query parameter. See Embedding Associations below.
|In some cases, arguments can be passed to the endpoint in the form of query parameters.|
|Operation||HTTP Method||Example URL||Notes|
|Update||Partial replacement||Partial replacement|
|Full replacement||Full Partial replacement|
|Client request that expects a response body||request header:||should include|
|Client request that includes a request body||request header:||required|
|Server response that includes a response body||response header:||requiredresponse body||response header:||required|
Each request contains a request identifier in the following form:
The above request header also appears as a header in the response.
NOTE: If you have an issue with a specific request, please include the
Each call to an API endpoint must include authentication credentials for a user with access to the requested objects. See API Authentication.
If SSL has been enabled for the
|D s platform|
Unless otherwise noted, the documentation and examples apply to latest version of the
|D s platform|
Examples may require modification to work in your environment.