RealtyTitleAgent ONE API integration & data services

1 · Authentication & profile bridge

Mirrors the app's authorization flow (token issuance, refresh, session validation) and exposes the agent / title-office branding profile — logo, license number, contact block, preferred underwriter. Use it to bind a brokerage user to their PalmAgent identity once and reuse it across every later call.

2 · Seller net sheet endpoint

Given a property address (or state/county + sale price), a payoff figure and commission terms, returns the full seller net sheet: title insurance premium, escrow/settlement fee, recording fees, transfer taxes, prorated taxes, HOA proration, seller credits and net proceeds. Drives listing presentations and pre-CD reconciliation.

3 · Buyer estimate & cash-to-close endpoint

Returns purchase price, loan amount, down payment, lender fees, owner's/lender's title premium, prepaids and reserves, monthly PITI and total cash to close. Feeds a "what will I need at closing" widget on an agent site or a loan officer's pre-qual screen.

4 · Rate & fee reference service

Read-only access to the preloaded jurisdiction tables — title premium bands, simultaneous-issue logic, endorsement pricing, county recording fees, deed/mortgage transfer taxes. Versioned by effective date so a quoting engine can show "rates as of …" and survive a state filing change.

5 · Scenario, buydown & HomeLink module

Runs multi-loan Smart Compare scenarios, 2-1/3-2-1 buydown math (with HOA included), buyer agent compensation under the 2024 NAR settlement format, and HomeLink-style monthly holding-cost projections derived from public-record inputs. Returns each scenario as a structured object for side-by-side rendering.

6 · Saved estimates, exports & webhooks

Lists an agent's saved estimates, fetches any one as JSON/Excel/PDF, and fires a webhook on create/update so a transaction-management system (SkySlope, dotloop, Lone Wolf, etc.) attaches the net sheet to the matching file automatically.

A · Brokerage CRM auto-fills net sheets

Context: a brokerage wants every new listing to carry a seller net sheet without agents re-typing numbers. Data/API: POST /v1/realtytitleagent/seller-net-sheet with property, payoff and commission terms; response written back to the deal record. OpenData mapping: account-bound estimate data exposed through a consented API — the same pattern as pulling a statement from a bank, applied to closing-cost line items.

B · Loan officer pre-qual cash-to-close widget

Context: a lender's pre-qual page should show realistic cash to close, not a guess. Data/API: POST /v1/realtytitleagent/buyer-estimate returning fees, prepaids, reserves and total cash to close; rendered inline. OpenFinance mapping: closing-cost reference data feeds an originator's quoting flow the way open-banking fee data feeds a comparison tool.

C · Title office quoting portal

Context: a title agency wants a branded "get a quote" page on its own domain. Data/API: GET /v1/realtytitleagent/rates?state=TX&county=Travis&price=450000 plus the branding-profile endpoint for logo and disclaimers. OpenData mapping: jurisdictional, versioned reference data surfaced as a clean read API — exactly the "open reference data" leg of OpenFinance.

D · Transaction-management auto-attach + audit

Context: when an agent saves an estimate, the matching file in SkySlope/dotloop should get the PDF and a compliance note. Data/API: webhook estimate.created → fetch GET /v1/realtytitleagent/estimates/{id}?format=pdf → attach; FinCEN-alert flag copied into the file's checklist. OpenData mapping: event-driven data sync with a full consent/audit log, the governance model OpenBanking expects.

1 · Authorize & bind an agent session

POST /v1/realtytitleagent/auth/token
Content-Type: application/json

{
  "grant_type": "agent_authorization",
  "agent_ref": "brokerage-user-8842",
  "device_binding": true
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "refresh_token": "rt_9f3c...",
  "profile": {
    "agent_id": "PA-22107",
    "office": "Lone Star Title — Austin",
    "license": "TX-0099123",
    "preferred_underwriter": "WFG National Title"
  }
}

2 · Generate a seller net sheet

POST /v1/realtytitleagent/seller-net-sheet
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "property": {"state":"TX","county":"Travis","city":"Austin","zip":"78701"},
  "sale_price": 525000,
  "loan_payoff": 312450.10,
  "commission": {"total_pct": 5.0, "buyer_side_pct": 2.5},
  "closing_date": "2026-06-15",
  "hoa": {"monthly": 145, "transfer_fee": 250}
}

200 OK
{
  "estimate_id": "ns_7Yk2",
  "currency": "USD",
  "line_items": {
    "owner_title_premium": 3120.00,
    "escrow_settlement_fee": 350.00,
    "recording_fees": 38.00,
    "transfer_tax": 0.00,
    "tax_proration": -1840.22,
    "hoa_proration": -72.50,
    "commission_total": 26250.00
  },
  "totals": {"total_seller_costs": 30193.78, "estimated_net_proceeds": 182356.12},
  "fincen_alert": {"raised": false},
  "pdf_url": "https://api.example.com/exports/ns_7Yk2.pdf"
}

3 · Look up jurisdiction rates

GET /v1/realtytitleagent/rates
  ?state=TX&county=Travis&price=525000&policy=owner_and_lender
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "effective_date": "2026-01-01",
  "owner_policy_premium": 3120.00,
  "lender_policy_premium": 100.00,
  "simultaneous_issue": true,
  "endorsements": [{"code":"T-19.1","amount":52.50}],
  "recording": {"deed": 26.00, "mortgage": 38.00},
  "transfer_tax": {"rate_per_1000": 0.00, "amount": 0.00},
  "source": "preloaded_filed_rate_table"
}

4 · Subscribe to estimate webhooks & handle errors

POST /v1/realtytitleagent/webhooks
Authorization: Bearer <ACCESS_TOKEN>

{ "event": "estimate.created",
  "target_url": "https://crm.example.com/hooks/palmagent",
  "secret": "whsec_3a9f...e21" }

// delivery payload
{ "event":"estimate.created",
  "estimate_id":"ns_7Yk2",
  "agent_id":"PA-22107",
  "type":"seller_net_sheet",
  "created_at":"2026-05-11T14:08:22Z" }

// error envelope (any endpoint)
429 Too Many Requests
{ "error": {"code":"rate_limited","retry_after":12,
  "message":"per-agent quota exceeded"} }

Compliance & privacy

Closing-cost and title data sits inside a regulated workflow, so the adapter is built for it. Net sheets and buyer estimates are consumer-facing settlement figures governed in the United States by the RESPA / TILA-RESPA Integrated Disclosure (TRID) framework overseen by the CFPB; we keep field-level provenance so a quoted figure can be traced to a rate table and effective date. Residential transactions also fall under FinCEN's residential real estate reporting rule, which is why we surface and log the app's FinCEN alert flags rather than dropping them. State-level title insurance rate regulation (filed-rate states) and consumer-privacy law (CCPA/CPRA in California, GDPR for any EU-resident data) shape what we store and for how long. We work strictly from authorized accounts or documented public endpoints, apply data minimisation, keep consent and request logs, and sign NDAs on request. For background on the product itself, see title insurance on Wikipedia.

Built-in safeguards

• Bearer-token auth with short TTL and per-agent quotas
• Request signing + webhook HMAC secrets
• Consent record id attached to every estimate pull
• Rate tables versioned by effective date for auditability
• PII redaction options on exported PDFs and share links
• Configurable retention windows; deletion on request

Deliverables checklist

• API specification (OpenAPI / Swagger) for the endpoints above
• Protocol and auth-flow report (token issuance, refresh, request signing, session handling)
• Runnable source for the net sheet, buyer estimate and rate-lookup APIs (Python / Node.js)
• Webhook receiver sample + retry/HMAC verification code
• Automated tests, Postman collection and written API documentation
• Compliance guidance (RESPA/TRID handling, FinCEN-alert propagation, retention and PII redaction)

About us

We are an independent studio focused on app interface integration, authorized API integration and OpenData / OpenFinance work. The team has hands-on backgrounds in mobile engineering, title and escrow tooling, payments, and protocol analysis, so we can take a project from analysis through build, validation and compliance handoff.

• Real estate, title/escrow, lending and fintech integrations
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance
• Source code delivery from $300 — runnable API source plus full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — use our hosted endpoints and pay only per call, no upfront cost

Contact

For a quote, send us the target app name and your requirements (which data, which platform, expected volume). Open our contact page:

Contact page

Note: RealtyTitleAgent ONE and PalmAgent are products of PalmAgent (PalmAgent Software / WFG). We are an independent integrator and are not affiliated with or endorsed by them.

Engagement workflow

1. Scope confirmation — which data and endpoints (net sheets, buyer estimates, rate tables, saved-estimate sync, webhooks).
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build and internal validation (3–8 business days).
4. Docs, samples and test cases (1–2 business days).
5. First delivery typically 5–15 business days; third-party approvals or multi-state rate work may extend it.

FAQ

What do you need from me to start a RealtyTitleAgent ONE integration?

How long does delivery take?

How do you handle compliance for closing-cost and title data?

Does RealtyTitleAgent ONE have an official public API?