Websites
Get Website Details
Returns the website detail page data in one call (mega endpoint). This includes monitoring stats, alert history, incident history, monitoring chart data, and maintenance windows.
GET /api/websites/:websitePublicId/details
Example (cURL)
BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"
curl -X GET "$BASE_URL/api/websites/9a3d4d4d-7a4b-4f37-a9df-2a6f6d9d7a10/details?range=day" \
-H "Authorization: Bearer $TOKEN" \
-H "Accept: application/json"Query Parameters
range(optional):day|week|month|year(default:day)date(optional): reference date for calendar viewsstartDate/endDate(optional): custom date window for zoomed viewsgranularity(optional): e.g.minutefor non-aggregated data (when supported)
Response
{
"website": {
"id": 101,
"name": "Main Marketing Site",
"url": "https://deinkunde.com",
"status": "active",
"monitoringType": "combined",
"customerId": 1
},
"uptimeStats": {
"day": "100.00",
"month": "99.95",
"year": "99.90",
"dayAvgResponse": 125,
"monthAvgResponse": 118,
"yearAvgResponse": 120,
"blockedRatio": { "day": 0, "week": 0, "month": 0.02, "year": 0 }
},
"monitoringData": {
"responseTimeData": [],
"statusData": [],
"uptimePercentage": "99.95",
"checkSuccessRatePercentage": "99.80",
"totalChecks": 100,
"successfulChecks": 99
},
"incidents": {
"history": [],
"total": 0,
"ongoing": 0,
"totalDowntime": "0m"
},
"alerts": {
"history": [],
"total": 0,
"notificationContext": null
},
"maintenance": {
"inMaintenance": false,
"activeWindows": [],
"allWindows": []
}
}Response Fields
uptimeStats.day|week|month|year: uptime percentage as a string with two decimals, ornullwhen nothing was measurable in that period. The same holds formonitoringData.uptimePercentage.uptimeStats.blockedRatio: per period, the share we could not measure, between0and1,nullfor an empty period. A site's bot protection can answer our check with a challenge instead of the page; that time leaves the uptime calculation, so it counts neither as up nor as down.uptimeStatsMeta.day|month|year:downtimeMinutesandincidentsfor the period, pluschecksTotalandchecksFailed. Fordaythese count check cycles (one per minute, failed when as many locations as the alert threshold failed together) over the last 24 hours. Formonth(the last 30 days) andyear(since 1 January, UTC) they count single location checks of every check type, read from the 15-minute and daily aggregates, because the per-minute cycles are only kept for 7 days. Do not compare the day figure with the month or year figure directly.uptimeStats.dayAvgResponse|weekAvgResponse|monthAvgResponse|yearAvgResponseand the matching…AvgPageSizefields: averages over the same windows as the uptime, the last 24 hours, 7 days and 30 days and the year since 1 January (UTC).monthAvgPageSizeandyearAvgPageSizearenull, because page size is kept for 7 days only.
Common errors
400 Invalid website public ID (UUID)when:websitePublicIdis invalid401 Unauthorizedwhen you are not logged in404 Not Foundwhen the website does not exist or belongs to another customer or organization (the two cases are indistinguishable on purpose)500 Failed to fetch website detailson server errors
Data retention
The series is read from the finest aggregate that still covers the requested range: minute data for the last 7 days, 15-minute buckets up to 30 days back and daily buckets beyond that. In the coarser buckets timingDns, timingTcp, timingTls, timingTtfb and timingTransfer are reported as 0 (not measured), and successRate is the share of successful location checks rather than the per-minute quorum.