POST body
Passing data through the body of a HTTP request.
In addition to pre-populating answers using URL parameters, It's possible to POST
form data into Formsort. This may be preferable, as answers will not appear within the URL at any point - POST bodies are part of the HTTP body and are encrypted with HTTPS.
To POST data, the user must navigate to the deployed URL of your flow with the answers as form data in the body of the form, using the answer variable name as the name
of the input.
The POST must be a navigation request.
You cannot just POST form data to Formsort using AJAX and then redirect the user.
Example: POSTing from a <form>
Normally, when you access a page directly in a browser, or by clicking a link, the browser will send a GET request, which cannot contain a body.
On the other hand, when submitting a <form>
in HTML, the browser will navigate with a POST
method, which will actually redirect the user to that URL.
Here's a working example as a standalone html page, that would redirect the user to a flow with cat_name
set to "Olivia"
and the cat_color
set to gray
:
Of course, you could also use <input>
attribute type="hidden"
if the data you wish to pass should not be user editable.
Example: POSTing in javascript
If you cannot have a <form>
, or it doesn't make sense for your UX, you can create a form
element on the fly and synthetically submit it:
Build up a
<form>
in your click handlerAdd the answers:
For questions that accept a single answer, such as text questions, use
<input type="hidden">
. Assign the answer's variable name as the element'sname
.For questions that accept multiple answers, use a
<select>
element, adding each answer as an<option>
. Assign the answer's variable name as the<select>
element'sname
. Make sure the<select>
has themultiple
property set totrue
, and each<option>
has theselected
property set totrue
.
Finally,
.submit()
the form instance.
Here's a working example as a standalone html page, that would redirect the user to a flow with cat_name
set to "Olivia"
:
Pre-posting data for a responder UUID
In the future, we'd like to support pre-posting data for a responder UUID, so that you can POST data asynchronously before you actually navigate the user to the flow, at which point the data will be retrieved.
This is an unimplemented feature - chat us if you'd be interested in this.
Last updated