Add structured log for creator trade webhook registration with creator ID and event types

[Chucks1093]

Summary

When a creator successfully registers a trade webhook, the server should emit an info-level structured log so webhook registrations are observable in the server logs without querying the database.

Scope

• Emit a structured info log on successful webhook registration with fields: creator_id, webhook_id, event_types, registered_at
• Emit a structured info log on webhook deletion with fields: creator_id, webhook_id, deleted_at
• Do not log the callback URL (use the masking helper)

Acceptance Criteria

• Registration log emitted with correct fields on success
• Deletion log emitted on webhook removal
• Callback URL is not present in any log output

ETA: 12 hours

---

Coordinate on Telegram

[umohjosephemmanuel-cyber]

Enhanced webhook observability by implementing structured logging for webhook registration and deletion events, capturing key metadata while protecting sensitive information through URL masking and secure logging practices.

[Mhidesav]

i would like to be assigned this issue please

[xJeffx23]

Hello!

My name is Jefferson, and I have been contributing to open-source projects for over a year. I have participated in multiple hackathons and have experience working with backend services, structured logging, and API-driven applications.

I would like to work on this issue because webhook registration and deletion are important operational events that should be observable in server logs without requiring a database lookup. Adding structured info-level logs would improve debugging and auditability while keeping sensitive callback URLs out of log output.

My plan would be to locate the webhook registration and deletion handlers, add structured info logs with creator_id, webhook_id, event_types, and timestamps where appropriate, and ensure the callback URL is never logged directly by using the existing masking helper or avoiding that field entirely. I would also verify the log output against the acceptance criteria.

I would greatly appreciate the opportunity to contribute to the project. Thank you for your time and consideration!

[CollinsKRO]

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

Good Day maintainer, pls assign me this issue. I'd love to work on it. Thanks.

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

[chinelo002]

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

Hi, my name is chinelo002, and I am a fullstack and smart contract developer skilled in React, Next.js, JavaScript, TypeScript, Tailwind CSS, and Soroban. For this task, I will:

1. Add structured info-level logging to the successful trade webhook registration flow, capturing creator_id, webhook_id, event_types, and registered_at in a consistent, queryable format.
2. Implement structured deletion logging for webhook removals, ensuring creator_id, webhook_id, and deleted_at are emitted whenever a webhook is successfully deleted.
3. Integrate the existing masking helper and verify that callback URLs are excluded from all log payloads to prevent sensitive endpoint exposure.
4. Add unit tests validating registration and deletion log emission, field correctness, and confirming that callback URLs never appear in logged output.

ETA: 10 hours

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

[Maximum-Prosper]

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

Hi maintainer.
I'd like to work on this project.
Please kindly assign.

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

[drips-wave]

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

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