Availability and appropriate use
This public endpoint is for facility inquiries submitted with the prospective customer’s authorization. Online handoff is not connected yet; use the office phone number until delivery has been configured and verified. The form-config endpoint reports configuration presence, not a successful delivery test.
Submit an inquiry
POST JSON to /api/v1/walkthrough-request using Content-Type: application/json and an Idempotency-Key of 16–128 letters, digits, hyphens or underscores. Supply contact_name, work_email, company, facility_city and service_needed. All values are strings. Use the service enum in the linked specification; the janitorial value remains Commercial Cleaning & Janitorial for compatibility.
Understand the response
A 201 response means the configured intake provider acknowledged the handoff and returns a request reference. It does not book an appointment. A 422 response contains field errors; 409 indicates a key reused with different details. Missing configuration returns 503, never a simulated receipt.
Retry safely
Keep the same key and unchanged fields when retrying a transient 429, 502 or 503 response. Follow Retry-After where returned. The public endpoint accepts a maximum 16 KB body and limits each source IP to 10 attempts per 15 minutes. Browser origins must match the configured website; arbitrary browser CORS access is not enabled. Do not include confidential information.
Delivery verification
The automated contract and retry checks use test providers. Real inbox receipt, duplicate delivery prevention with the live store and analytics conversion delivery still require a configured staging destination and an approved labeled test. No production or agent-readiness certification is implied.