Register, or replace, the URL that Framnex uses for webhook deliveries:Register the webhook URLConfigure the webhook URL separately for each environment.
Webhook events report asynchronous changes. Your integration should use the event payload and related resource identifiers to update its own state.The generated schemas include payloads for onboarding, account, credential, incoming-transfer, exchange-transfer, and outgoing-transfer events. Use the current schema reference when implementing event handling.
Keep your internal logs correlated with the Framnex resource identifiers so a failed business flow can be traced from the resource to its webhook delivery.
Framnex exposes an operation to re-queue a failed webhook delivery:Retry a failed webhook deliveryUse retry for failed deliveries after you have corrected the receiving-side issue. Do not use it as a substitute for fixing repeated processing failures in your integration.
