Webhooks
Register event receivers, save signing secrets, and inspect delivery logs.
Webhooks send selected organization events to a receiver operated by your team. Open Webhooks in the bottom dock. Your developer can use the webhook integration guide and signature-verification example.
Before you begin
Section titled “Before you begin”Use an Owner or Finance role. Have your developer prepare an HTTPS receiver and a secure place for its signing secret.
Register an endpoint
Section titled “Register an endpoint”- Add the receiver
Click Add Webhook and enter the receiver’s HTTPS address in URL. Use an address controlled by your organization, such as
https://api.example.com/koneth/events. - Choose events
Select at least one event under Events. Choose only the events your application needs.
- Choose which servers deliver
Leave Applies to on All servers to receive events from every server in your organization, or pick one server to receive events from that server only. You can see the target in the Applies to column afterwards.
- Create and save the signing secret
Click Create. In Webhook Signing Secret, use Reveal secret and Copy. Store it securely, then click I have saved this secret.
- Verify the endpoint
Click Verify on the endpoint row. Koneth sends a challenge to your URL and the endpoint turns Active only when your receiver replies with that same challenge value. Your developer can read the exact request and response in the webhook integration guide.
The signing secret belongs in the receiver’s protected configuration. Do not use it as a Management API key or share it with traders.
Available events
Section titled “Available events”| Event | Availability |
|---|---|
position.opened |
Sent when a filled order creates a position. |
position.closed |
Sent when a position is fully closed. |
position.reduced |
Sent when a position is partially closed and the rest stays open. |
finance.transaction.completed |
Sent when a deposit or withdrawal is completed. |
account.metrics.updated |
Sent when an account metric batch arrives for the account. |
Selecting an event subscribes the endpoint to that event type; it does not itself generate a delivery.
For continuous monitoring while positions are open, your developer can use Live account metrics.
Check delivery logs
Section titled “Check delivery logs”Find the endpoint row and click Deliveries. The Delivery Log shows event types and delivery statuses.
| Status shown | What to check |
|---|---|
| Success | Confirm your receiver accepted and processed the event as expected. |
| Failed | Investigate receiver availability and logs. Contact support if the state is unclear. |
| Dead letter | Delivery has stopped retrying. Ask your developer and Koneth contact to investigate. |
An empty log is not proof that the receiver is working. Check activation, event selection, and whether a relevant event has occurred. The dialog shows a limited recent history, not a complete delivery archive.
Manage an existing endpoint
Section titled “Manage an existing endpoint”Verify activates a pending endpoint and Disable stops an active one from receiving events — both are available on the endpoint row. Contact Koneth support if you need to rotate the signing secret, replace an endpoint, or redeliver a specific delivery. Do not create duplicate endpoints as a substitute for managing an existing one.