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 read-only. You can:
  • List the properties on your account, with visit and open-item counts.
  • List site visits, filtered by property or status.
  • List action items, filtered by property, visit, status, or priority — including links to evidence photos and the completion photo.
Writes (creating visits, updating action item status, marking items done) are coming next; see Versioning for how new endpoints are added.

​
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

https://sitevisit.app/api/v1
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.