Once the webhook receiver exists (#25), subscribe to it via Etsy's Webhook Portal / API for the four supported events (order.paid, order.canceled, order.shipped, order.delivered), and wire the resulting signing secret into config the same way EtsyAPIKeystring/EtsyAPISharedSecret are handled today (config/config.go) - e.g. EtsyWebhookSigningSecret, loaded from env, never hardcoded.
Confirm whether subscription happens once per app (single portal-level config) or needs to happen per-connected-shop as part of the OAuth flow in HandleNewAuthCode.
Once the webhook receiver exists (#25), subscribe to it via Etsy's Webhook Portal / API for the four supported events (`order.paid`, `order.canceled`, `order.shipped`, `order.delivered`), and wire the resulting signing secret into config the same way `EtsyAPIKeystring`/`EtsyAPISharedSecret` are handled today (`config/config.go`) - e.g. `EtsyWebhookSigningSecret`, loaded from env, never hardcoded.
Confirm whether subscription happens once per app (single portal-level config) or needs to happen per-connected-shop as part of the OAuth flow in `HandleNewAuthCode`.
angel
added this to the Etsy Integration milestone 2026-08-20 23:30:14 -06:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Once the webhook receiver exists (#25), subscribe to it via Etsy's Webhook Portal / API for the four supported events (
order.paid,order.canceled,order.shipped,order.delivered), and wire the resulting signing secret into config the same wayEtsyAPIKeystring/EtsyAPISharedSecretare handled today (config/config.go) - e.g.EtsyWebhookSigningSecret, loaded from env, never hardcoded.Confirm whether subscription happens once per app (single portal-level config) or needs to happen per-connected-shop as part of the OAuth flow in
HandleNewAuthCode.