404 when trying to use the API #2055

Closed
opened 2026-02-28 02:41:35 -05:00 by deekerman · 6 comments
Owner

Originally created by @corybohon on GitHub (Mar 29, 2023).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I'm trying to access the API in my Uptime Kuma installation to update the hostname for a particular monitor, however, whenever I try to use the PUT /api/v1/monitors/[id] endpoint, I get a text error that it Cannot PUT /api/v1/monitors/1. I've attached the image of the request below.

Questions:

  • Do I need to do anything beyond creating an API key to use the API?
  • Does the Authorization header just need to include Authorization: [KEY HERE]?

I appreciate any help in getting this working! This project is amazing and so happy that I found it!

CleanShot 2023-03-29 at 20 17 30@2x

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.21.1

💻 Operating System and Arch

Ubuntu 20.04.6 LTS

🌐 Browser

Safari 16.3

🐋 Docker Version

No response

🟩 NodeJS Version

v14.21.3

Originally created by @corybohon on GitHub (Mar 29, 2023). ### ⚠️ 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 I'm trying to access the API in my Uptime Kuma installation to update the hostname for a particular monitor, however, whenever I try to use the `PUT /api/v1/monitors/[id]` endpoint, I get a text error that it `Cannot PUT /api/v1/monitors/1`. I've attached the image of the request below. Questions: - Do I need to do anything beyond creating an API key to use the API? - Does the Authorization header just need to include `Authorization: [KEY HERE]`? I appreciate any help in getting this working! This project is amazing and so happy that I found it! ![CleanShot 2023-03-29 at 20 17 30@2x](https://user-images.githubusercontent.com/246933/228696586-d9ce4a4f-316a-4ac4-a876-26ae07f176c2.jpeg) ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version 1.21.1 ### 💻 Operating System and Arch Ubuntu 20.04.6 LTS ### 🌐 Browser Safari 16.3 ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version v14.21.3
deekerman 2026-02-28 02:41:35 -05:00
  • closed this issue
  • added the
    Stale
    help
    labels
Author
Owner

@louislam commented on GitHub (Mar 30, 2023):

No such API endpoint.

PUT /api/v1/monitors/[id] where did you see this?

@louislam commented on GitHub (Mar 30, 2023): No such API endpoint. `PUT /api/v1/monitors/[id]` where did you see this?
Author
Owner

@corybohon commented on GitHub (Mar 30, 2023):

I found it on an article online, but now I cannot find the link to it. Is there a list of official API documentation somewhere that I can look at?

@corybohon commented on GitHub (Mar 30, 2023): I found it on an article online, but now I cannot find the link to it. Is there a list of official API documentation somewhere that I can look at?
Author
Owner

@Computroniks commented on GitHub (Mar 31, 2023):

Currently there is no public API. See #118 for more details on proposed functionality. With regards to the API key, this is only for the prometheus endpoint and makes use of basic authentication with an empty username field. I.e. An authorization header with the following in base64 encoding :<api key>. Note that the : is required to indicate an empty username field.

@Computroniks commented on GitHub (Mar 31, 2023): Currently there is no public API. See #118 for more details on proposed functionality. With regards to the API key, this is only for the prometheus endpoint and makes use of basic authentication with an empty username field. I.e. An authorization header with the following in base64 encoding `:<api key>`. Note that the `:` is required to indicate an empty username field.
Author
Owner

@CommanderStorm commented on GitHub (May 24, 2023):

@corybohon Is this issue resolved?

@CommanderStorm commented on GitHub (May 24, 2023): @corybohon Is this issue resolved?
Author
Owner

@github-actions[bot] commented on GitHub (Aug 22, 2023):

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 (Aug 22, 2023): 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 (Aug 24, 2023):

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

@github-actions[bot] commented on GitHub (Aug 24, 2023): 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#2055
No description provided.