1DB
Sign inGet started
IntegrationSend leads on

Partner APIs

A forwarding rule sends each new lead to an https endpoint: your own API, Zapier, Make, a CRM webhook or a partner who buys leads. Unlike a webhook, it’s paced and retried, for destinations where every lead has to arrive.

  • Paced
  • Retried
  • Field mapping

How it works

  1. 1

    Create a rule

    Name it, give the endpoint and the destination’s auth token, then turn it on.

  2. 2

    Pick the payload

    The generic profile sends 1DB’s own lead shape: contact, request, location, page, attribution and every field as submitted.

  3. 3

    Leads are sent at the destination’s pace

    Requests are spaced out so the partner’s rate limits aren’t hit, and retried when their API is down.

Terminal
npx @1db/cli forwarding add --name "Our API" \
  --endpoint https://api.acme.com/leads \
  --auth-token ... --profile generic --enable

Good to know

Stable payload
Empty values are left out. New fields may be added; existing ones are never renamed.
Defaults fill the gaps
Lead type and product type come from the lead, else the form’s default, else the website’s.
From an agent or the CLI
1db forwarding add creates a rule, and agents can manage them with the routing scope.

Works alongside