Technical Architecture

Title Company API Integration

Comprehensive architecture diagram showing platform integration with title companies through REST, SOAP, and SFTP workflows.

System Architecture Diagram

                         ┌──────────────────────────┐
                         │        User Apps         │
                         │  (Buyer / Seller / RE)   │
                         └────────────┬─────────────┘
                                      │
                                      ▼
                         ┌──────────────────────────┐
                         │   Frontend Application   │
                         │  (Web / Mobile UI Layer) │
                         └────────────┬─────────────┘
                                      │
                                      ▼
                         ┌──────────────────────────┐
                         │     API Gateway Layer    │
                         │  Auth, Routing, Throttles│
                         └────────────┬─────────────┘
                                      │
                                      ▼
                   ┌────────────────────────────────────────┐
                   │        Platform Backend Services        │
                   │────────────────────────────────────────│
                   │ • Order Management Service             │
                   │ • Document Service                     │
                   │ • Workflow Engine                      │
                   │ • Notification Service                 │
                   │ • Audit & Logging                      │
                   └────────────┬───────────────┬──────────┘
                                │               │
                                │               │
                                ▼               ▼
         ┌──────────────────────────────┐   ┌──────────────────────────────┐
         │  Title Integration Adapter   │   │  Document Exchange Adapter   │
         │ (REST / SOAP / SFTP Bridge) │   │ (PDF, XML, SFTP, Email-Ingest)│
         └────────────┬────────────────┘   └────────────┬─────────────────┘
                      │                                   │
                      ▼                                   ▼
        ┌──────────────────────────────┐   ┌──────────────────────────────┐
        │   Title Company API Layer    │   │ Title Company Document Portal │
        │  (REST or SOAP Endpoints)    │   │ (SFTP, Upload, Email Intake)  │
        └────────────┬────────────────┘   └────────────┬─────────────────┘
                      │                                   │
                      ▼                                   ▼
        ┌──────────────────────────────┐   ┌──────────────────────────────┐
        │  Title Company Internal Sys  │   │   Title Ops / Escrow Team    │
        │  Order Mgmt, Escrow, Curative│   │  Manual Review & Processing  │
        └──────────────────────────────┘   └──────────────────────────────┘

How the Architecture Works

1. User Apps

Buyer, seller, lender, attorney, and title users interact with your platform.

They trigger events like "Open Title Order" or "Upload Contract."

2. Frontend Application

Displays title status, documents, escrow milestones, and closing timelines.

Sends requests to your backend through the API Gateway.

3. API Gateway

Handles authentication, rate limiting, routing, and request validation.

Normalizes all inbound/outbound traffic.

4. Backend Services

Core logic including Order Management, Workflow Engine, Document Service, Notifications, and Audit Logging.

Backend Services (Core Logic)

Order Management Service

Creates and tracks title orders. Stores metadata and order IDs.

Workflow Engine

Syncs milestones (title search, commitment, exceptions, clear-to-close). Triggers notifications and tasks.

Document Service

Stores contracts, commitments, exceptions, closing packages. Handles secure transmission.

Notification Service

Sends updates to buyers, sellers, attorneys, lenders.

Audit & Logging

Tracks every API call and document exchange.

5A. Title Integration Adapter

Handles all API types:

REST

JSON payloads, OAuth2

SOAP

XML, WSDL, token headers

SFTP

File-based workflows

Fallback for legacy title shops

This adapter normalizes everything into a single internal format.

5B. Document Exchange Adapter

Handles:

PDF ingestion

XML parsing

SFTP uploads/downloads

Email-based document intake

6. Title Company Systems

A. API Layer

REST or SOAP endpoints for:

• Create order
• Get status
• Upload documents
• Retrieve commitments
• Sync milestones

B. Document Portal

SFTP or secure upload for:

• Title commitments
• Exceptions
• Closing instructions
• Final closing package

C. Internal Title Ops

• Curative work
• Escrow processing
• Closing scheduling