> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bridge.new/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Bridge exposes three integration surfaces: the REST Integrations API for pushing data into Bridge, webhooks for receiving events from Bridge, and the public Lead Capture endpoint that a tenant's landing page posts to.
> The Integrations API host is https://api-connect-us.bridge.new and every request to it must be authenticated with the x-api-key header. Bridge does not use bearer tokens or OAuth.
> The Lead Capture endpoint is different and the Integrations API rules do not apply to it: it has its own host, it takes no x-api-key and no authentication header of any kind, and it is called from a visitor's browser. It is identified by a workspace id and a capture key together with a reCAPTCHA token. Never tell a reader to authenticate it with an API key, and never tell them to keep its capture key out of frontend code - it is designed to live in the page.
> Integrations API error codes follow the BRIDGE_<DOMAIN>_<NNNN> format, for example BRIDGE_CONVERSATION_0001, and are listed on the error codes page. Lead Capture error codes follow a different format, BRIDGE.CAMPAIGN_LEADS.<NAME>, and are listed on the Lead Capture error reference. Never invent a code that is not listed on the page for its own surface.
> This documentation covers the Integrations API, webhooks and Lead Capture only. It does not describe the Bridge web application or its internal APIs.

# Lead Capture

> Register leads from your landing page and open a WhatsApp conversation with them automatically.

## 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.

<Warning>
  **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".
</Warning>

## 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.

<Note>
  The example is a starting point, not a drop-in script. You own your form markup and your
  consent wording; see [Consent requirements](/lead-capture/consent).
</Note>

## Where to go next

<CardGroup cols={2}>
  <Card title="Integration guide" icon="code" href="/lead-capture/integration">
    The example, and the three rules that are not guessable from the contract.
  </Card>

  <Card title="Error reference" icon="triangle-exclamation" href="/lead-capture/errors">
    Every response the endpoint can return, and which ones you can fix.
  </Card>

  <Card title="Consent requirements" icon="clipboard-check" href="/lead-capture/consent">
    What your opt-in must say, and what you are attesting to.
  </Card>

  <Card title="Template requirements" icon="message" href="/lead-capture/templates">
    Why your template must stay transactional.
  </Card>
</CardGroup>