Source
API, monitoring as code & team administration — found from sitemap — Uptimia
Checked for Uptimia on 14 Nov 2026
- Page
- https://help.uptimia.com/articles/uptimia-api-v2-endpoint-map
- Checked
- 14 Nov 2026, 09:30 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:4f2b356fbca7e308cd82f47c711cae67c26fe6469e8ec226270a2eac669709ce
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
API v2 base Report an error
“Everything you can do in the control panel has a route under /api/v2/.”
-
Auth Report an error
“Every request carries Authorization: Bearer <your key>. Requests are JSON in and JSON out.”
-
API key scoping Report an error
“Keys carry the role and monitor-group scope of the seat that minted them.”
-
Token endpoint Report an error
“POST /api/v2/auth/token mints one from credentials.”
-
Monitor families Report an error
“Each monitor family is its own resource with its own base path, and that path is not always the word you see in the control panel.”
-
Security monitor legacy name Report an error
“Security monitors were called Virus monitors before, and the API keeps the old name: the path is /api/v2/virus and the type key is virus.”
-
Crud pattern Report an error
“Eleven of the twelve families answer the same five calls: GET the base path to list, POST it to create, then GET, PATCH and DELETE on /{id}.”
-
Put alias Report an error
“Four families also accept PUT on /{id} as an alias of PATCH: API, Heartbeat, DNS and Blacklist.”
-
Cross family actions Report an error
“Three actions work across families, with the family key in the path: POST /api/v2/monitors/{type}/{id}/pause, /resume and /copy.”
-
Bulk creation Report an error
“Bulk creation is POST /api/v2/monitors/bulk, with POST /api/v2/monitors/bulk/preview to dry-run the list first.”
-
Manual incidents Report an error
“POST /api/v2/monitors/{type}/{id}/manual-incident opens one, with a message and a severity of critical or degraded, GET on the same path reads it, and POST .../manual-incident/resolve closes it.”
-
Log readers Report an error
“GET /api/v2/logs Check results across ten families: uptime, speed, transaction, SSL, domain, security, server, API, DNS and blacklist.”
-
Incident impact plan gate Report an error
“none and partial need the Professional plan or above”
-
Bulk incident impact Report an error
“POST /api/v2/incidents/impact Set none or full on up to 500 incidents in one call, all or nothing”
-
Data exports Report an error
“File exports live beside the JSON readers, two of them at GET /api/v2/logs/export/csv and GET /api/v2/incidents/export/csv.”
-
Public share links Report an error
“POST /api/v2/logs/{type}/{id}/public-link and POST /api/v2/incidents/{type}/{id}/public-link mint a no-login share URL.”
-
Retention window by plan Report an error
“Your plan's readable window sets how far back a range can reach. On Uptime, Speed and Security, a date_start earlier than that floor is silently raised to it rather than refused.”
-
Default windows Report an error
“Every other clamped endpoint falls back to its own default window, one of 24 hours, 7, 14, 30 or 90 days by route”
-
Status pages API Report an error
“GET, POST /api/v2/status-pages List and create pages”
-
Reports API Report an error
“GET and POST /api/v2/reports list and create scheduled reports”
-
Maintenance API Report an error
“GET, POST /api/v2/maintenance List windows and create one. horizon_days sets how many days of occurrences the list expands, clamped to 1–31 (default 14)”
-
Alerting API Report an error
“GET, POST /api/v2/contacts · GET, PATCH, DELETE /{id} The address book”
-
Groups bulk membership Report an error
“POST /api/v2/groups/{id}/monitors Add and remove many monitors in one group in a single call, with add and remove lists of up to 1000 each.”
-
Location profiles min probes Report an error
“If a profile ends up with fewer than 6 probes, every entry fails with too_few_locations and nothing is written.”
-
Templates API Report an error
“GET, POST /api/v2/monitor-templates · PATCH, DELETE /{id} Saved monitor setups.”
-
Account management API Report an error
“GET, POST /api/v2/users · GET, PATCH, DELETE /{id} The seat roster and its lifecycle”
-
Reference exclusions Report an error
“The hosted reference leaves out the account-management and control-panel-internal groups, so the paths above are the record for those.”
-
Rate limits Report an error
“Uptimia sets no global per-key request quota, and ordinary monitor reads and writes are not counted against one. Twelve named actions carry their own limits.”
-
Pagination Report an error
“Monitor lists take limit and offset, GET /api/v2/logs takes page and limit (default 20)”
-
Error envelopes Report an error
“A 404 raised inside a controller, for a record that is not yours, comes back as ordinary JSON.”
-
Legacy API reference Report an error
“https://developers.uptimia.com The v1 (legacy) reference, still published and still where /api and the control panel's link land”
-
Uptime logs deprecated Report an error
“/api/v2/uptime/logs still exists alongside /api/v2/logs; new code should use the latter.”
-
Signin history retention Report an error
“GET /api/v2/settings/sign-ins Your own last 10 sign-ins and failed attempts, kept for 90 days”
Scores citing this record
- The Agency Developer API, monitoring as code & team administration
- The Agency Developer Uptime reports, data & the vendor's own reliability
- The Customer Support Lead API, monitoring as code & team administration
- The E-Commerce Operations Manager API, monitoring as code & team administration
- The SaaS Platform Engineer API, monitoring as code & team administration
- The Information Security Officer API, monitoring as code & team administration
- The Information Security Officer Uptime reports, data & the vendor's own reliability
- The Skeptic API, monitoring as code & team administration
- The Skeptic Uptime reports, data & the vendor's own reliability