Webhook availability

The current product does not provide merchant webhook endpoint configuration, shared secrets, an outbound event catalog, delivery history, or retry tracking. Do not depend on try-on completion, catalog-update, or subscription-change callbacks from Closku.

For a result, keep jobId and poll GET /api/widget/try-on/JOB_UUID?merchantId=MERCHANT_UUID. Read Try-on jobs and status for terminal states.

Closku receives signed subscription and usage-credit events from Polar for its own billing integration and verifies their signature before processing. Extra credits are applied for confirmed paid orders tied to the provider customer and merchant; an order-created event alone does not apply credit. Verified refund events reverse the associated order credits. These incoming events are separate from merchant event delivery and do not require your storefront to create a callback endpoint.

The supported flow is configuration, catalog lookup, session creation, try-on submission, and job polling. Callback URLs, webhook signature headers, delivery deadlines, and retry schedules are not part of that contract.

If your integration needs server notifications, ask Closku about a specifically provisioned solution before depending on it. A future webhook service would need its own versioned event and delivery documentation; this page does not promise a launch date.