---
updatedAt: 2026-03-23T22:02:41.000Z
---

Fetch the complete documentation index at: https://developer.trulioo.com/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# Workflow Studio (API)

***

## slug: /wfs-api/index.html

Workflow Studio is a platform used to create fast and compliant onboarding flows. Via our new API, you get countless possibilities to take advantage of our flow builder and access our catalogue of services.

In order to use Workflow Studio with Document Verification, we highly recommend you integrate with one of our easy-to-use SDKs. We offer SDKs for [Web](/reference/web), [Android](/reference/android) and [iOS](/reference/ios), so pick the one that best suits your needs.

## 1. Initialize Workflow

Calling GET to [api.trulioo.com/wfs/interpreter-v2/flow/\{flowId}](/reference/flow) will allow you to retrieve details about your Workflow, such as which fields you should collect from your users.

You can get the `flowId` required to call this endpoint from your Implementation Specialist, or by accessing your Workflow in Workflow Studio, and getting the `flowId` from the address bar.

The initialize call will give you the following response:

```
{
  ...
  "elements": [
    {
      "id": "someUniqueId",
      "name": "FullName",
      "type": "text",
      "validations": [ ... ]
    }
  ],
  ...
}
```

Each field, such as FullName in this example, will be given a unique identifier. This identifier can then be used to submit your users' data when you make a POST call in Step 2.

This call also returns an `x-hf-session` in the header response, which you can use in Step 3.

## 2. Submit Fields

Each field from Step 1, such as FullName in this running example, will be given a unique identifier, which is used to submit your users' data when you make a POST call to [https://api.trulioo.com/wfs/interpreter-v2/submit/\{flowId}](/reference/submit):

```
{
  "someUniqueId": "usersFullName"
}
```

The POST call will result in the following response:

```
{
    "canGoBack": boolean,
    "id": "string",
    "shortCode": "string",
    "type": "trulioo_doc_v"
}
```

The `shortCode` is needed to launch the [DocV SDK](/reference/web).

## 3. (Optional) Web Page Redirect

By providing the `x-hf-session` in your API call, you can resume a Workflow session. This means that you can bring a user to a different webpage, and then allow them to continue their flow. This is done by making a very similar GET call to the one in Step 1: [https://launch-workflow.trulioo.com/\{flowId}?x-hf-session=\{x-hf-session}](/reference/submit).

## 4. Get User Data From Workflow Studio API

### Authenticate

Authentication requires a Client ID and Client Secret, which will be given to you by your Implementation Specialist.

> Note: These are not the same as the Client ID and Secret from the API Export Step of your workflow.

After calling [http://auth-api.trulioo.com/connect/token](/reference/authentication-recipe#/) , you should receive an authorization token in the `Token` field, which you will need in the query call below.

### Query User Data

A GET call to [https://api.trulioo.com/wfs/export/v2/query/client/\{x-hf-session}](/reference/getclientdata) will return the following:

```
{
  "id": "string", // corresponds to x-hf-session
  ...,
  "flowData": {
    "...": {
      "id": "...",
      "completed": boolean,
      "fieldData": { ... },
      "fileData": {},
      "serviceData": [
        ...,
        {
          ...,
          "transactionInfo": {
            "transactionId": "string"
          }
        }
      ]
    }
  }
}
```

<br />

## 5. Get User Data

To retrieve the user information as well as the detailed service level response information, use a GET call to the <Anchor label="Retrieve profile data from client API" target="_blank" href="https://developer.trulioo.com/reference/getclientdata">Retrieve profile data from client API</Anchor>

When calling this API ensure to use the `x-hf-session` as the parameter for the `clientid` in the URL and set the `includeFullServiceDetails` parameter to `true` to retrieve the comprehensive profile data from the client's workflow submissions.

<br />