LPL Financial
LPL Financial is a data sync integration that allows advisors to import client households, accounts, and holdings from the LPL ClientWorks platform into RightCapital.
Overview
Section titled “Overview”| Attribute | Value |
|---|---|
| Integration Type | Data Sync (Read-only) |
| Authentication | OAuth 2.0 (Password Grant) |
| Data Flow | LPL ClientWorks → RightCapital (inbound) |
| Data Sync | Manual per-household + Nightly file-based sync |
| Identifier | Client ID (household), Account ID (account) |
| Developer | Qianwei Hao |
Data Structure
Section titled “Data Structure”Entity Mapping
Section titled “Entity Mapping”| LPL Entity | RightCapital Entity | Identifier |
|---|---|---|
| Client | Household | clientID |
| Account | Investment Account | accountID |
| Holding | Position | CUSIP / Symbol |
Key Points
Section titled “Key Points”- Per-household sync - LPL does not support batch sync; each household must be synced individually
- Dual sync modes - API-based for initial import; file-based for nightly updates
- CUSIP-based matching - Holdings are matched primarily by CUSIP
- Closed accounts filtered - Accounts with status “Closed” are excluded
API Endpoints
Section titled “API Endpoints”| Purpose | LPL API Path |
|---|---|
| Get Access Token | esb/lpl/resource/getaccesstoken |
| Search Clients | oauth/clientinfoservice/api/search |
| Get Accounts | oauth/accountinfoservice/api/search |
| Get Holdings | oauth/investmentservice/api/searchinvestments |
| User Onboarding | oauth/lplapi/cwpage/geturl |
Account Type Mapping
Section titled “Account Type Mapping”| LPL Account Type | RightCapital Subtype |
|---|---|
| Q - Personal Trust | Trust |
| T - Non-Profit Organization | Donor Advised Fund |
| S, Y, I, Z - Retirement Plans | Traditional IRA |
| B, U, J, A, E, K (various individual/joint) | Taxable |
| Variable Annuity | Annuity (Taxable) |
Code Locations
Section titled “Code Locations”| Component | Path |
|---|---|
| Backend Integration | retail-api/app/Integrations/Lpl/ |
| Connector (OAuth) | Connector.php |
| Integrator | Integrator.php |
| Config | Config.php |
| Controller | Controller.php |
| Sync | Sync.php |
| Models | Models/Household.php, Models/InvestmentAccount.php, Models/Holding.php |
Common Issues
Section titled “Common Issues”User Onboarding Not Complete
Section titled “User Onboarding Not Complete”Symptom: Integration shows as connected but no data can be retrieved.
Solution: Have advisor re-initiate the connection and complete the ClientWorks authorization.
No Accounts Found
Section titled “No Accounts Found”Symptom: Client is found but no accounts appear.
Cause: All accounts may be closed or have excluded location IDs.
Related
Section titled “Related”- Albridge - Similar custodian integration