Overview

Documentation for MorisBox partners integrating multi-channel messaging (in-app, WhatsApp, and SMS) with their own brand, templates, bots, and conversations.

This site covers the Partner API (sk_…).
For developer accounts that use MorisBox templates only, see Developer Docs.

Get started

You are…	Start with…
A partner enabled in the sandbox	Quickstart → Partner Hub key → `POST /messages`
Exploring the available surfaces	Platforms
A developer without a partner brand	docs.morisbox.com/developers

Other useful entry points:

Authentication - sk_… keys
API Overview - base URL and endpoint groups
Security and Compliance - DLP, PoD, and DSAR
Sandbox - public hosts

Who it is for

Profile	MorisBox usage
Institutions	OTPs, notifications, forms, and newsletters
SaaS / businesses	Multi-channel messaging inside an existing product
Partners	Custom brand and templates, bots, and support conversations

How it works

MorisBox is centered on the phone number. A REST call is routed to in-app, WhatsApp, or SMS, with intelligent fallback.

Partner journey

MorisBox grants sandbox access → Partner Hub
Create your own API keys
Link users (OTP and organization fields)
Send and automate text, media, HTML, flows, and more
Configure webhooks, bots, and compliance

Message destinations

Destination	Use case
Partner hub / inbox	Notifications, media, newsletters, and flow cards
Support conversations	Opened by the end user
Fallback channels	WhatsApp / SMS when in-app is unavailable (OTPs and alerts)