Developer docs
Build on Motion 5
Send one-time passwords on WhatsApp, and answer your customers' WhatsApp chats from your own helpdesk. Everything is JSON over HTTPS, authenticated with an API key, with signed webhooks for what happens in between.
What you can build
One-time passwords →
Login, transfer and reset codes delivered on WhatsApp with a Copy code button, checked with one call.
Your own helpdesk →
Get customers who ask for a person in your own support tool, and reply from there with text, photos, documents and voice notes.
Transfers →
Customers send money to any Nigerian bank account from WhatsApp, confirmed with their PIN, over your own rails.
Cards and disputes →
Customers freeze cards and report wrong payments in WhatsApp; you work the disputes in Motion 5 or your own system.
Webhooks →
Signed events to your servers: codes delivered or failed, handoffs requested, customer messages, delivery reports, transfers, disputes and card freezes.
Keys, errors and retries →
API keys, test and live mode, error codes, and Idempotency-Key for safe retries.
Quickstart
Send yourself a test code and check it. Test keys send nothing and cost nothing, so you can build the whole flow before going live.
- Sign in at Developers (your bank's admins have access) and create a test key. It starts with
m5_test_and is shown once. - Send a code to any number:
curl https://motion5.dev/v1/otp/send \
-H "Authorization: Bearer $MOTION5_KEY" \
-H "Content-Type: application/json" \
-d '{ "phone": "08031234567", "purpose": "login" }'- Check the code your customer typed. With a test key the right code is always
000000:
curl https://motion5.dev/v1/otp/verify \
-H "Authorization: Bearer $MOTION5_KEY" \
-H "Content-Type: application/json" \
-d '{ "id": "otp_01JD…", "code": "000000" }'
# { "valid": true }- When it works, create a live key (
m5_live_) and swap it in. Live codes go out from your bank's WhatsApp number once its code template is approved by WhatsApp; we set that up with you.
Test and live mode
Every key is either test or live, and the two never mix: a test key can't see or check a live code, and the other way round.
Test (m5_test_…)000000 for 6 digits) and count as delivered at once. Events are sent with livemode: false. The same limits apply, so you can test those too.Live (m5_live_…)Conventions
- Base URL:
https://motion5.dev/v1. HTTPS only. - Requests and responses are JSON (file uploads are multipart). Field names are snake_case.
- Times are ISO 8601 in UTC, like
2026-11-16T09:30:00.000Z. - IDs carry a prefix that says what they are:
otp_codes,cus_conversations,msg_messages,hnd_handoffs,evt_events. - Phone numbers can be sent as
08031234567,+234 803 123 4567or2348031234567. Codes show them masked (+234803••••567); conversations show them in full (+2348031234567). - New fields can appear in responses and events at any time. Ignore fields you don't know.
Need a hand?
Write to info@guruhub.ng with your key's prefix (never the whole key) and the ID of the code, conversation or event you're asking about.
Keep keys on your servers