feat: Implement a global 404 Not Found route handler

[AlAfiz]

Description

When a user hits an API route that doesn't exist, the server just hangs or returns a generic HTML error. We need a standard JSON response for missing endpoints so the frontend can handle it easily.

Requirements

• Add a catch-all route (app.use('*', ...)) at the very bottom of the route declarations.
• Return a 404 HTTP status.
• Return a simple JSON body: { "error": "Route not found" }.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[AbuJulaybeeb]

@AbuJulaybeeb has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello maintainer,
I would like to take on the implementation of the global 404 Not found route handler issue

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

[Samaro1]

@Samaro1 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

gm gm boss, would really love to be assigned this issue. Will raise a PR in 8 hours tops and would star the repo for continued collab

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

[jemilahshittu247-ctrl]

@jemilahshittu247-ctrl has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello Maintainer,
I’d like to take on Issue #14 – Global 404 Not Found Route Handler for TradeFlow-Core Currently, hitting an invalid API route either hangs the server or returns a generic HTML error, which complicates frontend handling. I propose adding a catch-all route (app.use('*', ...)) at the bottom of all route declarations to return a 404 status with a clear JSON response: { "error": "Route not found" }. This will ensure consistent, predictable API behavior, simplify frontend error handling, and improve overall reliability. I’m ready to implement this immediately and provide clean, tested code.

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

[EA10-lite]

@EA10-lite has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I'd love to work on this issue, my name is Emmanuel. I am a full-stack developer with 4 years of experience building Web and mobile applications.
I can confidently handle this issue. Here is my portfolio and projects I have handled:
https://loveping.net
https://ecohotels.com
https://proposelyai.com
https://www.usememora.xyz
https://360comms.network
https://ea10.vercel.app

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

[Kevin737866]

@Kevin737866 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would love to work on this project, and it would be done correctly and before the deadline

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

[Favourof]

@Favourof has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Ensure the backend responds consistently when a user hits an invalid API route, instead of hanging or returning a generic HTML error.

Proposed Solution:

Add a catch-all route (app.use('*', ...)) at the end of all route definitions.

Return an HTTP 404 Not Found status.

Respond with a JSON body:

{ "error": "Route not found" }

Why it matters:

Provides a predictable response for the frontend.

Improves API usability and error handling.

Prevents server hang or confusing HTML responses for API consumers.

Acceptance Criteria:

Any undefined route returns a 404 JSON response.

Frontend can reliably detect and handle missing routes.

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

[akordavid373]

@akordavid373 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

i will love to apply for this issues

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

[drips-wave]

Congratulations, @Kevin737866! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Kevin737866: 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 issued 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 🌊