Website widget & application links
There are three ways to hand an intake to an insured, from zero-code to fully embedded:
| Surface | What it is | Where it lives |
|---|---|---|
| Application link | Hosted page that starts a brand-new application | https://bindly.insure/start/<key> |
| Website widget | The same wizard embedded in your site via one script tag | Your domain, in an iframe |
| Insured link | A link to one existing application, for the insured to finish | https://bindly.insure/fill/<token>, minted per session in the app |
The first two are powered by a publishable embed key (pk_…) from
Integrations → Website widget. The insured link needs no key — it’s
minted per session with the Insured link button on the session page and
can be forwarded person to person until the application completes (a broker
can reopen a completed application to collect more).
Install the widget
Section titled “Install the widget”<script src="https://bindly.insure/embed.js" data-embed-key="pk_..."></script>That’s the whole install. The wizard renders where the script sits (inline mode), collects the basics in a few short steps, then hands the insured to the conversational intake. Forms are recommended automatically per submission from the business class — they are never pinned to the key, and your workspace’s Preferred forms curation restricts what the matcher may pick.
Options
Section titled “Options”All options are data-* attributes on the script tag:
| Attribute | Effect |
|---|---|
data-mode |
inline (default) or popup — popup renders a launcher button that opens the wizard in an overlay |
data-button-text |
Popup launcher label (default “Start your application”); setting it implies popup |
data-button="false" |
Popup mode without the built-in launcher — wire your own trigger |
data-color |
Explicit brand color override; without it the key’s stored brand color applies |
data-target |
CSS selector to mount into (waits for SPA frameworks to render it) |
Wiring your own buttons: add data-bindly-open to any element (delegated —
works for elements rendered later), or call window.Bindly.open() /
window.Bindly.mount(selectorOrElement).
Security model
Section titled “Security model”The wizard iframe asks the host page to mint the session, so the
browser’s Origin header is checked server-side against the key’s
allowed domains. A leaked publishable key can’t be used from a domain
you didn’t allowlist. The hosted /start/<key> page needs no domain
allowlist (it runs on Bindly’s origin).
Branding
Section titled “Branding”- Logo — uploaded on Agency profile; shown on the wizard, the hosted page, and the insured chat. The embedded widget shows your logo and no Bindly mark.
- Brand color — stored per key on Integrations → Website widget (accent color for buttons, focus rings, selection).
- Button text and mode — stored per key, overridable per page via the attributes above.
Limits
Section titled “Limits”- Widget/hosted-link session creation is rate-limited per key: 20 sessions per hour, 60 per day. Per-session insured links are not rate-limited.
- New sessions count against your plan’s monthly session allowance, whichever surface creates them.
- Insured uploads on the intake are capped at 20 MB per file, 25 documents per application.