Appearance
API overview
INFO
Change log (updated 12 November 2026)
Added documentation for court-status requests and result polling for lighting automation, including freshness, offline-camera behaviour and error handling. Available through the production Partner API.
Documentation corrections; the API did not change. Corrected the GET /video/{video_id}/results status codes, the empty /scheduled response, connect link replacement, login 401 and the error formats. Added run_version on video.status_changed, the /schedule defaults, camera statuses and control errors, and the history rating fields.
Added annotation consent and optional app returns on POST /partner/player-links, current player-link lookup, and GET/PATCH recording annotations. Includes request/response examples, screen flows and token-reuse guidance.
Added court_keypoints to GET /video/{video_id}/results, the multi_match option on schedule and start, and a reference for the shot and outcome counts in match.json. Corrected the schedule conflict status to HTTP 409.
Deployment status: live in production. Through api.clutchapp.io, POST /start does not pass multi_match on yet; use /schedule for multi-match recordings until it does.
Full change log here
Base URL: https://api.clutchapp.io/v1
The UUIDs were generated locally for this page and do not come from Clutch data. All endpoints except login require Authorization: Bearer <token>.