---
title: LoanPro API Integration on Truto
slug: loanpro
category: Accounting
canonical: "https://truto.one/integrations/detail/loanpro/"
---

# LoanPro API Integration on Truto



**Category:** Accounting  
**Status:** Beta

## Unified APIs

### Unified User Directory API

- **Users** — The User object represents a User.

## MCP-ready AI tools

Truto exposes 2 tools for LoanPro that AI agents can call directly.

- **list_all_loanpro_users** — Search users in LoanPro by query filters. Returns fields including id, firstName, lastName, fullName, userName, tenantAccessRoleDescription, tenantActiveStatus, active, jobTitle, isEnrolledInMFA, wizardGroup, searchRestrictionGroup, tenantAccessRole, phone, globalRole, and summary with totalHits and totalTime.
- **get_single_loanpro_user_by_id** — Get a specific agent user profile in LoanPro using id. Returns key fields such as id, firstName, lastName, userName, recoveryEmail, phone, jobTitle, active, gender, roleId, tenantRole, tenantAccessActive, validated, lastContractSigned, and isEnrolledInMFA.

## How it works

1. **Link your customer's LoanPro 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 LoanPro.** The Proxy API is a 1-to-1 mapping of the LoanPro 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

- **Route support tickets to the right loan servicing agent** — A helpdesk SaaS can sync all LoanPro servicing agents and their roles, then automatically route borrower inquiries to the agent responsible for that loan portfolio — eliminating manual ticket assignment and reducing resolution times.
- **Build a unified agent directory across lending platforms** — A workforce management or internal ops SaaS can pull all LoanPro users alongside agents from other platforms into a single directory, giving operations leaders a consolidated view of who has access to what across their lending stack.
- **Enforce access controls and audit agent permissions** — A compliance or GRC SaaS can continuously sync LoanPro user roles and permissions to detect over-provisioned accounts, flag unauthorized access patterns, and generate audit-ready reports for regulatory examinations.
- **Automate onboarding and offboarding of loan servicing staff** — An identity management or HR SaaS can read the current state of LoanPro users to identify stale accounts, reconcile them against HR systems, and ensure departing employees are flagged for deprovisioning promptly.

## What you can build

- **LoanPro agent roster sync** — Automatically import and keep up to date a complete list of all LoanPro users, including their names, job titles, and roles, into your application's internal directory.
- **Role-based ticket routing** — Use each agent's tenant access role and group assignments from LoanPro to intelligently route incoming borrower support requests to the correct servicing team.
- **Agent permission audit dashboard** — Surface a real-time view of every LoanPro user's global and tenant-level roles so compliance teams can quickly spot permission drift or over-provisioned accounts.
- **Cross-platform user directory** — Combine LoanPro users with users from other connected platforms via Truto's Unified User Directory API to give ops teams a single pane of glass across all their tools.
- **Stale account detection alerts** — Periodically list all LoanPro users, cross-reference against your HR or identity provider, and trigger alerts when accounts exist for employees who have left the organization.

## FAQs

### What operations does Truto support for LoanPro today?

Truto currently supports listing all LoanPro users and retrieving a single user by ID. These are exposed through the Unified User Directory API, so you can use the same schema and calling convention you use for other integrations.

### What user data fields are available from LoanPro through Truto?

Key fields include id, firstName, jobTitle, tenantAccessRole, globalRole, and group assignments (e.g., wizardGroup). These map onto Truto's unified user schema for consistent cross-platform consumption.

### How does authentication work for the LoanPro integration?

LoanPro uses API key-based authentication. Your end users provide their LoanPro API credentials through Truto's managed auth flow, and Truto securely stores and refreshes them — you never handle raw keys directly.

### Does Truto handle pagination for LoanPro's user endpoints?

Yes. Truto abstracts away LoanPro's pagination logic. When you call list_all_loanpro_users, Truto handles cursor or offset management behind the scenes and returns a consistent paginated response.

### Can I write data back to LoanPro through Truto?

The currently available tools are read-only — listing users and fetching a user by ID. If you need write operations or additional endpoints, Truto can build custom integrations on request to cover your specific workflow.

### How does the Unified User Directory API help if I integrate multiple loan management systems?

Truto's unified schema normalizes user records across all connected platforms. This means your application code works identically whether the data comes from LoanPro or another system — no provider-specific parsing or mapping required.
