Category: API
Summary: Due to regulatory requirements in some countries, an address may be required when purchasing/provisioning a sms number for sms messaging.
Context: This change was made due to increasing regulatory requirements in some countries. In order to continue to allow users to purchase/provision sms numbers, in some cases it is required to define the address that these numbers will be purchased for.
Impact: When calling POST /api/v2/routing/sms/phonenumbers to provision a number in countries with an address requirement (GET /api/v2/routing/sms/availablephonenumbers the response contains addressRequirement field) you will now need to provide an addressId with the POST request. Countries without address requirements no change is needed. If you need to provide an addressId you can GET list of addresses already added for your org by GET /api/v2/routing/sms/addresses or GET /api/v2/routing/sms/addresses/{addressId} Creating a new address is same as it was before POST /api/v2/routing/sms/addresses
Date of Change: Sept 10, 2019
Impacted APIs:
POST /api/v2/routing/sms/phonenumbers (addressId added as new optional parameter)
GET /api/v2/routing/sms/addresses?pageSize=500 (new API to get list of addresses)
GET /api/v2/routing/sms/addresses/{addressId} (new API to get address by ID)