Log in Start free

Paste a snippet — or treat it like an API.

Widgets and forms have public embed scripts. In-app collection uses a server-minted identity token. Never put the workspace secret in the browser.

  • Paste an iframe snippet on any site
  • Signed identity tokens for in-app collection
  • A JSON config API for developers
Start free → Book a demo

Free to start · no credit card · a real person helps you set up

How it works

From first ask to public proof

Paste the snippet

An iframe and a script tag on any page.

Sign the user

Mint an identity token on your server.

Pass the token

Tie each response to the real user.

Or use the API

Pull config and widget JSON directly.

Why the embed

A snippet for anyone, an API for developers

Paste one iframe on any site, tie in-app responses to the real user with a signed token, or drive it all from a JSON API.

The simple way

Paste a snippet on any site.

Drop an iframe and a script tag anywhere. It works on plain HTML, Webflow, WordPress, or a React app.

  • One iframe + script, done.
  • Allows camera and microphone for video.
  • Works on any site or CMS.
<iframe src="app.qintr.com/embed/form/KEY/"  allow="camera; microphone"></iframe><script src="app.qintr.com/embed/form.js"></script>
In-app

Signed identity, minted server-side.

For in-app collection, mint a signed token on your server and pass it in — every response is tied to the real, logged-in user.

  • Mint a signed identity token server-side.
  • Pass identity=TOKEN to the embed.
  • Never put the workspace secret in the browser.
POST /dashboard/api/form-identity-token/  { external_id: "user_123" }→ …/embed/form/KEY/?identity=TOKEN
For developers

Config and widget JSON APIs.

Pull a form's config or a widget's data as JSON, and listen for postMessage events — build your own UI if you want.

  • GET /api/v1/forms/KEY/config/
  • GET /api/v1/embed/KEY/
  • React, iOS, and Android recipes in the docs.
GET /api/v1/forms/YOUR_KEY/config/GET /api/v1/embed/YOUR_KEY/// events: ready, resize, submitted, error
Keep exploring
Docs hubWeb, React, iOS, Android In-app CSATTypical embed use IntegrationsSlack, webhooks, events

Questions

A documented iframe pattern, not a separate npm package you must adopt.
No — never put it in the browser. Signed identity tokens are minted on your server and passed to the embed as a short-lived token.

Ready to put real customer voices on your site?

Start free in a couple of minutes — or talk to a real person first.

Start free → Book a demo

No credit card · a free plan that stays free · a real person helps you set up