What webhook notifications are

Webhook notification is a mechanism where the system actively sends event information.

Unlike an institution actively calling APIs to query data, webhook notifications are sent by Finger Manager to the institution server after an event occurs.

A typical flow is: Finger Manager business event -> system triggers callback -> sends event data to institution Callback URL -> institution server receives it -> institution executes follow-up business logic.

This reduces the need for institutions to continuously poll APIs and improves data synchronization efficiency between systems.

Supported use cases

Webhook notifications can be used for user registration completion, KYC / KYB status changes, order creation, order status changes, execution notifications, position changes, deposit status changes, withdrawal status changes, account status changes, risk events, system notifications, subscription status changes, and custom business events.

The available callback events depend on the Finger Manager modules and system configuration enabled for the institution.

Callback URL

The institution can configure the server address used to receive callback data in Finger Manager.

For example: https://api.example.com/finger/callback.

When a selected event occurs, Finger Manager sends the corresponding event data to that address.

HTTPS is recommended to protect data in transit.

Callback payload

Callback payloads usually include Event Type, Event ID, Organization ID, User ID, business object ID, event time, current status, related business data, request signature, and other extended fields.

Different event types may contain different fields.

The institution can use Event Type to determine the event category and execute the corresponding business logic.

Security verification

To prevent unauthorized requests, institutions can verify callback requests.

Depending on the integration method, verification can use API Secret, Signature, Timestamp, Token, IP whitelist, and HTTPS.

After receiving a callback, the institution should verify request source and signature information before processing business logic.

Callback failure and retry

If the institution server cannot receive callbacks normally, for example because the server is unavailable, the request times out, an error status code is returned, or a network exception occurs, the system can retry or record the failure according to the callback mechanism.

The institution should keep the Callback URL available and return correct HTTP status codes.

Difference from API

API and webhook notifications solve different integration scenarios.

API means the institution actively requests Finger Manager to retrieve or submit data.

Webhook notification means Finger Manager actively sends data to the institution system after an event occurs.

In real integrations, API and webhooks are often used together. For example, API can query order details while webhook notification tells the institution in real time that order status has changed.

Examples

When a user submits an order in Finger Trader, Finger Manager receives the order, creates an order event, sends a callback to the institution server, and the institution system can then perform risk checks, order processing, or other business logic.

When a user's KYC status changes, Finger Manager can trigger a callback so the institution system receives the status change and updates customer profile or account permissions automatically.

Notes

Webhook notifications are mainly used for real-time system integration between Finger Manager and institution-owned systems.

The institution can decide which events to receive, which server receives callbacks, what business logic to execute after receiving events, and whether to forward events to other internal or third-party systems.

Through webhook notifications, Finger Manager can fit more easily into the institution's existing technical infrastructure without changing its core system architecture.