API docs/example to create new check/monitor via API #746

Closed
opened 2026-02-28 01:56:32 -05:00 by deekerman · 3 comments
Owner

Originally created by @codeagencybe on GitHub (Jan 12, 2022).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Is there any example or docs available where I can use the uptime Kuma API to create a new check/monitor programmatically?
I would like to automatically create a new check/monitor after I spin up a new application and sent an HTTP request to uptime kuma API backend.
But I can't find anything related to read up on this and give it a try.

Thanks.

🐻 Uptime-Kuma Version

1.11.3

💻 Operating System and Arch

not relevant to question

🌐 Browser

not relevant to question

🐋 Docker Version

not relevant to question

🟩 NodeJS Version

not relevant to question

Originally created by @codeagencybe on GitHub (Jan 12, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem Is there any example or docs available where I can use the uptime Kuma API to create a new check/monitor programmatically? I would like to automatically create a new check/monitor after I spin up a new application and sent an HTTP request to uptime kuma API backend. But I can't find anything related to read up on this and give it a try. Thanks. ### 🐻 Uptime-Kuma Version 1.11.3 ### 💻 Operating System and Arch not relevant to question ### 🌐 Browser not relevant to question ### 🐋 Docker Version not relevant to question ### 🟩 NodeJS Version not relevant to question
deekerman 2026-02-28 01:56:32 -05:00
  • closed this issue
  • added the
    Stale
    help
    labels
Author
Owner

@chakflying commented on GitHub (Jan 12, 2022):

Ref #118, API for monitors is not supported yet.

@chakflying commented on GitHub (Jan 12, 2022): Ref #118, API for monitors is not supported yet.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 23, 2022):

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions[bot] commented on GitHub (Sep 23, 2022): We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 25, 2022):

This issue was closed because it has been stalled for 2 days with no activity.

@github-actions[bot] commented on GitHub (Sep 25, 2022): This issue was closed because it has been stalled for 2 days with no activity.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#746
No description provided.