Create an API that accept monitor name/id and generate PDF report #2826

New issue

Closed

opened 2026-02-28 03:08:33 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 03:08:33 -05:00

Owner

Originally created by @qburst-justinjoseph on GitHub (Nov 21, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

API

🔖 Feature description

The Api should accept monitor id or monitor name and create a custom report for that alarm for the specified period (7 days upto 30 days). By using CURL request the end user can download the generated PDF file.

✔️ Solution

Create a node js API, that can use internally with CURL. This API endpoint can be used to download the generated PDF file to the system.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @qburst-justinjoseph on GitHub (Nov 21, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type API ### 🔖 Feature description The Api should accept monitor id or monitor name and create a custom report for that alarm for the specified period (7 days upto 30 days). By using CURL request the end user can download the generated PDF file. ### ✔️ Solution Create a node js API, that can use internally with CURL. This API endpoint can be used to download the generated PDF file to the system. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:08:33 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 03:08:37 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Nov 21, 2023):

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2028 #366 #118
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

Note that our contribution guide can be found here and that we are open to contributions if you adhere to this

@CommanderStorm commented on GitHub (Nov 21, 2023): I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2028 #366 #118 If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^ Note that [our contribution guide can be found here](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md) and that we are open to contributions if you adhere to this

deekerman commented

2026-02-28 03:08:38 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 1, 2023):

We are consolidating our duplicate issues a bit.
This issue will be tracked in

If you think that these issues don't cover what you meant, please reach out ^^

@CommanderStorm commented on GitHub (Dec 1, 2023): We are consolidating our duplicate issues a bit. This issue will be tracked in - https://github.com/louislam/uptime-kuma/issues/366 - https://github.com/louislam/uptime-kuma/issues/1101 - https://github.com/louislam/uptime-kuma/issues/118 If you think that these issues don't cover what you meant, please reach out ^^