Configure an Event Destination

Event destinations are configured per Sakneen organization in the Developer Console. You must be signed in with an account that has access to the organization and the required integration permissions.

1. Create an application

1. Open Developer Console from the Sakneen navigation.
2. Open Applications.
3. Select Create application.
4. Enter a name that identifies the connected system, such as DAZU Collections.

An organization can have multiple applications. Use separate applications when integrations have different owners or operational boundaries.

2. Add an event destination

Open the application and add an event destination with:

Setting	Description
Destination name	A unique name inside the application
Endpoint URL	The public HTTPS URL that receives webhook POST requests
Event subscriptions	The exact event types this destination receives

Production endpoints must:

• use HTTPS;
• resolve to public IP addresses;
• accept POST requests with Content-Type: application/json;
• respond within 10 seconds; and
• not include URL credentials or a fragment.

Localhost, private network addresses, link-local addresses, and cloud metadata hosts are rejected.

3. Store the signing secret

Sakneen generates a destination-specific signing secret when the destination is created. It has the following format:

whsec_...

Copy the secret immediately and store it in your server-side secret manager. The complete secret is not shown again. Never put it in frontend code, source control, logs, or support messages.

Every destination has its own secret. Do not reuse a secret across destinations or environments.

If the secret is lost or exposed, rotate it from the destination's Signing section and update your receiver immediately. Future deliveries use the new secret.

4. Send a test event

Select Send test event on the destination page. Sakneen creates an integration.test event and delivers it through the same signing, HTTP, attempt-history, and retry flow as production events.

The test confirms:

• Sakneen can resolve and reach the endpoint;
• your receiver accepts the request;
• signature verification is configured correctly; and
• the destination's delivery history is visible.

integration.test is a targeted diagnostic event. It is not a subscription and does not represent a Client or Wallet resource change.

5. Monitor deliveries

The Developer Console provides:

• the exact outbound event JSON;
• delivery status per destination;
• HTTP attempt history;
• sanitized response information;
• automatic retry progress; and
• manual retry for failed deliveries.

Return a 2xx response only after your system has durably accepted the event. See Delivery and retries for the full response behavior.

Destination lifecycle

• Active destinations receive their selected events.
• Suspended destinations receive no new events.
• Updating subscriptions affects only events that occur after the change.
• Deleting a destination stops future delivery to that destination.

Changing a destination does not replay historical events.