Skip to main content

​
What this does

Your landing page posts a lead to Bridge. Bridge then opens the WhatsApp conversation for you, using an approved template. You do not send the message; we do.
A 202 response means the lead was accepted, not that a message was sent. The first WhatsApp message is transmitted later by a separate service. Your thank-you copy must say something like “we’ll message you shortly” — never “we’ve messaged you”.

​
What you need, and where it comes from

Four values: the endpoint URL, your captureKey, the reCAPTCHA site key, and the reCAPTCHA action name. You do not assemble them by hand. In the Bridge admin console, under LeadScout → Capture snippet, an administrator of your workspace generates an integration example that already contains all four. They hand that block to whoever builds the page — that person never needs console access.
The example is a starting point, not a drop-in script. You own your form markup and your consent wording; see Consent requirements.

​
Where to go next

Integration guide

The example, and the three rules that are not guessable from the contract.

Error reference

Every response the endpoint can return, and which ones you can fix.

Consent requirements

What your opt-in must say, and what you are attesting to.

Template requirements

Why your template must stay transactional.