What's the OneUptime API path on self-hosted version? #350

Closed
opened 2026-04-05 16:19:26 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jose-yougov on 10/20/2025

Hello!

We are running a self-hosted OneUptime deployed with Helm and we are now exploring the OneUptime API capabilities.

In the one hand, we are fine when using the status page public API, which works fine for us (e.g.: curl -X POST https://status-portal.my-company-internal-domain.net/status-page-api/overview/3094d3d7-6ca5-4c24-aa20-1eb7a7c05790

But in the other hand, if we try to access the OneUptime API to list or manage entities like monitors, for example, we are not able to do so by using the /api/<path> as specified in the documentation. For example, to list the monitors as we can infer from the documentation https://oneuptime.com/reference/authentication (API Authentication) and https://oneuptime.com/reference/pagination (API pagination example), if we do:

curl --header "ApiKey: my-api-key-value-123" "https://status-portal.my-company-internal-domain.net/api/monitors/get-list?skip=0&limit=3"

we get this 404 response:

{"message":"Page not found - /api/monitors/get-list?skip=0&limit=3"}

The API key is created for a project called IP and the API key has Project Owner permission.

Is there something we are missing?

Thanks for your help!

*Originally created by @jose-yougov on 10/20/2025* Hello! We are running a self-hosted OneUptime deployed with Helm and we are now exploring the OneUptime API capabilities. In the one hand, we are fine when using the status page public API, which works fine for us (e.g.: curl -X POST https://status-portal.my-company-internal-domain.net/status-page-api/overview/3094d3d7-6ca5-4c24-aa20-1eb7a7c05790 But in the other hand, if we try to access the OneUptime API to list or manage entities like monitors, for example, we are not able to do so by using the `/api/<path>` as specified in the documentation. For example, to list the monitors as we can infer from the documentation https://oneuptime.com/reference/authentication (API Authentication) and https://oneuptime.com/reference/pagination (API pagination example), if we do: `curl --header "ApiKey: my-api-key-value-123" "https://status-portal.my-company-internal-domain.net/api/monitors/get-list?skip=0&limit=3"` we get this 404 response: `{"message":"Page not found - /api/monitors/get-list?skip=0&limit=3"}` The API key is created for a project called IP and the API key has Project Owner permission. Is there something we are missing? Thanks for your help!
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#350