Skip to main content
SiteVisit turns a walkthrough video into a structured site report: a transcript, a summary, and a prioritized list of action items with timestamps and evidence photos. The API exposes the same data your dashboard sees, so you can pipe it into the systems your team already runs in — work-order platforms, BI tools, Slack, or your own internal apps.

​
What you can do today

The v1 API is full CRUD. You can: Read properties, visits, and action items the same way the dashboard sees them. Create
  • A new property (subject to plan limits)
  • A site visit (manually, alongside the existing video-upload flow)
  • An action item on a visit (text-only — no video frame required)
Update + complete
  • Patch any action item’s title, description, category, location, priority, status, or assignee
  • Mark an action item DONE with an attribution + note + completion photo
Capture media from a phone
  • Issue a short-lived QR / URL token that takes the user to a sign-in-free camera page on their phone, attaches the photo back to the right action item, and expires in 24 hours
Delete properties, visits, or action items — cascades as expected. Receive webhooks for any of the 16 event types in the catalog — signed with HMAC-SHA256 using the Stripe pattern, retried with backoff if your endpoint is down, delivered to multiple endpoints in parallel. Everything is also exposed as MCP tools, so Claude Desktop / Cursor / your own agent can do all of the above in natural language.

​
Where things live

API reference

Every endpoint, parameter, and response — generated from the live OpenAPI spec.

Quickstart

Generate a key and make your first call in under five minutes.

Authentication

Bearer tokens, key rotation, and how secrets are stored.

Errors

Every error code, what it means, and how to fix it.

​
Base URL

All endpoints are versioned under /api/v1. We add new fields and endpoints freely; breaking changes get a new version (/api/v2) and a six-month deprecation window on the old one.

​
Beyond REST

We also run an MCP server so Claude Desktop, Cursor, and any other MCP-compatible agent can read your SiteVisit data with natural language. It wraps the same service layer — every REST endpoint above has a matching MCP tool. One key, two protocols.