canonical: https://jentic.com/apis/ncinomortgage.com/ncinomortgage # Ncinomortgage SimpleNexus API (SNAPI) The SimpleNexus API (SNAPI) by nCino Mortgage provides programmatic access to a digital mortgage platform that originators, loan officers, and integration partners use to manage borrowers, loan applications, loans, loan officers, and webhooks. The 52-endpoint surface covers borrower onboarding, document and credit-report retrieval, consent-document handling, and form-request workflows. Bearer-token authentication scopes access to a tenant's loan pipeline and supports webhook subscriptions for downstream automation. ## For AI agents Manage mortgage borrowers, loan applications, documents, credit reports, and webhook subscriptions inside the SimpleNexus digital mortgage platform. ## Scope Does not handle pricing engines, e-signature execution, or core LOS underwriting decisions - use for borrower, application, document, and webhook management in SimpleNexus only. ## Capabilities - Onboard a mortgage borrower and retrieve their credit report and consent documents - Track loan applications from intake through underwriting using application endpoints - Manage active loans assigned to a loan officer including status updates - Trigger borrower notifications and form requests for missing documents - Subscribe to webhooks for loan status, application, and document events - Retrieve loan officer profiles and portfolio assignments ## Use cases ### Borrower Onboarding Automation Lenders integrate SNAPI to automate borrower onboarding from a website lead-capture form. POST /borrowers creates the borrower, the credit-report and consent endpoints attach required disclosures, and webhook subscriptions notify the LOS when documents are signed. Replaces manual data entry that previously took 30 minutes per borrower. Example prompt: Call POST /borrowers with applicant details, then call GET `/borrowers/{borrower_id}/credit-reports` to fetch the credit pull ### Loan Officer Pipeline Management Loan officers and team leads pull their current pipeline, filter by application stage, and assign tasks to borrowers. The /loan-applications, /loans, and /loan-officers endpoints together surface a real-time view of the pipeline that can feed CRM dashboards or Slack notifications. Example prompt: Call GET /loan-applications, filter to loans assigned to a specific loan_officer_id, and post the pipeline summary to a CRM ### Document Collection via Form Requests When an underwriter needs additional documentation, the integration creates a form request that prompts the borrower in the SimpleNexus app. POST `/borrowers/{borrower_id}/form-requests` issues the request, GET lists outstanding requests, and webhook events notify the back office when the borrower uploads. Cuts document-collection cycle time from days to hours. Example prompt: Call POST `/borrowers/{borrower_id}/form-requests` with form_id and a due date; subscribe to the form-request webhook for completion notifications ### Agent-Assisted Mortgage Operations An AI agent embedded in a loan officer's workflow looks up borrower status, requests documents, and sends notifications without the officer leaving the chat window. Jentic resolves natural-language requests to the correct SNAPI endpoints and stores the bearer token in the encrypted vault. Example prompt: Search Jentic for 'request missing documents from borrower', execute POST `/borrowers/{borrower_id}/form-requests` with the form_id ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/borrowers` | List all borrowers | | POST | `/borrowers` | Create a borrower | | GET | `/borrowers/{borrower_id}/credit-reports` | List credit reports for a borrower | | POST | `/borrowers/{borrower_id}/form-requests` | Create a form request for a borrower | | GET | `/loan-applications` | List all loan applications | | POST | `/borrowers/{borrower_id}/notify` | Notify a borrower | ## Key resources - **Borrowers** — Create, retrieve, and delete borrower records and their credit reports, consent documents, letters, and form requests - **Loan Applications** — Track applications through the origination pipeline - **Loans** — Manage active loans and their statuses - **Loan Officers** — Retrieve loan officer profiles and portfolio assignments - **Webhooks** — Subscribe to events for loans, applications, and documents ## Why Jentic - **Setup:** Wiring SimpleNexus by hand means learning its bearer token auth on the api.simplenexus.com host, mapping borrower, application, document, and webhook calls, and handling errors yourself. Through Jentic you install once, import the SimpleNexus API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** SimpleNexus puts the borrower id in the URL path (`/borrowers/{borrower_id}/...`), so a rule can pin your agent to one borrower: it can read that borrower's credit reports and request forms. You choose the operations it may call, so creating a borrower or sending notifications are not included unless you add them. - **Credential handling:** Your SimpleNexus bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'request missing pay stubs from a borrower', and Jentic returns POST `/borrowers/{borrower_id}/form-requests` with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Plaid API** — Plaid provides bank-account verification and asset reports that mortgage originators attach to a loan application. - **Experian API** — Experian provides credit-bureau data that supplements credit reports stored against a SimpleNexus borrower record. - **Salesforce REST API** — Many mortgage teams sync borrower and application data into Salesforce for reporting and lifecycle management. ## FAQ ### What authentication does the SimpleNexus API use? SNAPI uses HTTP bearer-token authentication (security scheme `bearerAuth`). Tokens are issued per integration and scoped to a SimpleNexus tenant. Through Jentic, the bearer token is stored encrypted in the vault and supplied at execution time - agents never see the raw token. ### Can I create a borrower and pull their credit report through this API? Yes. Call POST /borrowers with the applicant payload to create the record, then GET `/borrowers/{borrower_id}/credit-reports` to retrieve credit reports already on file. New credit pulls are typically initiated by the loan-application flow rather than directly through SNAPI. ### What are the rate limits for the SimpleNexus API? Public rate limits are not declared in the OpenAPI spec. Refer to the developer portal at developer.ncinomortgage.com for current quotas; SNAPI typically applies per-token throttles for write-heavy workloads. ### How do I subscribe to loan status webhooks through Jentic? Search Jentic for 'create simplenexus webhook subscription', load the schema for the webhook endpoints under the `Webhooks` tag, and execute with the target callback URL. Webhook delivery includes loan, application, and document events. ### Can I send borrower notifications programmatically? Yes. POST `/borrowers/{borrower_id}/notify` triggers an in-app or email notification to the borrower. Combine with POST `/borrowers/{borrower_id}/form-requests` to request specific documents. ### Can I limit what my agent is allowed to do with the SimpleNexus API? Yes. Because you self-host Jentic One, your own rules decide which SimpleNexus operations and credentials the agent may use. Since the borrower id sits in the URL path (`/borrowers/{borrower_id}/...`), you can pin the agent to a single borrower and let it read that borrower's credit reports and request forms while leaving out creating borrowers or sending notifications. Only the operations you grant are callable, and the bearer token is injected at execution time so the agent never sees it.