Step 3: create a webhook
Let’s try creating a webhook. For this, you can choose to use either the webhook event type’s name or its ID. Below are two examples showing how webhook scope works depending on whether you includeaccountId.
Example A: Global webhook (no accountId)
A global webhook fires across all accounts in your multi-account configuration. This is required for onboarding event types such as AccountActivated, IdentityVerificationRequest, KycInformationRequested, KybInformationRequested, ApplicationStatusUpdated, and AccountStatusUpdated.
201 response.
Example B: Account-specific webhook (with accountId)
Include accountId to create a webhook scoped to a specific account. This is suitable for non-onboarding event types such as BoxDebited, BoxCredited, CardTransaction, and others where the account already exists.
201 response.