When should we use API or inbound enrichment?
Last updated: June 21, 2026
Short answer
Use API or inbound enrichment when another system needs to send records to Kernel during a workflow and receive enriched results back programmatically.
This works well for 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.
What to send support
- Calling system.
- Expected request volume.
- Required input and output fields.
- Callback, polling, or status-handling preference.
- Destination system for results.