Fast path
Use without an account
Run the Doctor command, keep the terminal open, paste the generated provider callback URL into the service you are testing.
Callback workbench
Generate a callback URL, forward it locally, and inspect every attempt.
Use the CLI for local forwarding. Use the browser workbench when you need to create a session, inspect URLs, or queue sample STK callbacks manually.
Install and run
CLI-first workflow
npx callbackdesk doctor http://localhost:3000/api/mpesa/callback
- No-account mode
- anonymous session
- Account mode
- project token
- Callback URL
- /c/...
- Inbox URL
- /s/...
Team path
Create an account
Sign in when you need persistent projects, longer retention, project-scoped CLI tokens, and revocation.
Evidence path
Inspect and replay
Open the session inbox to view redacted payloads, status codes, delivery attempts, and replay commands.
1
Run Doctor
The CLI creates a session and starts forwarding captured callbacks to localhost.
2
Paste provider URL
Use the generated /c/... URL in the provider callback setting or request body.
3
Replay evidence
Fix the handler, replay the same event, and keep an audit trail of attempts.
Browser session
Manual callback workbench
Use this when you want to generate callback and inbox URLs from the browser. For local forwarding, the terminal Doctor command remains the main path.
- API base
- https://api.loremipsum.co.ke
- Callback base
- https://api.loremipsum.co.ke
- Session API
- POST /doctor/v1/sessions
- Public paths
- /c/... and /s/...
No active browser session
Start a session to generate the callback and inbox URLs.
System
Runtime status
- Health
- checking
- Ready
- checking
- Store
- checking
- Version
- checking
Real callbacks
Provider POSTs are captured on the hosted /c/... endpoint.
Sample events
STK samples are local test payloads, separate from live provider traffic.