Capitect
Capitect is a data aggregation integration that syncs portfolio data from the Capitect API into RightCapital. It imports client households, accounts, and holdings for financial planning.
Overview
Section titled “Overview”| Attribute | Value |
|---|---|
| Integration Type | Data Sync (Import) |
| Authentication | OAuth 2.0 (Password Grant) |
| Data Flow | Capitect → RightCapital (inbound) |
| Data Sync | On-demand sync |
| Entity Model | Household with Children (Accounts, Holdings) |
Entity Model
Section titled “Entity Model”Capitect uses capid as the unique identifier for all entities:
| Entity | Identifier | Example |
|---|---|---|
| Client (Household) | capid | cli01abc123 |
| Account | capid | acc01bTWbRHUce3 |
| Holding | capid | Security reference |
Holding Types
Section titled “Holding Types”| Capitect Type | RightCapital Type |
|---|---|
bond | Bond |
cd | CD |
closedendfund | Closed-End Fund |
exchangetradedfund | ETF |
limitedpartnership | Equity |
moneymarketfund | Money Market Fund |
mutualfund | Open-End Fund |
option | Option |
preferredstock | Equity |
stock | Equity |
unitinvestmenttrust | UIT |
unittrust | Open-End Fund |
Type normalization: Capitect types are normalized by removing spaces, underscores, and hyphens, then lowercasing.
API Endpoints
Section titled “API Endpoints”| Purpose | Endpoint | Method |
|---|---|---|
| Get Access Token | /v1/tokens | POST |
| List Clients | /v1/clients | GET |
| Get Client Accounts | /v1/clients/{capid}/accounts | GET |
Code Locations
Section titled “Code Locations”| Component | Path |
|---|---|
| Backend Integration | retail-api/app/Integrations/Capitect/ |
| Connector (OAuth2) | Connector.php |
| Integrator | Integrator.php |
| Config | Config.php |
| Models | Models/Account.php, Models/InvestmentAccount.php, Models/BankAccount.php, Models/LoanAccount.php, Models/Holding.php, Models/Household.php |
| OAuth2 Provider | OAuth2/Provider.php |
Authentication Flow
Section titled “Authentication Flow”Capitect uses OAuth 2.0 Password Grant:
- Advisor provides username and password
- RightCapital exchanges credentials for access token via
/v1/tokens - Uses HTTP Basic Auth with client_id/secret for token endpoint
- Access token used as Bearer token for API calls
Common Issues
Section titled “Common Issues”Client Not Found (404)
Section titled “Client Not Found (404)”Symptom: NotFoundException when syncing accounts
Solution: Remove the client mapping in RightCapital and re-link if needed.
Invalid API Key
Section titled “Invalid API Key”Symptom: “User does not have an active API key” error
Solution: Verify API key status in Capitect and re-authenticate.
Account Type Not Mapped
Section titled “Account Type Not Mapped”Symptom: Account syncs but with wrong subtype.
Solution: Review logs for the specific type and add mapping if needed.
Related
Section titled “Related”- BridgeFT - Similar data aggregation integration