Add integration test for creator detail returning 404 with correct error shape

[Chucks1093]

Summary

GET /creators/:id must return a 404 with a consistent error shape when the creator does not exist. An integration test should confirm both the status code and the response body structure.

Scope

• Call GET /creators/:id with a creator ID that does not exist
• Assert response status is 404
• Assert response body matches the standard error shape: { error: { code, message } }
• Assert code is a recognizable not-found code string

Acceptance Criteria

• Returns 404 for non-existent creator
• Response body matches standard error shape
• code field is present and descriptive

ETA: 12 hours

---

Coordinate on Telegram

[Silver36-ship-it]

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

I would love to work on this professionally, please assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Silver36-ship-it to this issue.

[Vicsygold]

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

Hi Maintainer, Please can I have this project I will resolve it immediately. Thanks in advance!

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

[graceshaba93]

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

Hello maintainer, I can fix this issue.

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

[chiscookeke11]

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

Hi
let me take care of this ASAP

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

[grantfox-oss]

🦊 GrantFox — @chiscookeke11 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #553)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@chiscookeke11's PR #565 was approved and merged by @Chucks1093.

🏆 @chiscookeke11: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (296 total points). Track your full progress on GrantFox.

👏 Great work, @chiscookeke11! Keep contributing to accesslayerorg.

[drips-wave]

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

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