July 2026

SMS API: new developer documentation (formerly OptiText)

New: SMS API developer documentation

Published a full guide for integrating a third-party SMS provider with Optimove's
SMS channel through the SMS API (formerly OptiText API). The hub covers
configuration, authentication, and the four integration flows, with dedicated
reference pages for each endpoint.

Impact: SMS aggregators can now build a native integration against a documented,
standardized API. No action required for existing tenants.

Start with the SMS API guide. Reference pages: Handshake Endpoint, Campaign Transmission Webhook, Delivery Report Endpoint, Incoming Messages Webhook, and IP Allowlist.

New: Introduction to SMS

Added a channel-usage guide covering the customer profile attributes required for
SMS/MMS delivery (MOBILE_NUMBER, SMS_CONSENT, SMS_VALID) and how event data
supports real-time triggered campaigns for newly converted users.

Impact: Clarifies attribute requirements for teams setting up SMS campaigns,
especially real-time triggers.

See the Introduction to SMS guide.

Changed: OptiText renamed to SMS

Updated developer documentation to reflect the channel's new name — SMS
(formerly OptiText) — and the SMS API (formerly OptiText API).

Impact: Terminology only; no change to endpoints or payloads.