Skip to main content

​
Integration architecture

​
Data flow

​
Source boundary

A source webhook is bound to a specific channel or list source. The source ID, external ID, mapping, and duplicate rules determine how incoming data is processed. An HTTP success can mean the request was newly accepted or recognized as an idempotent replay. Read the response status instead of assuming every success created a new record.

​
Buyer boundary

Airlead sends a lead.delivered event to the configured buyer webhook. The payload includes a transactionId, which the buyer must retain for later lifecycle callbacks. Technical acceptance and commercial confirmation are separate:
  1. Buyer webhook returns 2xx to acknowledge receipt.
  2. Buyer calls the lifecycle endpoint to report the commercial outcome.

​
Connect boundary

Connect delivers between Airlead workspaces and is configured through a partnership, endpoint, terms, and field mapping. It is not a general API-key-based REST interface.

​
Workspace isolation

All data belongs to a workspace. Webhook paths identify the target channel, source, or list and are protected by the secret configured for that resource. Never reuse resource IDs or secrets from another workspace or environment.

​
Auth layers

Next: Authentication · Lead ingest · Outbound delivery