hosting
GET /v1/sites/{siteId}/vitals/history
Get a site's speed history and change timeline.
인증
Bearer 토큰으로 API 키를 전송하세요. 이 엔드포인트는 명세에 특정 권한을 명시하지 않으므로, 가정하기보다는 키에 필요한 최소한의 권한을 부여하고 응답을 확인하세요.
이 엔드포인트는 조직 ID를 받지 않습니다. 사용자의 키가 이미 속한 조직을 식별하며, 응답은 해당 조직으로 한정됩니다.
무료 체험하기
대괄호 안에 있는 모든 내용을 사용자 지정 값으로 바꾸고, 키 플레이스홀더는 대시보드의 키로 바꾸세요.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/vitals/history \
-H "Authorization: Bearer zdk_live_…"로그인하셨나요? 대시보드의 API 콘솔이 실제 조직 ID와 본인의 키를 자동으로 채우고 라이브 API를 대상으로 요청을 실행하므로 실제 응답을 확인할 수 있습니다. API 콘솔에서 이 엔드포인트를 여세요
상세 정보
How the site's speed has moved over time, and what changed on the site, on one axis — so a customer can see that activating a plugin cost them 0.4 s rather than having to remember it. This is the consumer that was missing. Vitals rows have been kept since #626 with a comment saying they exist "so the Performance tab can show a trend"; nothing ever read them, there was no time-series endpoint, and there was no charting library in the repo. The trend was being stored correctly, for weeks, for nobody. Two producers, one axis. points are Lighthouse measurements taken off the request path by a scheduled sweep. events are what the site reported about itself over a signed webhook (plugin activated, core updated, theme switched, PHP version changed), merged with its successful deploys. Events carry the time they happened on the site, so a webhook delivered late still lands beside the score it explains. score_delta is computed here. Two clients subtracting two nullable columns is two chances to render -87 for "we did not measure the earlier one". ⚠️ Cadence. The sweep measures a fixed number of sites per hour, so on a large estate a site's points can be days apart. A site that reports a change is moved to the front of the next sweep, which is why the timeline — not the sweep — is the primary signal for attributing a regression (docs/85 §4.2). RLS-scoped to a site the caller can view (sites.view); an out-of-scope or unknown id is a 404 alike, exactly like getSite.
매개변수
| 이름 | 유형 | 필수 | 설명 |
|---|---|---|---|
siteId (path) | Uuid | 예 | Site ID (UUIDv7). |
days (query) | integer | 아니요 | How far back to look. Clamped rather than rejected — this is a cheap read of the caller's own data, so a 422 on days=0 would be a worse experience than a sensible window, and… |
응답
| 이름 | 유형 | 필수 | 설명 |
|---|---|---|---|
points | SiteVitalsHistoryPoint[] | 예 | Oldest → newest, so a chart renders it without reversing. Capped; when a site has more measurements than the cap, the most recent are returned — a chart that stopped before… |
events | SiteEvent[] | 예 | Oldest → newest, on the same axis as points. |
stack_type | string | 예 | The site's configured stack — static, php, wordpress, woocommerce, node, one_click. Decides which advice and which events apply: a static site must never be given… |
stack_packs | string[] | 예 | What the newest lab run detected. Resolves one_click, which is a container for "whatever the customer installed" and therefore knows nothing about itself. |
opportunities | SiteVitalsOpportunity[] | 예 | The newest lab run's opportunities. On a customer surface these are the same rows getSiteVitals returns; on the staff surface they additionally include owner: platform audits,… |
recommendation | SpeedUpRecommendation | 예 | Which optimisation tier to lead with for this site, and the evidence for it (docs/85 §7). Before this, the speed-up offer fired on a traffic-light band alone while the platform… |
이 엔드포인트가 반환할 수 있는 오류
401 · 403 · 404 · 429