Use this command to test the functionality of your webhook endpoint by triggering a test webhook event. The test event will be sent to all the webhook endpoints you have registered on Cobo Portal. You can optionally provide theDocumentation Index
Fetch the complete documentation index at: https://cobo.com/developers/llms.txt
Use this file to discover all available pages before exploring further.
override_data option to customize the payload.
Usage
Arguments
<event_type>: The webhook event type you want to trigger. Possible values include:
wallets.transaction.createdwallets.transaction.updatedwallets.transaction.failedwallets.transaction.succeededwallets.mpc.tss_request.createdwallets.mpc.tss_request.updatedwallets.mpc.tss_request.failedwallets.mpc.tss_request.succeeded
You can also run the cobo webhook events command to get the latest list of all available event types.
Options
--override <json_string>: Override specific fields in the event payload with the provided JSON string.
Example
This command triggers awallets.transaction.updated event with the specified chain_id and amount values:
Best Practices
- Test all event types: Trigger events for all the webhook types your application is subscribed to, ensuring your system can handle each type correctly.
- Use realistic data: When overriding event data, try to use realistic values that match your production scenarios.
- Test error handling: Trigger events with edge case data to ensure your webhook consumer can handle unexpected scenarios.
- Verify webhook delivery: After triggering an event, check your webhook endpoint logs to confirm that the event was received and processed correctly.
