Lead Intake Endpoints Explained

A lead intake endpoint is a unique webhook URL your organization generates so an external lead vendor can POST lead data to KamoUniverse directly, instead of you importing a file by hand. Each endpoint is tied to one vendor/product/market combination (optionally — these can be left unset), and carries its own rate limit and max payload size to protect against a vendor sending too much, too fast.

Lifecycle: Pending → Configured

A new endpoint starts Pending. It only becomes Configured once at least one field mapping is saved, connecting the vendor's JSON field names to KamoUniverse's system lead fields — see How to Map Intake Endpoint Fields Payloads can arrive and be logged before that point, but they won't turn into leads until mapping exists.

What happens to incoming data

Every payload a vendor sends is logged — visible in the endpoint's Queue (see How to Review an Endpoint’s Incoming Leads) — regardless of whether it successfully becomes a lead. This gives you a full audit trail independent of whether mapping was configured correctly at the time.

An endpoint can be disabled (rejecting new requests without losing its history) or deleted (permanently, along with its payloads and mappings) — see How to Edit, Disable or Delete an Intake Endpoint