Developer docs

What in-app voice feedback is, the three parties involved and who calls what.

On this page

WTN lets the people who use your app tell you what they really think, by voice or by typing, in their own language. A person taps "Feedback" in your app, a short conversation opens in the phone's browser, and you receive aggregated results and signed webhook events. There is no SDK to install and no login for the person.

The three parties

  • Your app (on the phone). It registers itself with a public campaign code and opens the feedback page. It never holds a secret.
  • Your server. It holds your API key, optionally creates one-time launch links, reads results and receives webhooks.
  • WTN. The API at api.wtn.live and the feedback page at survey.wtn.live.
The three parties and who calls whatYour app registers and sends heartbeats to WTN with the public campaign code and no secret, then opens the feedback page with its access token. Your server uses its API key to create launch links and read results, and WTN sends signed webhooks to your server.Your appon the phoneWTNapi + surveyYour serverholds the API keyregister, heartbeatcampaign code, no secretdeviceId + tokensaccessToken, refreshTokenopen the page/p/<code>#dt=<accessToken>launch link, results, devicesAPI key (secret)signed webhooksfeedback.receivedone-time launch linkoptional, signed mode

Who calls what:

CallerCallCredential
Your appregister, heartbeatnone (the campaign code is public)
Your appopens the feedback pagethe accessToken, in the URL fragment
Your serverlaunch link, results, installs, devices, webhooksAPI key (secret)
WTNwebhook deliveries to your serversignature you verify

Where to go next

Everything here is additive and versioned by path (/api/v1). The machine-readable contract is the OpenAPI document.