Skip to content
WeZend

Channels

In-app inbox

A persistent message center inside your own product — messages that wait for the user instead of interrupting them.

Not every message deserves an interruption. The in-app inbox is a message center you embed in your own web app — announcements, feature news and account notices land there and wait until the user logs in.

Why an inbox channel

  • Zero fatigue — it never buzzes a phone. Perfect for "nice to know" content that would hurt your push opt-in rate.
  • Guaranteed reach — no spam filter, no notification permission needed; every active user sees it.
  • A journey step like any other — journeys can deliver to inapp exactly like SMS or email, so "announce in-app, escalate to email if unread after 3 days" is a standard pattern.

Embedding

Fetch messages for the signed-in user from your backend and render them in your own UI:

curl "https://api.wezend.com/v1/inapp/messages?contact_id=c_123" \
  -H "X-API-Key: $WEZEND_API_KEY"

Mark read state back so unread badges stay correct:

curl -X POST https://api.wezend.com/v1/inapp/messages/msg_456/read \
  -H "X-API-Key: $WEZEND_API_KEY"

Sending

Use the universal endpoint with "channel": "inapp", or add an in-app step in a journey. Messages support Markdown, a call-to-action URL and an expiry date (after which they disappear from the inbox on their own).

One platform. Every customer interaction.

Replace your patchwork of messaging APIs, CDP and automation tools with a single engagement platform built for scale.

No credit card required · EU data residency · 99.99% uptime SLA