Reference

Partner types & scope

Which surfaces, key kinds, events and console access each partner type gets, and why. Choose your type on the intake form; it determines everything below.

Licensee

A company that runs Ridge Arc Network as its own sales and installation platform, under its own brand. It owns its customers, prices and books.

• Console: full owner console for its own company: users and roles, catalogue, pricing, feature flags (subject to evidence gates), keys, webhooks, exports.
• Keys: may create general and contractor keys for its own systems, and installer-company keys for the installers it works with.
• Events: every catalogue event for its own company.
• Limits: its data is isolated from every other company by row-level security; platform-owned integrations (property data, permits, AI models) are used through the platform, not exported.

Lead source / marketplace

Sends homeowners who asked for a quote. Paid on attribution, so it needs to know its lead was received and, optionally, that it converted.

• Surface: POST /inbound/leads with a general key issued by the receiving company. One key per company you feed.
• Events (optional): quote.sent, quote.accepted, project.completed for leads it sourced, carrying the lead id and stage, never the price.
• Limits: receives an id and created/merged status only. No read access to customers. Consent flags it sends are stored with the lead and govern messaging.

Booking / scheduling vendor

Books and moves sales appointments on the company's behalf.

• Surface: POST /inbound/appointments with a general key; appointment.booked webhook for changes made in the platform.
• Limits: name, address and phone for the visit it books; no quote or project data.

Installer company

Performs installations for one or more companies on the platform. Has its own technicians and scheduling system.

• Surface: Installer API v1 with an installer-company key; install webhooks.
• Console: optional installer workspace logins (INSTALLER_ADMIN, DISPATCHER, TECHNICIAN) for crews without an integration.
• Limits: the installer-safe job projection only: customer name, address, phone, scope, equipment, accessories, schedule, readiness blockers, documents released to it. Never email by default, never price, cost, margin, financing, payment or signatures. Only jobs assigned to it, only while assigned.

Contractor inside a company

A subcontractor set up as a contractor record inside one company, without a separate installer-company account.

• Surface: GET /inbound/jobs and POST /inbound/jobs/:id/status with an installer-contractor key bound to the contractor record.
• Limits: sold jobs for that contractor only; a note-based status update. Companies that need scheduling and assignment writes should onboard as an installer company instead.

Distributor / supplier

Supplies equipment and keeps the company's catalogue current.

• Surface: catalogue feed by arrangement (file or endpoint per distributor), and optional project.completed events for warranty registration where the company opts in.
• Limits: its own SKUs, costs and availability. No customer data, no competitor cost lines, no quote prices.

Financing partner

The production financing design connects customer and proposal records to hosted applications, signing, welcome calls and installation review.

• Exchange: approved customer fields, equipment, system and proposal pricing, external identifiers, application and signing status, welcome-call links, installation evidence and QC outcomes.
• Boundary: agree contact-field sharing at onboarding. Sensitive credit inputs stay in the provider-hosted flow; internal costs and margin are excluded.
• Contract: partner-specific routes, schemas and event names are agreed with the provider. Installer API keys do not grant financing access.

Incentive program

Rebate and incentive programs use their own eligibility rules, application handoff and approved data-sharing scope. Rebate status is separate from a lender decision or funding confirmation.

Accounting / bookkeeping

Keeps the company's ledger and payroll.

• Surface: financial journal webhook events (deposits, invoices, refunds, payouts, adjustments) and console exports.
• Limits: journal-level amounts with project and invoice ids; no customer contact details; no card or bank data (the payment provider holds those).

Something else

Choose Other on the intake form and describe the integration. Most requests fit one of the types above once we talk; genuinely new ones become a documented type here before any key is issued.