canonical: https://jentic.com/apis/mloflo.com/mloflo

# Mloflo API

Jentic publishes the only available OpenAPI specification for Mloflo API, keeping it validated and agent-ready. The Mloflo API exposes Zapier-style webhook endpoints for the Mloflo mortgage lending platform. The three endpoints let external systems push new mortgage leads into Mloflo and subscribe or unsubscribe from milestone status update notifications, so a connected CRM or lead source can stay in sync with loan-stage transitions.

## For AI agents

Push new mortgage leads into the Mloflo lending platform and manage Zapier-style milestone status update subscriptions across three webhook endpoints.

## Scope

Does not handle credit pulls, document signing, or loan funding - use for Mloflo Zapier-style lead intake and milestone webhook subscriptions only.

## Capabilities

- Submit a new mortgage lead to Mloflo
- Subscribe a webhook URL to milestone status updates
- Unsubscribe a previously registered milestone webhook

## Use cases

### Lead Capture to Mortgage Pipeline

A landing page form or marketing tool captures borrower interest and pushes the contact details into Mloflo via the add-lead webhook. Mloflo creates the lead record, assigns it to the appropriate loan officer, and the borrower enters the standard intake flow without manual rekeying. This avoids CSV imports and keeps top-of-funnel sources synchronised.

Example prompt: POST the captured form data to `/webhooks/zapier/add-lead` with borrower name, email, phone, and loan amount

### Milestone Status Sync to External CRM

A lender's external CRM or marketing automation tool registers a webhook endpoint with Mloflo so it receives a notification each time a loan moves through milestones such as application submitted, conditional approval, or clear to close. This keeps borrower comms timely without continuous polling and lets ops teams trigger downstream tasks immediately.

Example prompt: Subscribe https://crm.example.com/hooks/mloflo to milestone updates via POST `/webhooks/zapier/milestone-status-subscribe`

### Webhook Lifecycle Cleanup

When a third-party CRM is decommissioned or rotates its webhook URL, the existing subscription should be removed so Mloflo stops sending updates to a dead endpoint. The unsubscribe endpoint takes the previously registered URL or subscription identifier and tears it down cleanly.

Example prompt: Call POST `/webhooks/zapier/milestone-status-unsubscribe` with the old CRM webhook URL when migrating to the new CRM

### Agent-Driven Lead Routing

An agent discovered through Jentic listens for new leads in a marketing tool, enriches them with public data, and pushes the cleaned record into Mloflo as a mortgage lead. Jentic stores any required webhook secret in its credential vault so the agent issues the call through Jentic's execution layer.

Example prompt: Use Jentic to find the Mloflo add-lead operation and execute it for each new qualified inquiry from the marketing source

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/webhooks/zapier/add-lead` | Submit a new mortgage lead |
| POST | `/webhooks/zapier/milestone-status-subscribe` | Subscribe a webhook to milestone updates |
| POST | `/webhooks/zapier/milestone-status-unsubscribe` | Unsubscribe a webhook from milestone updates |

## Key resources

- **Leads** — Webhook for pushing new mortgage leads
- **Milestones** — Subscribe and unsubscribe webhooks for loan milestone status updates

## Why Jentic

- **Setup:** Wiring the Mloflo API by hand means coding its open webhook POSTs for lead intake and milestone subscribe and unsubscribe, then handling payload formatting yourself. Through Jentic you install once, import the Mloflo API from the API Directory, and your agent calls it.
- **Permission scoping:** Mloflo's lead and milestone targets travel in the request body rather than the URL path, so scope your agent by limiting it to the operations it needs, such as adding a lead or subscribing to milestone status. You leave out the unsubscribe operation so the agent enrolls leads without tearing down existing subscriptions.
- **Credential handling:** Any Mloflo connection settings are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a lead to Mloflo' or 'subscribe to milestone updates', and Jentic returns the matching Mloflo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid API** — Bank account and income verification for lending workflows
- **HubSpot Account Info API** — CRM platform that can receive Mloflo milestone webhook updates
- **Salesforce REST API** — Enterprise CRM that can host the lead pipeline

## FAQ

### Why is there no official OpenAPI spec for Mloflo API?

Mloflo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mloflo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Mloflo API use?

The Mloflo webhook endpoints are reached via the Zapier integration model rather than a public bearer or API key scheme. Coordinate with Mloflo support to register your integration and receive any required signing secret. Through Jentic any shared secret is held in the credential vault and injected at execution time.

### Can I add a mortgage lead with the Mloflo API?

Yes. POST the borrower payload to `/webhooks/zapier/add-lead.` Mloflo creates the lead and routes it into the standard intake pipeline. The webhook returns success or validation errors so the caller can retry.

### What are the rate limits for the Mloflo API?

Mloflo's public webhook endpoints are intended for one-event-at-a-time use through Zapier-style integrations. Bulk imports should be paced and coordinated with Mloflo support rather than fired in parallel against the webhook endpoints.

### How do I subscribe my CRM to milestone updates through Jentic?

Search Jentic for subscribe mloflo milestones, load the schema for POST `/webhooks/zapier/milestone-status-subscribe`, and execute with your CRM's webhook URL. Mloflo will then push milestone status events to that URL.

### Can I unsubscribe a webhook when migrating CRMs?

Yes. Call POST `/webhooks/zapier/milestone-status-unsubscribe` with the previously registered URL or subscription identifier. Mloflo stops sending milestone events to that endpoint.

### Can I limit what my agent is allowed to do with the Mloflo API?

Yes. Because you run Jentic One yourself, your own rules decide which Mloflo operations and connection settings the agent may use. Since Mloflo's lead and milestone targets travel in the request body rather than the URL path, you scope the agent by allowing only the operations it needs, such as adding a lead or subscribing to milestone status updates. For example, you can leave out the unsubscribe operation so the agent enrolls leads without tearing down existing milestone subscriptions.