Help · API

Lead API

Public endpoint to create or match CRM accounts from website forms, daily agents, or your server. Never put your API secret in browser JavaScript or public repos.

CRM and Connect are licenses in one Pipeline Intelligence platform. Every workspace uses https://app.pipelineintel.io/api/public/leads with its own workspace ID and API secret.

One platform endpoint

Use the unified Next address. Your workspace ID and secret determine which workspace receives the lead.

POST https://app.pipelineintel.io/api/public/leads

Get the secret from that product’s Admin → Integrations → Website form → For developers.

Use your workspace credentials

In Admin → Integrations → Website form → For developers, copy the workspace ID and API secret. The endpoint is the same for CRM and Connect licenses.

Content type: application/json. One lead per request — for a list, loop and POST each row.

Authentication

Send the workspace API secret in one of these ways:

Authorization: Bearer YOUR_API_SECRET (recommended)
X-Lead-Intake-Secret: YOUR_API_SECRET

Also include tenantId (workspace ID) in the JSON body unless you are using a form embed token (hosted form path — not needed for Twin-style server posts).

Security: Treat the secret like a password. Rotate it in Admin if it leaks. Do not publish live secrets, workspace IDs, or form links with tokens on marketing pages.

Fields

Which fields are required is configured per workspace under Admin → Website form → Form fields. Company is always required. Defaults also require name, email, phone, industry / use case, and seats.

Pipeline field	Also accepts
`company`	`company_name`, `organization`, `account`
`name`	`contactName`, `full_name`, or `first_name` + `last_name`
`email`	`email_address`, `contact_email`
`phone`	`phone_number`, `mobile`
`industry`	`industryUseCase`, `useCase`, `use_case`
`seats`	`seatCount`, `numberOfSeats`, `seatsNeeded`
`message`	`notes`, `comments`, `description`
`formName`	`form`, `form_id`, `utm_campaign`
`tenantId`	Workspace ID from Admin

Nested customFields, fields, or properties objects are flattened automatically.

Example

This example works for every Pipeline Intelligence workspace.

curl -X POST 'https://app.pipelineintel.io/api/public/leads' \
  -H 'Authorization: Bearer YOUR_API_SECRET' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenantId": "WORKSPACE_ID",
    "company": "Acme Logistics",
    "name": "Jane Doe",
    "email": "jane@acme.example",
    "phone": "+12155550100",
    "industry": "Freight brokerage",
    "seats": "25",
    "message": "Interested in Connect + CRM",
    "formName": "twin-morning"
  }'

Daily lead agents (Twin, Zapier, Make, etc.)

If a tool offers “REST API” or “inbound webhook” to send a morning lead list, set the destination to the full unified endpoint above — not only the path /api/public/leads.

Schedule the agent daily (or whenever leads are ready).
Use https://app.pipelineintel.io/api/public/leads.
POST one lead per request; loop the list.
Map company, name, email, phone, industry, seats, and optional notes.
Set formName to something stable like twin-morning so reps see the source.

Twin’s own “inbound webhook” usually means something calling Twin to start an agent. For sending leads into Pipeline, Twin should call this Lead API instead.

What happens in Pipeline

Leads create or match CRM accounts and arrive unassigned.
Matching email on an existing account logs activity instead of duplicating.
care@pipeline.care is emailed on every submission (plus any extra addresses you configure).
Your team also gets in-app Signal alerts.

Website form without coding

Prefer the hosted form? In Admin, copy the form link or website snippet and paste it on your site. No API key in the browser.

← Help home · Home