Motion 5Book a demo

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

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.

  1. Sign in at Developers (your bank's admins have access) and create a test key. It starts with m5_test_ and is shown once.
  2. 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" }'
  1. 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 }
  1. 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_…)
mode
Nothing is sent on WhatsApp. Codes are always zeros (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_…)
mode
Real WhatsApp messages from your bank's number. Needed for conversations, which are real customers.

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 4567 or 2348031234567. 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

Never put an API key in a mobile app or a web page. Anyone who has it can send codes as your bank. Revoke a leaked key at once in Developers.