Bridge Brightland Mortgage borrower data into your CRM, LOS, or analytics stack
Brightland Mortgage runs on the SimpleNexus point-of-sale platform (now part of nCino's mortgage suite). We help builders, brokerages, and servicers extract loan application milestones, document statuses, and borrower contact data from the mobile flow, then surface that data wherever it is actually used — Salesforce, Velocify, Encompass, or a custom analytics warehouse.
What we deliver
Each engagement ships as a working code drop the lender's IT team can pick up immediately, plus the documentation needed to defend the integration in a vendor or compliance review. We do not just hand over a Postman collection; we hand over a tested service that an analyst can operate.
Deliverables checklist
- OpenAPI 3.1 specification covering login, loan list, loan detail, document, and webhook endpoints
- Protocol and authentication report (OAuth client-credential flow, tenant scoping, signed webhook payload validation)
- Runnable reference service in Python (FastAPI) and Node.js (Express) with retry, idempotency, and rate-limit handling
- End-to-end Postman collection plus pytest / Jest test suites against a sandbox tenant
- Compliance dossier — GLBA Safeguards mapping, GLBA opt-out language, FTC MFA/encryption controls, audit-log schema, retention recommendations
- Operational runbook for on-call: error codes, replay strategy, dead-letter queue handling, secret rotation
Two engagement models
Source-code delivery from $300 — we hand over runnable API source plus full documentation; you only pay after delivery if you are satisfied with the working code. Suitable for in-house teams that want to own and extend the integration.
Pay-per-call hosted API — call our managed endpoints with no upfront fee; usage is metered per request. Suitable for brokerages, builders, or fintechs that prefer predictable opex over hiring a backend engineer.
Data available for integration
The following inventory reflects what Brightland Mortgage's borrower-facing flow exposes through SimpleNexus/nCino partner APIs and what most lenders are willing to syndicate to authorized partners. Granularities and field names follow the SNAPI v0 schema and the newer nCino Mortgage API where it is in general availability.
Typical integration scenarios
1. Builder pipeline sync
A regional homebuilder lists Brightland Mortgage as the preferred lender for new-construction buyers. Sales consultants need to see a buyer's loan progress from the builder CRM without logging into a separate portal.
Data & APIs: GET /api/v1/loans for the consultant's assigned borrowers, GET /api/v1/loans/{id}/milestones for status events, plus a webhook on loan.status_changed that posts to the builder's CRM webhook endpoint.
OpenFinance mapping: the milestone stream becomes a normalized loan-lifecycle resource that the builder's BI tool can join with sales-contract dates to compute "days from contract to clear-to-close" by community.
2. Document conditions automation
An operations team wants to chase missing borrower conditions automatically rather than have processors send manual emails.
Data & APIs: GET /api/v1/loans/{id}/documents returns each open condition; webhook on document.requested fires a templated SMS/email; webhook on document.accepted closes the loop in the LOS.
OpenFinance mapping: the condition state machine is exposed as a public resource that borrower-side aggregators (e.g. budgeting apps) can read with explicit consent to surface "you owe Brightland 2 documents" reminders.
3. Realtor co-marketing portal
A real-estate brokerage runs a co-branded portal that shows realtors which of their buyers are pre-qualified, in underwriting, or clear-to-close.
Data & APIs: contact-graph API to scope visibility, milestone API for status, and a redacted version of the 1003 (pre-qualification amount only) for the portal's pipeline tile.
OpenFinance mapping: follows the same consent pattern as US open-banking aggregators — the borrower authorizes a downstream party (the realtor) to see specific fields, not the full file.
4. LOS hand-off and round-trip sync
An origination team wants a borrower's mobile-submitted application to appear in Encompass or Empower without re-keying, and any LOS-side milestone changes to flow back to the borrower's app within seconds.
Data & APIs: SNAPI loan-create plus document-attach for hand-off; the new nCino Mortgage API or partner LOS connector pushes status back. Webhook-driven so the round trip stays under a minute.
OpenFinance mapping: equivalent to the dual-rail message bus seen in PSD2 implementations — one rail for application data, one rail for status/event signals — keeping the borrower app and the system of record consistent.
5. Compliance & audit warehouse
A compliance officer needs an immutable record of every disclosure delivery, e-sign event, and document acceptance for TRID and state regulator audits.
Data & APIs: webhook fan-out to an append-only S3 + Athena warehouse, with hashes signed using the lender's tenant key. Daily reconciliation against GET /api/v1/loans?modified_since=… guarantees no events are missed.
OpenFinance mapping: mirrors the FCA's requirement for regulated firms to produce a verifiable activity log on demand; the same warehouse can serve CFPB and state DFI examinations.
Technical implementation
The reference stack we ship targets the SimpleNexus API (SNAPI v0) for legacy tenants and the new nCino Mortgage API for tenants on the rebranded platform. All examples are simplified for readability; production code includes retries, exponential backoff, and idempotency keys.
Auth — OAuth client credentials
POST /oauth2/token HTTP/1.1
Host: api.simplenexus.com
Content-Type: application/x-www-form-urlencoded
grant_type=client_credentials
&client_id=BRIGHTLAND_TENANT_ID
&client_secret=***
&scope=loans.read documents.read webhooks.manage
200 OK
{
"access_token": "eyJhbGciOi...",
"token_type": "Bearer",
"expires_in": 3600,
"scope": "loans.read documents.read webhooks.manage"
}
Loan status — list & detail
GET /api/v1/loans?modified_since=2026-05-01T00:00:00Z
Authorization: Bearer <ACCESS_TOKEN>
200 OK
{
"page": 1, "page_size": 50, "total": 187,
"data": [
{
"loan_id": "ln_8f3...",
"borrower": {"id":"b_91a...","name":"J. Doe"},
"milestone": "UNDERWRITING",
"milestone_at": "2026-05-09T14:22:11Z",
"loan_originator_id": "lo_12...",
"builder_id": "bld_77...",
"amount": 412000,
"rate_locked": true
}
]
}
Webhook — loan.status_changed
POST /your/webhook/endpoint HTTP/1.1
X-SN-Signature: t=1715300000,v1=8c3f...
Content-Type: application/json
{
"event": "loan.status_changed",
"occurred_at": "2026-05-10T09:11:02Z",
"loan_id": "ln_8f3...",
"from": "PROCESSING",
"to": "CLEAR_TO_CLOSE",
"tenant_id": "brightland"
}
# verify HMAC-SHA256 of (timestamp + "." + body)
# using the tenant webhook secret before processing
Document upload mirror
POST /api/v1/loans/ln_8f3.../documents
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: multipart/form-data
category=INCOME_W2
filename=w2_2025.pdf
file=<binary>
201 Created
{
"document_id": "doc_44c...",
"state": "RECEIVED",
"sha256": "f4e0...",
"received_at": "2026-05-10T09:13:48Z"
}
Compliance & privacy
Regulatory frame
Mortgage data in the United States is governed by overlapping rules. The Gramm-Leach-Bliley Act (GLBA) privacy notice rule requires opt-out language whenever non-public personal information moves to a non-affiliate. The FTC Safeguards Rule (revised December 2021, fully in force from 2023) requires multi-factor authentication, encryption of customer information in transit and at rest, and continuous logging of access to consumer data — every endpoint we ship complies by default.
TRID timing rules and the CFPB's 2024–2025 reports on financial-data privacy further constrain how disclosure events and 1003 fields are stored and shared. State laws (Montana SB 297, Connecticut SB 1295, both in 2025) have started to remove the broad GLBA exemption, so production deployments must be ready to honor state-specific consumer rights such as deletion and data-access requests.
Controls we implement
- OAuth 2.0 client-credentials with rotated secrets and tenant-scoped tokens
- HMAC-signed webhook payloads with replay window
- TLS 1.2+ everywhere; AES-256 at rest for any stored documents
- Audit log of every API call (caller, scope, target loan, timestamp)
- Role-based redaction (e.g. realtor only sees pre-qualification status, not full 1003)
- Configurable retention and deletion to support state privacy-law requests
- Authorized or documented APIs only — we do not bypass authentication or scrape unauthorized endpoints
Data flow / architecture
A typical Brightland Mortgage integration follows a four-node pipeline:
- Mobile app (Brightland Mortgage) — borrower submits 1003 fields, scans documents, receives push status updates.
- SimpleNexus / nCino Mortgage API — the tenant's authoritative source for loan, document, and event data; emits webhooks on state changes.
- OpenFinance Lab integration layer — token management, payload validation, retry & dead-letter queue, schema normalization, audit logging, role-based redaction.
- Downstream systems — LOS (Encompass, Empower), CRM (Salesforce, HubSpot, Velocify), data warehouse (Snowflake, BigQuery), or a compliance archive (S3 + Athena).
The same backbone supports both batch reconciliation (paged modified_since queries) and real-time push (signed webhooks), so reporting accuracy and operational speed do not have to fight each other.
Market positioning & user profile
Brightland Mortgage is the captive mortgage app for Brightland Homes, a US homebuilder, white-labeled on the SimpleNexus / nCino mortgage point-of-sale platform — the same engine behind hundreds of US lenders. Primary users fall into four segments: prospective buyers of new-construction homes, current homeowners exploring refinancing, in-house loan originators handling the file, and the builder's sales consultants and partner realtors who need pipeline visibility. Distribution is mobile-first across Android and iOS in the United States, with most volume concentrated in Texas and the Gulf-Coast / Sun-Belt markets where Brightland builds. Integration buyers therefore tend to be the builder's IT team, marketing-operations leads who run co-marketing with realtors, and compliance officers preparing for CFPB or state-DFI examinations.
Screenshots
Click any thumbnail to view it full size. Screenshots are sourced from the Google Play Store listing for context only.
Similar apps & integration landscape
Brightland Mortgage sits inside a broader US mortgage and homebuying ecosystem. Lenders, builders, and brokerages routinely need to combine borrower data from Brightland with the apps below; we frame these as adjacent integration targets, not competitors. ICE Mortgage Technology has set a December 2026 deadline to migrate Encompass customers from SDK-based customizations to API-first Developer Connect/Partner Connect flows, which is accelerating cross-app data work across this list.
Rocket Mortgage
The largest US mortgage lender by volume in 2025. Holds full digital application data, milestone events, and rate-lock history; teams that work with both Rocket and Brightland often need a unified pipeline view across the two systems.
Better Mortgage
Direct-to-consumer digital lender with a fully online flow. Data of interest includes pre-approval letters, locked rates, and document checklists — useful when borrowers shop multiple lenders before settling on the builder-preferred option.
Chase Mortgage
Bank-of-record mortgage app paired with Chase deposit accounts. Combining Chase verification-of-deposit data with the Brightland 1003 reduces document chase and tightens income/asset reconciliation.
SoFi Home Loans
App-led lender with strong member overlap with first-time buyers. Integration interest typically focuses on rate quotes and pre-qualification status alignment for buyers comparing offers.
LendingTree
Marketplace that fans a single application across 500+ partners. Lenders ingest LendingTree leads and need to mirror them into the Brightland POS without re-keying — a classic Brightland-API plus LendingTree-webhook joint flow.
Flagstar Bank Mobile
Lender with first-time-buyer programs (Power-Up grants). Operationally similar to Brightland in document-collection and milestone semantics, so the same integration patterns apply.
Bankrate
Rate-comparison platform with live quotes from 100+ lenders. Often used upstream of a Brightland application; UTM and quote-ID hand-off is the typical integration shape.
Tomo Mortgage
Digital lender focused on purchase (rather than refi) loans, like Brightland. Schema overlaps heavily on milestone and conditions taxonomy, so a normalized integration layer can read both with little branch logic.
MeridianLink Mortgage
LOS used by community lenders with an open-API ecosystem connecting hundreds of partners. A common downstream target when Brightland data needs to land in a credit-union or community-bank system of record.
ICE Encompass
Industry-leading LOS migrating to API-first Developer/Partner Connect by December 2026. Brightland-to-Encompass round-trip sync is one of the most-requested integration jobs we see today.
About OpenFinance Lab
We are an independent technical studio specializing in mobile-app protocol analysis and authorized API integration. Our engineers come from US fintech, mortgage technology, and cloud-platform backgrounds, and we have shipped production integrations against SimpleNexus/nCino, Encompass, MeridianLink, and direct-lender stacks.
- Mortgage origination, servicing, and post-close automation
- Builder and brokerage co-marketing data feeds
- Custom Python / Node.js / Go SDKs and webhook routers
- Compliance reviews against GLBA, FTC Safeguards, and state privacy laws
- Source-code delivery from $300 — runnable code plus full docs; pay only after you are satisfied
- Pay-per-call hosted API — usage-priced, no upfront fee, ideal for opex budgets
Contact
To request a quote or to submit a target app and integration scope, open our contact page:
Engagement workflow
- Scope confirmation: which loan events, document categories, and downstream systems are in play.
- Protocol analysis and API design (2–5 business days, complexity-dependent).
- Build and internal validation against a sandbox tenant (3–8 business days).
- Documentation, sample requests, and test cases (1–2 business days).
- Hand-off, smoke test in your environment, and a 30-day support window.
FAQ
Do I need lender-side credentials to integrate Brightland Mortgage?
What loan data can typically be pulled out via the API?
How long does delivery take and what is the price model?
How do you handle GLBA, CFPB, and FTC Safeguards compliance?
📱 Original app overview (appendix)
The Brightland Mortgage tool helps provide exemplary service to home builders, realtors, and their customers. Brightland Mortgage simplifies the home buying and lending process with a mobile app when making a loan application, loading documents, and receiving status updates. Whether you are a homebuyer looking to purchase a home, a current homeowner interested in refinancing, or a home builder or real estate agent hoping to speed up the process for clients, Brightland Mortgage has a feature to benefit you.
Key features (from the original Google Play description):
- Easy loan qualification process from your phone, tablet, or computer.
- Loan calculator tools for comparing lending scenarios and payment options.
- Instant access to contact information for your loan originator, sales consultant, or realtor.
- Document scan and upload feature to speed up the lending process.
- Centralized communication tool and real-time updates on loan status.
By working with one of the lender's mortgage professionals and using the Brightland Mortgage tool, the lending process is presented as a streamlined, mobile-first experience for borrowers and partners alike.
Platform note: the package id com.simplenexus.loans.client.s__35225 indicates the app is a tenant build of the SimpleNexus client-loans platform (now part of nCino's mortgage suite), the same stack used by hundreds of US lenders.