Redirects & Callbacks
Once a Task is created and is live, handling Worker entrances and redirecting them back to WXET is the primary concern. Determining where a Worker goes when they enter a Task is entirely determined by the live_url attribute. This formatted string is a url that get's substituted with a range of possible variables. These are available to the Survey or Task platform to use for their own purposes. The only required variable on live_url is the session_uuid because it is a required query parameter when redirecting the Worker back to WXET.
Worker Entering the Task
When WXET's Supplier Network determines to send a Worker into the Task, the Worker will enter the Task's live_url with an HTTP Redirect from the WXET platform. Every live_url must have a {{session_uuid}} and the Survey or Ephemeral Task platform must store that identifier. When a live_url is set, it must look something like:
https://enter.survey.com/?foo=1234&abc={{session_uuid}}
and when the Worker actually enters the Task, they'll be redirected to a URL that looks something like:
https://enter.survey.com/?foo=1234&abc=fb39dcedaeaf4e37887c1134ba98c743
Using this string replacement pattern allows WXET Accounts to construct URLs to match the requirements of your Survey or Task platform. In total, the following variables are all support for passing into a Task.
session_uuid(required): The unique identifier for the session.task_uuid: The unique identifier for the task.project_uuid: The unique identifier for the project.account_uuid: The unique identifier for the account.respondent_uuid: The unique identifier for the respondent.cpi: If a dynamic pricing strategy is used, this is the selected price.
A formatted variable can also be a URL Path into a Survey or Task platform, so the following url https://enter.survey.com/task/{{project_uuid}}/{{session_uuid}}/ will correctly format to enter into the task like: https://enter.survey.com/task/b29c64b940c7488589ae532bb51bbbc2/e4293c79ac3a442b860cfd66bfb485bf/
Worker finished their Task Attempt
Regardless of the outcome, a WXET Account must issue a POST to the Set Wall Status endpoint before redirecting the Worker back into the WXET platform. This is
In the example above, I used the literal values for the cURL. However, you can see below the Enum definitions for WXETStatus and WXETStatusCode1
Once this POST has been issued, a Worker can be HTTP 302 Redirected into the following URL: https://api.wxet.org/v2/wall/return/?session_uuid=<session_uuid> and WXET will ensure they are returned back to their respective WXET Supplier Network partner.