Hoot Lens API
API by Hoot Lens · rest
The Hoot Lens REST API records website interaction evidence for the sites you add and returns it as visits, recordings, heatmaps, goals, funnels and change impact. This document describes the endpoints a person or an agent uses to read that evidence and to log changes. Everything returned is observed behavior with its evidence; the API makes no claims about visitors' emotions or intent. Authentication. Send Authorization: Bearer <credential>. The credential is either a Firebase ID token (a signed-in person, whose role on each site decides what they may do) or a personal access token (hl_pat_...) made in the dashboard. A personal access token carries the scopes read, replay and annotate, belongs to one site, expires in 30, 60 or 90 days, and can do no more than its creator's current role allows. Operations marked x-hootlens-sign-in-only need a signed-in person and answer 403 to a token. OAuth. The hosted MCP endpoint (/mcp, Streamable HTTP) signs assistants in with…
Verification: observed. Source: crawl.
Capabilities (60)
- Service health
- Signed-in account state
- List sites
- Create a site
- Update site settings
- List change markers
- Log a change
- Delete a change marker
- Impact of a change
- Report a completed business outcome
- Conversion outcomes by original visit source
- List element names
- Name an element
- Remove an element name
- List JavaScript errors
- Get a JavaScript error
- List finding work
- List finding assignees
- Read finding work
- Update finding work
- Findings
- List funnels
- Create a funnel
- Replace a funnel
- Delete a funnel