--- title: LendingWise API Integration on Truto slug: lendingwise category: CRM canonical: "https://truto.one/integrations/detail/lendingwise/" --- # LendingWise API Integration on Truto **Category:** CRM **Status:** Generally available ## MCP-ready AI tools Truto exposes 32 tools for LendingWise that AI agents can call directly. - **list_all_lending_wise_loans** — List Lendingwise loan-file summaries with optional filters by broker, borrower, or loan officer. Returns: id, branchID, loanBrokerID, loanOfficerID, borrowerId, borrowerName, borrowerEmail, loanNumber, primaryStatusId, activeStatus, createdAt. Max 100 per page (default 25). - **create_a_lending_wise_loan** — Create a new Lendingwise loan file with borrower, branch, loan type, program, and pipeline status. Returns the created loan including id, branchID, borrowerId, loanNumber, primaryStatusId, and createdAt. Required: branchID, fileType, loanProgram, primaryStatusId, borrower. - **get_single_lending_wise_loan_by_id** — Get a single Lendingwise loan file by its numeric id (LMRId). Returns: id, branchID, loanBrokerID, loanOfficerID, borrowerId, borrowerName, borrowerEmail, loanNumber, primaryStatusId, activeStatus, createdAt. Required: id. - **update_a_lending_wise_loan_by_id** — Update an existing Lendingwise loan file by id with a merge-patch — every field is optional, so send only the fields you want to change; move the pipeline status with primaryStatusId. Returns the updated loan including id, branchID, loanNumber, primaryStatusId, borrowerName, borrowerEmail, and createdAt. Required: id. - **lending_wise_loans_add_properties** — Add subject/collateral properties to a LendingWise loan file via POST. Returns the list of created property objects including propertyId and isPrimary. Required: loan_id. Multi-property supported; mark exactly one property as isPrimary — the primary property's address also mirrors onto the loan. - **lending_wise_loans_add_members** — Add members to a Lendingwise loan file. Returns an array of created member records, each including memberId (the id needed to later change or remove the member). Required: loan_id, entity. - **lending_wise_loans_delete_member** — Remove a member from a LendingWise loan file by member id. Returns the updated loan file including its id, entity (with remaining members), primaryStatusId, loanNumber, and borrowerName. Required: loan_id, member_id. - **lending_wise_loans_get_branch** — Get the branch assigned to a loan file in Lendingwise. Returns the branch object on the loan file, or null when no branch is set. Required: loan_id. - **lending_wise_loans_assign_branch** — Assign a branch to a loan file in LendingWise. Returns the branch now on this loan file, including its id. Required: loan_id, branchId. - **lending_wise_loans_get_broker** — Get the broker assigned to a Lendingwise loan file. Returns the broker's full profile including id, email, firstName, lastName, company, phone, phoneTollFree, and preferredCommunication, or null when no broker is set. Required: loan_id. - **lending_wise_loans_assign_broker** — Assign a broker to a LendingWise loan file by providing the broker's numeric id. Returns the broker now on the loan file including id, firstName, lastName, and email. Required: loan_id, brokerId. - **lending_wise_loans_unassign_broker** — Remove the broker from a LendingWise loan file. Returns the broker that was taken off the loan file including id, firstName, lastName, and email. Required: loan_id. - **lending_wise_loans_get_loan_officer** — Get the loan officer assigned to a Lendingwise loan file. Returns the loan officer's profile including id and additional attributes, or null when no officer is set. Required: loan_id. - **lending_wise_loans_assign_loan_officer** — Assign a loan officer to a Lendingwise loan file. Returns the loan officer now on the file, including its id. Required: loan_id, loanOfficerId. - **lending_wise_loans_unassign_loan_officer** — Remove the loan officer from a Lendingwise loan file. Returns the loan officer that was taken off the file, including its id. Required: loan_id. - **lending_wise_loans_list_employees** — List the back-office employees assigned to a LendingWise loan file. Returns each employee record with its id. Required: loan_id. - **lending_wise_loans_replace_employees** — Replace the complete list of back-office employees on a LendingWise loan file. Returns each employee record now on the file with its id. Required: loan_id, employeeIds. Send an empty array to remove all employees; any invalid id rejects the entire request. - **delete_a_lending_wise_loan_by_id** — Archive a LendingWise loan file by its numeric id (LMRId). Returns: id. Required: id. - **list_all_lending_wise_loan_types** — List loan types configured for your company in Lendingwise. Returns: id, branchID, loanBrokerID, loanOfficerID, borrowerId, borrowerName, borrowerEmail, loanNumber, primaryStatusId, activeStatus, createdAt, moduleCode. The list can be empty. - **list_all_lending_wise_loan_programs** — List Lendingwise borrower-facing loan programs configured for your company. Returns: id, STCode. The list can be empty. - **lending_wise_loan_programs_list_internal** — List your company's internal loan programs in Lendingwise. Returns the company's internal lending programs, each identified by an STCode value used when setting a loan's `loanProgram` field during create or update. The list can be empty. No required parameters. - **list_all_lending_wise_loan_primary_statuses** — List your company's top-level loan primary statuses in Lendingwise. Returns: id. The list can be empty; pass includeInactive to also return switched-off statuses, or fileType to narrow to statuses set up for a single loan type. - **list_all_lending_wise_loan_sub_statuses** — List your company's loan sub-statuses in Lendingwise, optionally narrowed by category or loan type. Returns: id, categoryId, fileType. The list can be empty. - **list_all_lending_wise_brokers** — List LendingWise brokers for your processing company. Returns each broker with id, email, firstName, lastName, company, phone, phoneTollFree, and preferredCommunication. Set includeInactive to true to include deactivated or archived records. - **get_single_lending_wise_broker_by_id** — Get a single LendingWise broker by its numeric id. Returns the broker's full profile including id, email, firstName, lastName, company, phone, phoneTollFree, and preferredCommunication. Required: id. - **lending_wise_brokers_create_or_update** — Create or update a LendingWise broker, matched by email address. Returns the broker record including id, email, firstName, lastName, company, phone, and phoneTollFree. Required: email. phoneNumber writes the toll-free number and cellNumber writes the main contact number. - **list_all_lending_wise_loan_officers** — List loan officers in Lendingwise. Returns: id. Active records are returned by default; set includeInactive to true to also retrieve deactivated or archived records. An empty list is returned when you have none. - **get_single_lending_wise_loan_officer_by_id** — Get a Lendingwise loan officer by numeric id, returning the officer's full profile. Returns: id, attributes. Required: id. - **list_all_lending_wise_branches** — List LendingWise branches for your company. Returns: id. Set includeInactive to true to also retrieve deactivated or archived branches. - **get_single_lending_wise_branch_by_id** — Get a single Lendingwise branch by its numeric id — the same id the list branches endpoint returns. Returns: id. Required: id. - **list_all_lending_wise_back_office_employees** — List back-office employees in LendingWise. Returns: id. Pass includeInactive=true to also retrieve deactivated or archived records; omit it for active records only. - **get_single_lending_wise_back_office_employee_by_id** — Get a single back-office employee by its numeric id in LendingWise. Returns the employee's full profile including id. Required: id. ## How it works 1. **Link your customer's LendingWise account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach LendingWise.** The Proxy API is a 1-to-1 mapping of the LendingWise API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Push borrower applications from your POS into LendingWise** — If you run a point-of-sale or intake platform for real estate investors and brokers, offering a LendingWise integration lets your customers auto-create loan files, attach borrowing entities, and push collateral properties without any manual re-keying. - **Automate commission calculations for brokerages** — Commission and payroll platforms serving mortgage and CRE brokerages can poll funded loans in LendingWise and pull the assigned loan officer, broker, and branch to calculate volume-based payouts automatically. - **Generate closing documents from live loan data** — Document generation and legal tech platforms can pull loan, borrower, and property data straight from LendingWise to draft term sheets and closing packages, then flip the loan's primary status once documents are sent. - **Trigger marketing and nurture campaigns on pipeline changes** — Marketing automation platforms serving lenders can watch loan sub-status changes in LendingWise and trigger targeted SMS or email drips, pulling the assigned loan officer to personalize outreach on their behalf. - **Enrich loan files with third-party valuation and risk data** — Property valuation, credit, and background check providers can read subject property details from a LendingWise loan file, run their own analysis, and write enriched data back so underwriters see everything in one place. ## What you can build - **One-click loan file creation from your app** — Let end users create a LendingWise loan directly from your UI, pre-mapped to their lender's active loan programs, loan types, and branches fetched at runtime. - **Borrower and entity sync** — Attach individual borrowers and corporate entities like LLCs to a loan file using the add members endpoint, ideal for CRE and hard money workflows. - **Collateral and subject property push** — Send one or more subject properties into a loan file and flag the primary collateral so it mirrors to the main loan address automatically. - **Loan team assignment automation** — Programmatically assign or reassign brokers, loan officers, branches, and back-office employees on a loan file when your app's workflows trigger. - **Pipeline status webhooks and progression** — Move loans between primary and sub-statuses via merge-patch updates when external tasks like document generation, valuation, or underwriting checks complete. - **Funded-loan pipeline reporting** — List and filter loans by primary status to feed BI dashboards, commission engines, or accounting systems with closed and funded volume. ## FAQs ### How does authentication with LendingWise work through Truto? Truto handles the LendingWise auth flow and credential storage for you. Your end users connect their own LendingWise account through Truto's connection UI or headless flow, and your app makes API calls scoped to that account without you managing tokens directly. ### Which LendingWise resources can I read and write today? The integration supports loans (list, get, create, update, delete), loan members, properties, branches, brokers, loan officers, and back-office employees. You can also list loan types, loan programs (including internal), primary statuses, and sub-statuses to map your app's taxonomy to each lender's setup. ### Can I update a loan's pipeline status from my application? Yes. You can call the update loan endpoint with a merge-patch to change fields like primaryStatusId or subStatusId, which is the standard pattern for moving loans between stages such as Processing, Underwriting, or Docs Sent. ### How do I handle lender-specific loan programs and statuses? Every lender configures LendingWise differently. Before creating or updating loans, fetch the tenant's live list of loan programs, loan types, primary statuses, and sub-statuses via the list endpoints and map them in your UI so users select values that exist in their account. ### Is there a unified CRM API I can use to write once and sync to LendingWise? Not yet for this connector. LendingWise is currently exposed via its native tool surface in Truto, so you'll work with LendingWise-specific endpoints. If a unified CRM schema is important for your roadmap, it can be prioritized on request. ### How do I keep data fresh — are webhooks or polling supported? You can poll list endpoints like list_all_lending_wise_loans on a schedule to detect changes such as status transitions or new files. If native LendingWise webhook support is required for your use case, reach out and it can be scoped as part of the integration. ## Related reading - [Connect LendingWise to ChatGPT: Manage Loans, Properties and Members](https://truto.one/blog/connect-lendingwise-to-chatgpt-manage-loans-properties-and-members/) — A complete engineering guide to generating a managed MCP server for LendingWise, connecting it to ChatGPT, and automating loan file management using AI agents. - [Connect LendingWise to Claude: Track Pipeline Status and Loan Files](https://truto.one/blog/connect-lendingwise-to-claude-track-pipeline-status-and-loan-files/) — Learn how to connect LendingWise to Claude using Truto's managed MCP server. Automate loan origination, pipeline tracking, and broker assignments via AI. - [Connect LendingWise to AI Agents: Orchestrate Brokers and Staffing](https://truto.one/blog/connect-lendingwise-to-ai-agents-orchestrate-brokers-and-staffing/) — Learn how to connect LendingWise to AI agents using Truto's unified tools API. Build autonomous workflows for loan origination, broker assignments, and staffing.