Release MR130

Template

get_template_data_field_list
update_template_data_field_list
get_template_group_field_list
update_template_group_field_list

Marked "i_format_type" as readonly in TemplateDataFieldInfo and TemplateGroupFieldInfo. The field is still returned in responses but is no longer accepted on update — it is now derived from "i_format".

Values sent in this field on update are silently ignored.

Notification

update_notification_template

Removed "i_format_type" from the variables array in input. The value was redundant and is now derived from "i_format".

Stop sending "i_format_type" in the variables array — only "i_format" is needed.

Service

update_service

It's possible to set i_tax_transaction_code value for predefined (system) services

Session

login

A new credential pair (login, one_time_password) is now accepted from the customer and account realms — the one-time-password authenticates the user directly, without a static password. Available only from IP addresses listed in the Security.AllowLoginByOTPFrom configuration option. When the one-time-password was issued with a specific domain, the login request must originate from the same domain, otherwise it is rejected. When the user has multi-factor authentication configured, the returned session still requires 2FA confirmation before it can be used.

AccessControl

create_otp

Two optional inputs added: "otp_domain" binds the issued one-time-password to a domain (the default OTP notification templates append a trailing "@<otp_domain> #<password>" line so mobile clients can auto-fill the code, and a subsequent Session/login that uses this OTP is accepted only when the request originates from the same domain), and "skip_auth" (when set to 1) binds the OTP to the target entity instead of the caller's session, so the entity itself can later consume it via Session/login (the call must originate from an IP listed in the Security.AllowLoginByOTPFrom configuration option). The "notification_type" input is no longer mandatory — it may be omitted when an ESPF handler for the new Notification/PlatformManagement/OTPVerificationCode event is enabled, in which case the OTP is delivered via ESPF only.

Generic

get_config_data

Removed:

• Web.UseNewInterfaceForReseller
• Web.UseNewInterfaceForDistributor

Vendor

add_vendor
add_vendor_advanced
update_vendor
get_vendor_info
get_vendor_list

Removed:

• i_acl

• login

• password

• in_date_format, in_time_format

• out_date_format, out_time_format, out_date_time_format

• password_lifetime (for get_vendor_info)

Product

clone_product

Added optional input field "end_user_name" — sets the user-visible product name on the cloned product. When omitted, the new product retains the prior behavior: admin-realm clones inherit "end_user_name" from the parent product, reseller-realm clones default it to the new product "name".

Generic

get_config_data

Config options was extended with Customers.AllowedCleanupPeriod

Account, Customer

Account.get_emergency_details,
Customer.get_emergency_details,
Customer.get_customer_site_emergency_details

New read-only methods that return Bandwidth E911 emergency endpoint details (caller name and address) for an account, customer, or customer site.

TTS

get_capabilities

get_voice_list

New service with 2 new methods.

get_capabilities: returns voice-related capabilities for a Text-to-Speech provider - list of synthesis models with supported languages and an example of the per-voice settings payload.

get_voice_list: returns the list of available Text-to-Speech voices for a provider, optionally filtered by language and model.

CallControl

say

Synthesizes text and plays it as a prompt during an active IVR call using a Text-to-Speech provider. Supports codec selection (u_law, a_law, wav, mp3), provider-specific voice settings, and the same playback controls as the play method (repeat, interrupt on input, callbacks). In standalone mode, only previously cached audio is available.

NOTE: API methods for CallControl service are not reflected in API docs (that's by design)

DialingRule

add_dialing_rule
update_dialing_rule

Translation rule safety validation (tr_rule_from_local, tr_rule_to_local) now applies to all rule types (pbx, plan, advanced).

Previously it only applied to advanced. Rules containing unsafe code will be rejected with errEvalTranslationRule.

UA

get_ua_profile_info

The used field in ua_profile_info is now returned as the documented 'Y'/'N' string. Previously it was returned as the integer 0/1, contrary to the schema. get_ua_profile_list already returned 'Y'/'N'.

Clients that consume ua_profile_info.used must accept 'Y'/'N' instead of 0/1.

Product

add_product
update_product

It's not allowed to use fraud_protection='Debit' for input (the value is obsolete now) - the error is raised if you provide it in add/update API request.
But all existing products with 'Debit' are returned as is and you still can change fraud_protection mode for them.

DiscountPlan

add_vd_threshold
update_vd_threshold

For a Service Wallet (top-up) bundle item, notify_threshold_type now accepts only remaining_amount; other values (and a non-negative warning_threshold) are rejected with a fault instead of silently saving a zero threshold.

Product

add_product
update_product

Enabling a service feature whose service is not included in the product is now rejected with a fault (e.g. "emergency" on a product without the Voice Calls service). Disabling, clearing, or inheriting such a feature is still allowed.

Stop enabling service features for services the product does not include.

Account

add_account
update_account

Enabling a service feature whose service is not covered by the account's product or add-ons is now rejected with a fault. Disabling, clearing, or inheriting such a feature is still allowed.

Stop enabling service features for services not included by the account's product or add-ons.

Invoice

review_invoice
review_invoice_list

Added a new value pdf_regenerate to the action field. It regenerates the invoice PDF from the current template for an invoice under review (e.g. after the invoice template was changed), without recalculating charges or payments — the invoice stays under review. The existing approve and regenerate actions are unchanged.