Add integration test for webhook endpoint returning 404 when webhook ID does not exist

[Chucks1093]

Summary

The webhook detail, update, and delete endpoints should return 404 when the requested webhook ID does not exist rather than a generic 500. An integration test should call each endpoint with a non-existent ID and confirm the 404 response and error shape.

Scope

• Call GET, PATCH, and DELETE for a webhook ID that does not exist in the database
• Assert each returns status 404
• Assert each response body contains an error field with a descriptive message identifying the resource as not found
• Assert the message does not leak internal details such as table names or SQL errors

Acceptance Criteria

• GET non-existent webhook returns 404
• PATCH non-existent webhook returns 404
• DELETE non-existent webhook returns 404
• All three error bodies contain a descriptive error field
• No internal details in any error message

ETA: 12 hours

---

Coordinate on Telegram

[akinboyewaSamson]

Hi Maintainer,

I would love to be assigned to this issue.

I’m a Full-Stack Developer and I also actively explore blockchain development and smart contracts, which has strengthened my problem-solving skills and attention to code quality.

After reviewing the issue, I believe I can contribute effectively and deliver a well-tested solution within the expected standards of the project.

ETA: 6 hours

Thank you for your consideration.

[ZeePearl56]

@ZeePearl56 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ZeePearl56 to this issue.

[abrcrmb]

@abrcrmb has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

pls assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abrcrmb to this issue.

[abimbolaalabi]

@abimbolaalabi has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer! I’m interested in contributing to this task and can ensure timely delivery with clean implementation. I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it. Thank You

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abimbolaalabi to this issue.

[drips-wave]

Congratulations, @abrcrmb! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @abrcrmb: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @abrcrmb as part of the Stellar Wave Program's 7th Wave 🥳

😎 @abrcrmb: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.