Add integration test for webhook list returning empty array when creator has no webhooks

[Chucks1093]

Summary

GET /creators/:id/webhooks should return an empty array for a creator with no registered webhooks rather than a 404.

Scope

• Register a creator but do not register any webhooks
• Call GET /creators/:id/webhooks with valid creator auth
• Assert response is 200 with an empty array

Acceptance Criteria

• Returns 200 with empty array for creator with no webhooks
• Does not return 404

ETA: 12 hours

---

Coordinate on Telegram

[Okorie2000-code]

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

Hi maintainer, can I work on this?

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

[Arome8240]

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

Hello, I'm a smart contract and full stack developer, open for contributions. contributed to over 20 project on OnlyDust and Drips , with expertise in Solidity, Cairo, JavaScript, TypeScript, and RUST. I am passionate about building secure and scalable blockchain solutions, and I would love the opportunity to contribute my skills toward solving this issue.

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

[teethaking]

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

Hey maintainer! I'd love to take on this issue and write the integration test to ensure the webhook list endpoint handles creators without webhooks correctly.
Here is how I plan to implement it:

1. Set Up the Test Scenario

I will write an integration test that performs the following setup:

• Create and register a brand-new creator in the database.
• Authenticate as this creator to get a valid authorization token.
• Intentionally leave the creator's webhook configuration completely empty.

2. Implement Assertions (Acceptance Criteria)

I will make a request to GET /creators/:id/webhooks using the valid auth token and verify the API meets the acceptance criteria:

• Status Code: Assert that the response returns a 200 OK (ensuring it doesn't mistakenly throw a 404 Not Found).
• Response Body: Assert that the returned data payload is a valid, empty array [].

3. Maintain Test Isolation

I will ensure the test runs in isolation using standard teardown hooks so that existing seed data or webhooks from other test suites don't leak into this scenario.
I can get this implemented and submitted quickly. Please feel free to assign this issue to me!

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

[GEEKYFOCUS]

3. Hi, after reviewing the relevant code paths, I have a clear strategy for implementing the fix and validating it through automated tests. Please consider assigning this issue to me sire. Bless me with this task and the lord shall bless you more . I can PR within 5hrs, thanks in addvance

[sulaimonifeoluwa4-blip]

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

Hi can I work on this

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

[CodingAngel1]

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

Hello,

Please Can I take this? Assigning me would give me the privilege of contributing to your awesome project.

I’ll reproduce it, ship a minimal fix with tests, and update the PR within 12h of being assigned.

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

[grantfox-oss]

🦊 GrantFox — @CodingAngel1 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 #551)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

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

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