Skip to main content

Integration overview

SpaceRivers exchanges data with external systems through authenticated APIs and the SR-Bridge desktop agent.

flowchart LR
    SOURCE[Customer system] --> BRIDGE[SR-Bridge]
    BRIDGE --> STAGE[Inbound staging]
    STAGE --> VALIDATE[Validate]
    VALIDATE --> MASTER[SpaceRivers master and cost data]
    MASTER --> OPERATE[Schedule, time, expense, budget]
    OPERATE --> OUTBOUND[Eligible outbound records]
    OUTBOUND --> BRIDGE
    BRIDGE --> SOURCE

Inbound domains​

The current bridge supports employee, job, phase, cost-code, initial-budget, change-order-budget, committed-cost, and actual-cost jobs. Imported payloads are staged so invalid records can be corrected without silently changing operational data.

Outbound domains​

Configured flows can retrieve eligible time-sheet and expense records. The bridge writes them to the customer system, then reports success or structured failure so SpaceRivers can update posting state.

Responsibilities​

  • The integration administrator owns connection, mapping, and API-key setup.
  • The data owner resolves invalid master or financial data.
  • Payroll/accounting reconciles batch totals and posting results.
  • SpaceRivers logs show API/staging activity; SR-Bridge logs show local extraction and write activity.

Never edit an integration identifier casually. It is part of the contract that prevents duplicates and connects related records.