Submit a BM transactional template for Viber moderation.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Query parameter senderInfoTrackingId (required) identifies the Viber sender. Routee resolves the sender's Viber service id from this tracking id.
For business rules (OTP {{pin}} requirement, moderation, content limits), see the customer guide.
Moderation lifecycle callback
Optional callbackUrl on create registers an HTTPS endpoint for moderation status changes (PENDING_MODERATION, APPROVED, REJECTED). This payload is not the same as delivery callbacks on send — see Update Viber transactional template lifecycle callback.
Optional moderationNotifyEmail triggers Routee email notifications when the template lifecycle changes.
Response fields
| KEY | DESCRIPTION |
|---|---|
id | Template id assigned by Viber |
serviceId | Viber business / service id |
category | OTP or Transactional |
status | Moderation status (e.g. PENDING_MODERATION) |
statusNote | Moderation note when available |
params, locales, varExample | Echo of submitted template definition |
callbackUrl | Stored Routee lifecycle webhook URL, if set |
Validation error
Missing or invalid OAuth token, or insufficient Viber permission
Account or resource not found