Onfido Studio migration guide (v4 to v3.5)
Start here
Following the general release of Onfido Studio in API v3.4 and v3.5, all integrations using v4 must be migrated to v3.5.
API v4 was used for initial integrations prior to Studio's official release. This API version will soon be decommissioned, after which all v4 integration requests will fail.
This guide will help those who are still using API v4 to migrate their integration over to v3.5.
Endpoint mapping v4 → v3.5
In API v3.5, a number of endpoints have changed, some have been added, while others have been deprecated. You will find specific details on the endpoint mapping in the table below:
v4 | v3.5 | Description |
---|---|---|
Workflow run endpoints | ||
POST v4/workflow_runs | POST v3.5/workflow_runs | Creates a workflow run |
GET v4/workflow_runs/{workflow_run_id} | GET v3.5/workflow_runs/{workflow_run_id} | Retrieves a workflow run |
N/A | GET v3.5/workflow_runs | Retrieves the workflow runs of the client |
Task endpoints | ||
N/A | GET v3.5/workflow_runs/{workflow_run_id}/tasks | Retrieves the tasks for a workflow run |
N/A | GET v3.5/workflow_runs/{workflow_run_id}/tasks/{task_id} | Retrieves a specific task for a workflow run |
Workflow links | ||
POST v4/workflow_links | N/A | Note: This functionality is now under "POST /workflow_runs" |
DELETE v4/workflow_links/{workflow_link_id} | N/A | Note: This functionality is no longer supported |
Request payloads and response bodies
As a consequence of endpoint changes in API v3.5, the request payloads and response bodies have also been modified. You will find specific details in the tables below:
Workflow run endpoints
v4 | v3.5 |
POST v4/workflow_runs | POST v3.5/workflow_runs |
Request payload example:
|
Request payload example:
|
Response body example:
|
Response body example:
|
Major differences:
- Applicant data is no longer passed through the create request, an applicant ID is used instead. Find further documentation here
- The Smart Capture Link URL is now created together with a workflow run and returned in the response body. Find further documentation here
- Task information can now be obtained using a dedicated endpoint, not in the response body
- The
finished
attribute was removed, information can be obtained from thestatus
attribute -
The
state
attribute has been replaced by the status attribute:in_progress
→awaiting_input
,awaiting_client_input
orprocessing
clear
→approved
fail
→declined
manual_review
→review
cancelled
→abandoned
orerror
- The
version_id
attribute has been renamedworkflow_version_id
v4 | v3.5 |
GET v4/workflow_runs/{workflow_run_id} | GET v3.5/workflow_runs/{workflow_run_id} |
Response body example:
|
Response body example:
|
Major differences:
- Applicant data is no longer available in the workflow run response, but can be retrieved via API or the Studio Dashboard. For mapping applicant data to output any fields from the profile, please refer to our API reference or Studio product guide for workflow run output documentation
- Task information can now be obtained using a dedicated endpoint, not in the response body
v4 | v3.5 | Description |
GET v3.5/workflow_runs | ||
N/A | New | A new endpoint available under v3.4 and v3.5 to retrieve the workflow runs of the client. Find further documentation here |
Task endpoints
v4 | v3.5 | Description |
GET v3.5/workflow_runs/{workflow_run_id}/tasks | ||
N/A | New | A new endpoint available under v3.4 and v3.5, to retrieve the tasks for a workflow run. Find further documentation here |
GET v3.5/workflow_runs/{workflow_run_id}/tasks/{task_id} | ||
N/A | New | A new endpoint available under v3.4 and v3.5, to retrieve a specific task for a workflow run. Find further documentation here |
Workflow links endpoints
v4 | v3.5 | Description |
POST v4/workflow_links | ||
Deprecated | Deprecated endpoint. This functionality is now managed in the Create Workflow Run endpoint | |
DELETE v4/workflow_links/{workflow_link_id} | ||
Deprecated | Deprecated endpoint, no longer exists under v3.4 or v3.5 |