Developer Tools

Everything you need to build, test, debug, and monitor your Wajub integration — webhooks, CLI, Konsole, and the sandbox environment.

2 min read

Developer Tools are the infrastructure layer around your integration: receive real-time events, develop locally, observe every request, and validate your integration before going live. This page covers the four tools that live under /developer-tools. SDKs and Plugins are part of the same "build and debug" cluster in the sidebar but are documented under Libraries instead, since they're organized by language/platform, not by tool.

WebhooksReceive real-time signed events for every state change — the source of truth for asynchronous operations.CLIForward webhooks to localhost, trigger test events, and interact with the API from your terminal.KonsoleReal-time API debugger — inspect every request, replay webhooks, and observe routing decisions.Testing & SandboxSimulate payments, test every scenario, and validate your integration before production.SDKs & LibrariesOfficial server, browser, and mobile packages — documented under Libraries.Plugins & E-commerceWordPress, WooCommerce, and no-code integrations — documented under Libraries.

When to use each tool

Scenario	Tool
Receive payment status updates reliably	Webhooks
Test webhooks without deploying	CLI (`wajub listen`)
Debug a failing API call after the fact	Konsole → API Logs
Watch routing decisions in real time	Konsole → Routing Log
Simulate a declined or timed-out payment	Testing → Test scenarios
Validate your full integration pre-production	Testing → Sandbox mode

Start with Webhooks

Before any other tool, set up webhooks. They are the only reliable signal for asynchronous operations (Mobile Money confirmation, transfer completion). Everything else — Konsole, CLI, Testing — accelerates development once webhooks are working.

Was this page helpful?

Edit this page on GitHub

Need help?

Troubleshooting Contact support GitHub Discussions Service Status