Developers introduction

Airlead integrates with source and buyer systems through HTTPS JSON webhooks. Choose the guide by the direction in which lead data moves.

Choose an integration

Goal	Start here
Send leads to Airlead	Lead ingest
Walk through sample → live → transaction	End-to-end ingest example
Receive buyer deliveries from Airlead	Outbound delivery
Confirm, reject, cancel, or report payout	Partner lifecycle
Connect two Airlead workspaces	Connect integration
Receive supported inbound email	Email inbound
Use tokenized partner upload links	Share and upload links

Base URL

Production:

https://app.airlead.de

Use the environment-specific host provided by Airlead for staging or testing.

Integration principles

Treat IDs as opaque strings.
Send and accept application/json.
Use TLS for every request.
Store secrets outside source code and logs.
Use stable external IDs for ingest retries.
Store transaction IDs for lifecycle callbacks.
Retry transient failures with exponential backoff and jitter.
Do not retry validation or authentication failures without correcting the request.

Public vs. in-app endpoints

This documentation covers supported partner webhook endpoints. The Airlead web app also uses session-authenticated endpoints internally. Those endpoints are not a public integration contract unless they appear in this documentation and the OpenAPI specification. Next: Integration architecture · Authentication · Errors, retries, and limits