Initiating a test workflow via signedURL

Use the test signed-URL endpoint with the workflow ID. The returned launch URL contains /test/ and runs the current unpublished draft without creating live transactions.

Make sure you have:

  • A valid workflow: workflow validation errors must be resolved before the test can start.
  • A Workflow Studio API credential with access to the account that owns the workflow.
  • Permission to run transactions for that account.
  • The workflow ID for the workflow you want to test.

Step-by-step

Prepare the workflow.

  1. Identify the correct workflow ID.
  2. Copy the workflow ID for the workflow. Use this value as dev_flow_id in the request below.

Request a test signed URL.

  1. Send an authenticated POST request to the test signed-URL endpoint.
POST {wfs_api}/interpreter-v2/test/signed-url/{dev_flow_id}
Authorization: Bearer {wfs_api_token}
curl --request POST \
"${WFS_API}/interpreter-v2/test/signed-url/${DEV_FLOW_ID}" \
--header "Authorization: Bearer ${WFS_API_TOKEN}"

Read the response.

The response includes the signedUrl to open and the endClientId created for the test transaction. If an existing end client is supplied using your standard signed-URL integration, the URL remains scoped to that end client and flow.

{
  "signedUrl": "https://launch.workflow.dev.trulioo.com/test/{dev_flow_id}?st={signed_token}",
  "endClientId": "{end_client_id}"
}

Open the returned signed URL.

Open signedUrl in a browser to start the hosted test experience. The path will contain /test/.

https://launch.workflow.dev.trulioo.com/test/68fc1e4817db021adc06dbc7?st={signed_token}