Skip to main content
Version: 1.2.0.2 · Published: September 9, 2026 · Published by: Telegent Platform Team
Port In now accepts a number’s messaging, voice, and MMS configuration directly in the submission request. Previously these were applied with a separate POST /v1.0/numbers/update call after the port; they can now be set up front, so a ported-in number arrives already configured. The same release adds inline MMS control to Number Provision and Numbers Update.

​
Enhanced

Port In now accepts the full messaging and voice configuration in the submission request, removing the need for a follow-up Numbers Update call after the port completes:
  • MessageType — a2p or p2p
  • MessageEnabled — enable SMS on the line
  • MmsMessageEnabled — enable MMS on the line (optional; independent of MessageEnabled)
  • MessageRouteId — MRID for message routing (required when SMS or MMS is enabled)
  • VoiceEnabled / VoiceRouteId — enable voice and assign a CRID (required when voice is enabled)
  • DataEnabled — enable data capabilities (IoT numbers)
  • AssignedSubscriberId — assign a subscriber (TSUID-) at port time
  • ProductType — Sms-Only, Data-Only, Sms+Data, or Sms+Data+Voice
Number Provision (POST /v1.0/numbers/provision) and Numbers Update (POST /v1.0/numbers/update) now accept MmsMessageEnabled in the request body, so MMS can be enabled or disabled inline. MmsMessageEnabled is independent of MessageEnabled (SMS) and can still be changed on its own via POST /v1.0/numbers/mms/update.

​
Fixed

  • Clarified the MessageEnabled description across the Numbers endpoints — it controls SMS only and does not affect MMS. Earlier copy implied a single field toggled both SMS and MMS.
These are additive changes. Existing integrations continue to work without modification.
If you have questions about any of these changes, contact support@telegent.com.