The Zwivio Network API is a public machine-readable interface for people, AI assistants, and applications. It can share supported public information such as Market Presence, Serviceability, point-in-time Fulfillability, and Network Handoff. It does not assign a contractor or complete a homeowner request by itself.
Network API
Zwivio Network API
The Zwivio Network API is home-service infrastructure for people and AI assistants. Applications can discover where Zwivio operates, check whether a request can be accepted, evaluate point-in-time network fulfillability, and prepare known request details for homeowner review. The homeowner remains in control and submits through Zwivio's existing intake.
Network API is distinct from Zwivio's contractor Dispatch Network and does not reserve a contractor or autonomously book service.
Separate layers
- Serviceability asks whether Zwivio can currently accept the specified request under publication, intake, geographic, and operational rules. A serviceable result does not mean supply exists.
- Fulfillability asks whether dispatch-eligible network supply appears to exist for that structured request at the moment of evaluation. It is a point-in-time signal. It is not a reservation, appointment, contractor selection, ETA, or assignment guarantee.
- Network Handoff stores convenience details an external client already collected and returns a Zwivio-built path into the existing homeowner intake. The homeowner reviews and submits. It does not create a service request and does not reserve a contractor. An earlier Fulfillability result can change before submission.
- Transaction and assignment are a separate homeowner lifecycle. Submitting a request and officially assigning a service business are not part of these Network operations.
Public endpoints today
GET /public/network/v1/serviceabilityGET /public/network/v1/market-presence— the public operating footprint, not operational coverage, contractor availability, fulfillability, or assignment capacity.POST /public/network/v1/fulfillabilityPOST /public/network/v1/handoffs— temporary prefill only. Zwivio builds the returned path. Phone, email, and homeowner name are not accepted.GET /public/network/v1/handoffs/{handoffId}— reads that temporary prefill. Possession of the id is not homeowner authentication.
Canonical OpenAPI document: GET /public/network/v1/openapi.json. That relative path is served by the Network API. This website does not host a second copy, and no API hostname is published here.
Looking for homeowner availability? Check service availability for your ZIP.
Machine-readable semantics: Network API semantics.
Network API FAQ
Short answers about what the public Network API can check, and what it does not do.
No. The Network API is a public interface for people, AI assistants, and applications. The Dispatch Network is Zwivio’s network of eligible independent service businesses that receive routed homeowner requests and official assignments. They are different.
Serviceability asks whether Zwivio can currently accept the specified ZIP, service, and request type under its current publication, intake, geographic, and operational rules. It does not mean a contractor is available. Fulfillability asks whether dispatch-eligible supply appears to exist for that request at that moment. It is point-in-time. It is not an appointment, a reservation, a selected contractor, an arrival time, an assignment, or a guarantee.
No. A fulfillable result means dispatch-eligible supply appeared to exist at that moment. It does not reserve a contractor, select one, or guarantee that the request will be fulfilled.
No. Fulfillability does not provide an appointment or an arrival time. Timing is determined later, after a homeowner submits a request and the existing assignment process continues.
Network Handoff lets an application or AI assistant prepare supported request details it already has and open Zwivio’s existing homeowner intake. The homeowner reviews and can edit those details, completes normal verification, consent, and any required fee acknowledgement, and then submits.
No. Creating or opening a Network Handoff does not submit the request, reserve a contractor, create an assignment, or sign the external application in as the homeowner.
No. Zwivio does not currently provide an official ChatGPT, Gemini, Claude, or other third-party workflow that books a contractor through the Network API. An assistant may prepare a request for the homeowner to review. The homeowner still submits it. Zwivio does not control whether a named product discovers or uses Zwivio’s public information.
AI assistants and applications may use Zwivio’s public Network API. Zwivio publishes that machine-readable interface. Zwivio does not control whether a particular product discovers, indexes, calls, or uses it, and it does not currently offer an official autonomous booking integration with a named AI product.
No. Public Network API results describe the network and the request. They do not show an individual service business’s name, contact information, how many businesses are eligible, rankings, distance, reliability, tier, capacity, schedule, Field Console data, protected compliance information, or Zwivio’s internal routing. A Fulfillability result says whether dispatch-eligible supply appears to exist. It does not identify which businesses produced that result, and it is not a contractor directory.
No. A service business does not need Field Console Pro, a CRM integration, or a Network API integration merely because homeowners or applications use the Network API. Dispatch eligibility, routing, offers, assignment, fees, and Field Console behavior stay the same.