When should we use API or inbound enrichment?
Last updated: June 22, 2026
Use API or inbound enrichment when another system needs to send records to Kernel and receive enriched results back programmatically.
This fits lead routing, workflow tools, custom services, and systems that create or update records continuously.
Best fit
A system needs enrichment during a workflow.
Records arrive continuously.
The customer can poll or handle asynchronous status.
Results will be written back by the customer's service, automation, or configured Kernel integration.