mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Is there a way to programmatically create a monitor (API)? #1888
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1888
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JoelMiller74 on GitHub (Feb 13, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
I think this is a great product and would like to use this internally as we only use Uptime Robot externally. However, we have a lot of websites to monitor and I was wondering if there is an API (REST or otherwise) to create a new monitor (or delete one).
I don't care too much about what type of API like REST, Powershell module, etc... I am just looking for some way to create programmatically instead of just using the UI.
I did not see anything in the docs or other issues about this so if I missed it, I apologize. Any insight would be greatly appreciated!
🐻 Uptime-Kuma Version
1.20.0
💻 Operating System and Arch
Docker Desktop
🌐 Browser
Edge
🐋 Docker Version
20.10.17
🟩 NodeJS Version
No response
@Computroniks commented on GitHub (Feb 13, 2023):
duplicate of #118
@JoelMiller74 commented on GitHub (Feb 13, 2023):
Thank you. I did not see that thread and I appreciate you pointing me towards it! Still trying to digest everything....
This can definitely be closed.