One customer journey. Connected partner systems.
Ridge Arc Network coordinates customer intake, home comfort proposals, financing, contracts and installation. This is the production workflow partners design against.
Integration environments
| Environment | Application | API base |
|---|---|---|
| Production | ridgearc.network | https://ridgearc.network/api |
| Staging / sandbox | staging.ridgearc.network | https://staging.ridgearc.network/api |
| Partner documentation | dev.ridgearcnetwork.com | |
Use separate credentials, records and callback destinations for each environment. Confirm account activation with your onboarding contact before connecting customer traffic.
Who owns each part
| System | Responsibility |
|---|---|
| Ridge Arc Network | Customer and project context, equipment and proposal scope, authorized pricing, operational work and the partner status shown to staff. |
| Financing partner and financier | Approved financing products and disclosures, hosted credit applications, decisions, loan documents and funding facts. |
| Signing provider | Signing sessions, document versions, executed documents and signature evidence. |
| Installation and review teams | Scheduling, required installation evidence, QC review, corrections and completion approval. |
Every integration agreement identifies the authoritative system for each field and status. A financing approval, a signed document, an installation completion and a settled payment are separate facts.
Customer to contract
- Identify the customer. Exchange the approved customer fields and retain each system’s customer and project identifiers.
- Synchronize the proposal. Send equipment, system configuration and authorized pricing with a proposal version. Agree how revisions affect applications and signed documents.
- Present financing. Display provider-approved product information and open the hosted application in an approved embedded flow or a direct homeowner link.
- Receive the decision. Verified provider updates return the application state and permitted offer details to the project.
- Trigger signing. Start the provider’s document-signing process against the agreed proposal version and retain its document identifiers and signing status.
- Complete the welcome call. Display the partner-returned welcome-call URL and track the completion outcome separately from link creation.
Installation through quality review
The integration design carries installation progress, the partner’s required fields and photo evidence to the reviewing system. QC results return with the fields or evidence requiring correction. Funding milestones are tracked separately from installation and QC acceptance.
At onboarding, agree required equipment identifiers, installation dates, photo categories, file types and size limits, reviewer responsibilities, correction handling and the exact conditions for requesting and confirming funding.
API contracts and access
The OpenAPI reference defines the implemented inbound and Installer API routes. The financing workflow defines the partner-specific production design; its endpoint paths, payloads and event names are finalized with the provider during onboarding. A workflow description does not grant an API scope.
- Inbound API: leads, appointments and contractor job updates.
- Installer API v1: assigned jobs, status events, scheduling and technician assignments.
- Signed webhooks: authenticated change notifications with retries and duplicate handling.
- Financing exchange: customer and proposal synchronization, hosted applications, signing, welcome calls and installation review under an agreed partner contract.
Production acceptance
Prove the full journey in the sandbox with synthetic records: create, revise, apply, sign, complete the welcome call, submit installation evidence, resolve a QC correction and reconcile funding status. Include duplicate delivery, out-of-order updates, expired links, declined applications, cancellation and recovery from an unavailable provider.
Agree data ownership, credentials, security contacts, support escalation and the activation checklist before enabling production traffic. Start with partner intake.