Page tree

Release 5.0.1



For the latest updates on available API endpoints and documentation, see


To enable programmatic control over its objects, the  Designer Cloud powered by Trifacta platform  supports a range of REST API endpoints across the objects in the platform. This section provides an overview of the API design, methods, and supported use cases.

Supported operations:

  • 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


  • Can be used for automation of resource management for end-to-end workflow
  • Can be used to integrate wrangling experience in third-party application
  • See Use Cases below.

Design Overview

URL Format


Elements in square brackets [brackets] are optional. 


HTTP protocol identifier. The protocol should be https in a production environment.


Name of the Trifacta node

Port number over which you access the Designer Cloud powered by Trifacta platform . By default, this value is 3005.


API version number.

NOTE: Unless stated otherwise, the versions for all API endpoints is v3.

<endpoint>Name of the API endpoint to use./connections
[resource_id]Internal identifier for the specific resource requested from the endpoint. This value defines the object against which the requested operation is performed./10

If applicable, the association identifiers the API endpoint that is requested using the context determined by the <endpoint> and the [resource_id].

Associations can also be referenced by query parameter. See Embedding Associations below.

[?args]In some cases, arguments can be passed to the endpoint in the form of query parameters.?arg1=value1&arg2=value2

Naming Conventions

  • Resource names are plural and expressed in camelCase.
  • Resource names are consistent between main URL and URL parameter.

v4 conventions

The following conventions apply to v4 and later versions of the APIs:

  • Parameter lists are consistently enveloped in the following manner:

    { "data": [
  • Field names are in camelCase and are consistent with the resource name in the URL or with the embed URL parameter.
  • From early API versions, foreign keys have been replaced with identifiers like the following:

    v3 and earlierv4 and later
    "createdBy": 1,
    "creator": {
      "id": 1
    "updatedBy": 2,
    "updater": {
      "id": 2

Operations and Methods

Support for basic CRUD (Create, Read, Update, and Delete) operations across most platform objects.

NOTE: Some of these specific operations may not be supported in the current release. For a complete list, see API Endpoints.

OperationHTTP MethodExample URLNotes
ReadGET /v3/people/1 1 = internal user Id
GET /v3/jobResults/10 10 = internal job Id
GET /v3/people/1/jobGroups  
GET /v3/jobGroups/4/flowNode flowNode is a singular reference. Most resource names are plural.
ListGET /v3/people  
UpdatePATCH /v3/people/1 Partial replacement
PATCH /v3/jobResults/10 Partial replacement
PUT /v3/people/1 Full replacement
PUT /v3/jobResults/10 Full replacement
DeleteDELETE /v3/people/1  
DELETE /v3/jobResults/10


Embedding Associations

An association can be referenced using the above URL structuring or by applying the embed query parameter as part of the reference to the specific resource. Example:


Example response:

  "id": 6,
  "description": "A nifty job group",
  "flowNode": {
    "id": 1,
    "script": {
      "id": 1
    "terminal": true

The id value of the association is always included in the response. 

Media Type Headers

NOTE: Some endpoints may accept and return a custom media type. These endpoints are documented.

Client request that expects a response bodyrequest header:
Accept: application/json 
should include
Client request that includes a request bodyrequest header:
Content-Type: application/json 
Server response that includes a response bodyresponse header:
Content-Type: application/json 


The REST APIs use the same authentication methods as the UI. 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  Designer Cloud powered by Trifacta platform , requests to URL endpoints are automatically redirected to the HTTPS equivalent.


Single-file upload is supported.

Multi-file upload is not supported.

Versioning and Endpoint Lifecycle

NOTE: API versioning is not synchronized to specific releases of Designer Cloud Powered by Trifacta Enterprise Edition. For example, some API endpoints for v4 may be updated, while v3 instances of the API endpoint are still supported. APIs are designed to be backward compatible.

APIs are designed to be backward compatible so that scripts and other tooling built on a previous version of an endpoint remain valid until the previous version has reached end-of-life. Each API is supported across a window of  Designer Cloud Powered by Trifacta Enterprise Edition releases, after which you must reference a newer version of the API.

API endpoint routes support a consistent structuring and do not contain business logic. 

Version information is available at the following endpoint:


For more information, see API Version Support Matrix.

HTTP Status Codes and Errors

Request MethodRequest EndpointHTTP Status Code (success)
POST/v3/<resource>201 Created
GET/v3/<resource>200 OK

304 Not Modified when client has cached version.

See Caching below.

PATCH/v3/<resource>/<id>200 OK
PUT/v3/<resource>/<id>200 OK
DELETE/v3/<resource>/<id>204 No Content

The following error codes can apply to any of the above requests:

NOTE: 5xx status codes may be generated by the server.

HTTP Status Code (client errors)Notes
400 Bad Request

Potential reasons:

  • Resource doesn't exist.
  • Request is incorrectly formatted.
  • Request contains invalid values.
403 ForbiddenIncorrect permissions to access the Resource.
404 Not FoundResource cannot be found.
410 GoneResource has been previously deleted.
415 Unsupported Media TypeIncorrect Accept header.


When a resource has been cached in the client, the client may set an If-Modified-Since header in HTTP date format on the request. If so:

General ResponseHTTP Status Code
Returns full modified resource200 OK
Returns an empty response for unmodified resource304 Not Modified

Use Cases


By chaining together sequences of calls to API endpoints, you can create, read, update, and delete objects using identifiers accessible through the returned JSON. For more information, see API Endpoints.

For more information on endpoint workflows, see API Workflows.

UI Integrations

The REST APIs can also be used for integrating the core transformation experience of the  Designer Cloud powered by Trifacta platform  into a third-party application. Using a series of URL-based calls, you can retrieve and display specified datasets in the Transformer page, where authenticated users can wrangle datasets controlled by the third-party application. See API - UI Integrations.

About This Documentation

  • Unless otherwise noted, the documentation and examples apply to version 3 (v3) of the  Designer Cloud powered by Trifacta platform  APIs.
  • Examples may require modification to work in your environment.

This page has no comments.