mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
API endpoint for general information (version, etc.) #2537
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#2537
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 @solick on GitHub (Sep 1, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
API
🔖 Feature description
An API Endpoint /api/version where the current version is returned
An API Endpoint /api/info where general information about the instance are returned (amount of monitors, groups etc.)
✔️ Solution
Implement both API endpoints
❓ Alternatives
No response
📝 Additional Context
No response
@solick commented on GitHub (Sep 3, 2023):
I would implement it on my own an create a PR if we agree on the details. Lets discuss
@CommanderStorm commented on GitHub (Sep 3, 2023):
Please note that most public API development is currently blocked by https://github.com/louislam/uptime-kuma/issues/118 and the associated PR.
If you'd like to contribute, this would be the area in which work may be needed before this.
@solick commented on GitHub (Sep 3, 2023):
@CommanderStorm thanks for hinting me to this ticket. I tried to understand what exactly is the state of this feature and where I could help but to be honest it's quite hard to understand. There seems to be a lot ongoing but I cannot identify work packages where I could be of help. Is there a sort of project planning on this feature?