What Is API Intake?
API intake is a method of submission where data and documents are transferred automatically between systems via APIs.
In MCA and small business lending, this is especially useful for high-volume brokers, ISOs, and platforms that already operate their own systems and want a seamless way to submit deals.
API intake typically appears when partners need tighter integrations or want to bypass email submissions entirely. Operators use it to increase speed, reduce manual handling, and make sure every packet enters the workflow in a structured format.
How Does API Intake Work?
API intake operates through a secure, system-to-system exchange.
- Submission push: A broker, ISO, or partner platform pushes a deal packet directly into Heron through an API endpoint.
- Data transfer: Key fields and documents such as applications, IDs, and bank statements are included in the payload.
- Validation: The system validates the data format and checks that required files are present.
- Workflow entry: The submission enters the processing pipeline as if it had been captured from an inbox or portal.
In Heron, API intake connects directly into the standard workflow, so all automation applies.
- Direct ingestion: Partners push submissions into Heron APIs without email forwarding or portal uploads.
- Automated scrubbing: Completeness, deduplication, and fraud checks run instantly on the incoming payload.
- Structured CRM write-back: Parsed fields and documents are written to the CRM in real time.
- Next action: Deals are routed to underwriting queues, missing-info requests, or task creation depending on the checks.
This makes API intake the fastest possible way to move a submission into a “ready to underwrite” state.
Why Is API Intake Important?
For brokers and funders, API intake is valuable because it eliminates the delays and risks of email submissions. There are no inbox rules to maintain, no missed attachments, and no manual sorting.
It also enables scale. High-volume partners can send hundreds of deals directly into Heron without overwhelming staff. This reduces touches, shortens turnaround time, and creates a more reliable submission pipeline.
Common Use Cases
API intake is used in high-volume, tech-enabled workflows where speed is critical.
- Allowing partner platforms to push deals directly into Heron without email.
- Sending complete applications with bank statements as structured API payloads.
- Bypassing shared inboxes to avoid lost or delayed submissions.
- Writing clean data fields into the CRM automatically as submissions arrive.
- Handling spikes in volume smoothly by accepting bulk API submissions.
FAQs About API Intake
How does API intake reduce manual work for brokers and funders?
Heron connects directly to partner platforms, which means no one has to open emails, save attachments, or copy data. Submissions arrive in a ready-to-process format.
What outputs should teams expect from API intake?
Teams receive clean CRM records with fields like applicant name, business details, submission date, and attached documents already mapped. This makes deals immediately available for underwriting.
How does API intake handle incomplete or invalid submissions?
If required fields or documents are missing, Heron flags the submission and triggers a missing-info workflow. This makes sure only usable packets advance to underwriting.