Integrations
Plugs into the systems you already run
13 connectors and adapters across property data, rentals and screening, title and settlement, lending, documents, payments, services, growth, analytics, and messaging — with honest availability states instead of a logo wall.
Connector library
What is available today, and what is not
Property data
RESO Web API
Standards-based MLS/IDX ingestion with per-feed field mapping and display rules.
Property data
CSV / SFTP bulk import
Scheduled imports with mapping profiles and reject reports.
Rentals
Rental screening (CRA)
FCRA-compliant consumer reporting agency integration with consent capture and adverse action notices.
Rentals
Rent & deposit payments
A licensed payment partner collects rent and holds deposits. The platform never takes custody of funds.
Title & settlement
Qualia
Title and escrow order creation with status write-back to the deal.
Title & settlement
RamQuest / ClearEdge class systems
Adapter built per tenant; portal handoff available day one.
Lending
Lender & LOS handoff
Consumer-chosen application handoff, pre-qualification requests, and loan milestone status on the transaction record. No lead routing to lenders.
Documents
E-signature providers
Envelope creation, status webhooks, and certificate archiving for sales and leases.
Services
Provider scheduling & booking
Inspection, appraisal, and moving requests with calendar handoff and per-job scoped document access.
Payments
Marketplace payouts
Split payments between licensed parties, rent payouts to landlords, provider billing, and tenant payout ledgers.
Growth
CRM & marketing suites
Two-way lead and activity sync with configurable field mapping and consent-state sync.
Analytics
Valuation & AVM providers
Multiple AVM sources with tenant-selectable default models, plus rental-yield models.
Messaging
SMS & email delivery
Template management, quiet hours, opt-out handling, and TCPA-aware consent capture.
Categories
Five categories, and what each one carries
Property data and rentals
MLS/IDX via RESO Web API under the tenant's own display rules, CSV and SFTP migration, manual entry, and rental inventory from a property manager's own system.
Rental operations
FCRA-compliant screening through a consumer reporting agency, and rent and deposit collection through a licensed payment partner. The platform never takes custody of funds.
Settlement and closing
Title and escrow order creation with status write-back, document exchange, and closing statement reconciliation. Fees here are flat technology fees, never per order.
Lending
Consumer-chosen application handoff and loan milestone write-back. No lead routing to lenders, and no per-loan payment structure anywhere in the product.
Providers and services
Scheduling and booking handoff for inspections, appraisals, and moves, with document access scoped to the individual job.
How it works
Three things happen on every connection
You connect the account
Where an integration needs credentials, the partner supplies them for their own tenant. One partner's connection never sees another's data, and credentials are stored server-side and never exposed to the browser.
The gateway maps, validates, normalizes
Inbound feeds are mapped to the canonical property model, validated, deduplicated, and geocoded. Anything rejected is reported back with the reason instead of failing silently.
Status flows back into the deal
Outbound events write into the transaction record, so an appraisal result or an escrow milestone appears on the deal rather than arriving by email and living in an inbox.
Custom adapters
When the system you need is not on the list
- Tenant-specific title, settlement, or LOS system with no standard connector
- A screening or rent-payment provider outside the standard library
- Legacy CRM with no modern API but an export you can schedule
- Proprietary valuation or rental-yield model you want served inside your own marketplace
- Franchise-mandated internal system that everything else has to talk to
Credential handling
How partner credentials are stored and scoped
- Stored server-side and encrypted at rest, scoped to the tenant that supplied them.
- Never returned to a browser, never written to logs, never present in client bundles or build output.
- Rotation is self-service. Rotating a credential revokes the previous value immediately rather than at the next sync.
- Every use of a credential is attributable in the audit log, including which sync or operation consumed it.
Third-party API keys stay out of this website's code and configuration. They live in the platform's secret store, which is why nothing on this page is a placeholder for a real key.
Next step
Send us your stack and we'll tell you what connects
List the systems you run today — MLS provider, CRM, transaction manager, title partner, lender, e-sign. We will map each one to a connector or a scoped adapter and tell you which are quick wins.