Add integration test for alert registration returning 400 for invalid Stellar wallet address

[Chucks1093]

Summary

The price alert registration endpoint accepts a wallet_address field that must be a valid Stellar address. An integration test should confirm that a malformed address is rejected before any database write occurs.

Scope

• POST to /alerts with a wallet address that is not a valid Stellar format
• Assert response is 400 with a descriptive validation error
• Assert no alert record was created in the database

Acceptance Criteria

• Returns 400 for malformed wallet address
• Error body identifies the wallet_address field
• No alert record created after the failed request

ETA: 12 hours

---

Coordinate on Telegram

[dorisadams]

I would love to work on this issue, please assign the issues to me so i Can work on it ASAP

[sudo-robi]

@sudo-robi has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer I'm a full stack developer and smart contract developer let me help you resolve this issue and I assure you it will be thoroughly done neatly as I have seen my way around the issue.

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

[exronnin]

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

I would love to resolve this issue, I have experience building contracts and fullstack applications.

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

[10xwhoman]

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

Hello i would love to work on this.

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

[Danto1606]

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

I would like to work on this

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

[villadel]

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

i would like to work on this issue

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

[drips-wave]

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

🧑‍💻 @villadel: 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 @villadel as part of the Stellar Wave Program's 6th Wave 🥳

😎 @villadel: 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.