Question about API and Group creation (and monitor assignment)

[kristiandg]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Good morning. We're trying to set something up where, when a new project is spun up, the collection of monitors for that project are all created via API, and placed in a group for the project name. That way, when the project is spun down, or anyone working on the project needs to view those monitors, they can find their collection of monitors in the same place.

However, in the API documentation, I don't see the option for creating/editing a monitor type of "group" (which I would have expected). Additionally, when creating an actual monitor (such as, a ping), I don't see a key for "group membership" or something like that to place the monitor in the group.

Can someone shed some light on this, by chance?

Thank you.

📝 Error Message(s) or Log

n/a - API question, not a bug

🐻 Uptime-Kuma Version

1.23.1

💻 Operating System and Arch

n/a - API question, not reporting a bug

🌐 Browser

Various

🐋 Docker Version

n/a - API question, not a bug

🟩 NodeJS Version

n/a - API question, not a bug

[CommanderStorm]

To answer your question (if future people come across this issue):

• we currently don't offfer an api, see API functionality #118
• Current planned approach to resolve this is Document the Socket.io API and try to convert it to a HTTP request #3854
• There is third party tooling out there which wrapps around our websocket endpoints to create a http api like https://uptime-kuma-api.readthedocs.io/en/latest/

[kristiandg]

Thanks. I was confused because I saw within Kuma the API Key section, and on badges (the base URL including "/api/", which threw me.