mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Support external interface call operation #3856
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#3856
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 @songzhibin97 on GitHub (Dec 23, 2024).
📑 I have found these related issues/pull requests
🏷️ Feature Request Type
API / automation options
🔖 Feature description
It is possible to treat uptime-kuma purely as a service, with functional operations providing api for other services to use
✔️ Solution
You can select uptime-kume for integration in other integrations to provide monitoring content and corresponding notifications, which will give you more options
❓ Alternatives
https://github.com/lucasheld/uptime-kuma-api
https://github.com/MedAziz11/Uptime-Kuma-Web-API
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Dec 25, 2024):
implementing a stable, externally facing http API instead of the internal socket.io API is tracked here:
Closing as a duplicate