Overview

Back Office API Documentation

Intro — What can be done with this API

The Back Office API exposes brokerage accounting, commissions, deals, and compliance data so other systems can read or write transactions, splits, fees, contacts, and checklist conditions programmatically. It enables commission automation, CRM/TMS synchronization, financial reporting, and compliance orchestration across platforms. Common adopters include vendor integrators (CRM, transaction management, BI, payroll) and brokerage finance, compliance, and operations teams building internal tools.

Common Use Cases

  • Pull a brokerage directory for routing, CRM sync, and provisioning

    • GET /v1/offices · GET /v1/offices/{officeId}

  • Build or enrich a transaction rolodex with business and client contacts

    • GET/POST /v1/transactions/{transactionId}/business-contacts
    • GET/PATCH/DELETE /v1/business-contacts/{businessContactId}
    • GET/POST /v1/transactions/{transactionId}/client-contacts
    • GET/PATCH/DELETE /v1/client-contacts/{clientContactId}

  • Automate commission splits and fee audits

    • GET /v1/transactions/{transactionId}/tiers/{tierId}/commissions
    • POST /v1/transactions/{transactionId}/tiers/{tierId}/commissions
    • PATCH/DELETE /v1/commissions/{id}
    • GET /v1/commission-fees/{id}

  • Sync deal checklist conditions with TMS/form/compliance systems

    • GET /v1/condition-types
    • PATCH /v1/condition-types/{conditionTypeId}
    • GET/POST /v1/transactions/{transactionId}/conditions

  • Drive analytics or tiering logic using classification catalogs

    • GET /v1/classifications
    • GET /v1/classifications/{classificationId}

  • Build a consolidated “single pane of glass” deal view for staff and agents

    • Combine contacts, commissions, fees, conditions, and office metadata