IncomingPhoneNumber resource

The SID of the Account that created this IncomingPhoneNumber resource.

The SID of the Address resource associated with the phone number.

Whether the phone number requires an Address registered with Twilio. Can be: none, any, local, or foreign.

The API version used to start a new TwiML session.

Whether the phone number is new to the Twilio platform. Can be: true or false.

The set of Boolean properties that indicate whether a phone number can receive calls or messages. Capabilities are Voice, SMS, and MMS and each capability can be: true or false.

The date and time in GMT that the resource was created specified in RFC 2822 format.

The date and time in GMT that the resource was last updated specified in RFC 2822 format.

The string that you assigned to describe the resource.

The SID of the Identity resource that we associate with the phone number. Some regions require an Identity to meet local regulations.

The phone number in E.164 format, which consists of a + followed by the country code and subscriber number.

The phone number's origin. twilio identifies Twilio-owned phone numbers and hosted identifies hosted phone numbers.

The unique string that that we created to identify this IncomingPhoneNumber resource.

The SID of the application that handles SMS messages sent to the phone number. If an sms_application_sid is present, we ignore all sms_*_url values and use those of the application.

The HTTP method we use to call sms_fallback_url. Can be: GET or POST.

The URL that we call when an error occurs while retrieving or executing the TwiML from sms_url.

The HTTP method we use to call sms_url. Can be: GET or POST.

The URL we call when the phone number receives an incoming SMS message.

The URL we call using the status_callback_method to send status information to your application.

The HTTP method we use to call status_callback. Can be: GET or POST.

The SID of the Trunk that handles calls to the phone number. If a trunk_sid is present, we ignore all of the voice urls and voice applications and use those set on the Trunk. Setting a trunk_sid will automatically delete your voice_application_sid and vice versa.

The URI of the resource, relative to https://api.twilio.com.

The SID of the application that handles calls to the phone number. If a voice_application_sid is present, we ignore all of the voice urls and use those set on the application. Setting a voice_application_sid will automatically delete your trunk_sid and vice versa.

Whether we look up the caller's caller-ID name from the CNAM database ($0.01 per look up). Can be: true or false.

The HTTP method we use to call voice_fallback_url. Can be: GET or POST.

The URL that we call when an error occurs retrieving or executing the TwiML requested by url.

The HTTP method we use to call voice_url. Can be: GET or POST.

The URL we call when the phone number receives a call. The voice_url will not be used if a voice_application_sid or a trunk_sid is set.

The configuration status parameter that determines whether the phone number is enabled for emergency calling.

The SID of the emergency address configuration that we use for emergency calling from this phone number.

The SID of the Account that will create the resource.

The phone number to purchase specified in E.164 format. E.164 phone numbers consist of a + followed by the country code and subscriber number without punctuation characters. For example, +14155551234.

The desired area code for your new incoming phone number. Can be any three-digit, US or Canada area code. We will provision an available phone number within this area code for you. You must provide an area_code or a phone_number. (US and Canada only).

The API version to use for incoming calls made to the new phone number. The default is 2010-04-01.

A descriptive string that you created to describe the new phone number. It can be up to 64 characters long. By default, this is a formatted version of the new phone number.

The SID of the application that should handle SMS messages sent to the new phone number. If an sms_application_sid is present, we ignore all of the sms_*_url urls and use those set on the application.

The HTTP method that we should use to call sms_fallback_url. Can be: GET or POST and defaults to POST.

The URL that we should call when an error occurs while requesting or executing the TwiML defined by sms_url.

The HTTP method that we should use to call sms_url. Can be: GET or POST and defaults to POST.

The URL we should call when the new phone number receives an incoming SMS message.

The URL we should call using the status_callback_method to send status information to your application.

The HTTP method we should use to call status_callback. Can be: GET or POST and defaults to POST.

The SID of the application we should use to handle calls to the new phone number. If a voice_application_sid is present, we ignore all of the voice urls and use only those set on the application. Setting a voice_application_sid will automatically delete your trunk_sid and vice versa.

Whether to lookup the caller's name from the CNAM database and post it to your app. Can be: true or false and defaults to false.

The HTTP method that we should use to call voice_fallback_url. Can be: GET or POST and defaults to POST.

The URL that we should call when an error occurs retrieving or executing the TwiML requested by url.

The HTTP method that we should use to call voice_url. Can be: GET or POST and defaults to POST.

The URL that we should call to answer a call to the new phone number. The voice_url will not be called if a voice_application_sid or a trunk_sid is set.

The configuration status parameter that determines whether the new phone number is enabled for emergency calling.

The SID of the emergency address configuration to use for emergency calling from the new phone number.

The SID of the Trunk we should use to handle calls to the new phone number. If a trunk_sid is present, we ignore all of the voice urls and voice applications and use only those set on the Trunk. Setting a trunk_sid will automatically delete your voice_application_sid and vice versa.

The SID of the Identity resource that we should associate with the new phone number. Some regions require an identity to meet local regulations.

The SID of the Address resource we should associate with the new phone number. Some regions require addresses to meet local regulations.

The configuration parameter for the new phone number to receive incoming voice calls or faxes. Can be: fax or voice and defaults to voice.

The SID of the Account that created the IncomingPhoneNumber resource to fetch.

The Twilio-provided string that uniquely identifies the IncomingPhoneNumber resource to fetch.

The SID of the Account that created the IncomingPhoneNumber resources to read.

Whether to include phone numbers new to the Twilio platform. Can be: true or false and the default is true.

A string that identifies the IncomingPhoneNumber resources to read.

The phone numbers of the IncomingPhoneNumber resources to read. You can specify partial numbers and use '*' as a wildcard for any digit.

Whether to include phone numbers based on their origin. Can be: twilio or hosted. By default, phone numbers of all origin are included.

The SID of the Account that created the IncomingPhoneNumber resource to update. For more information, see Exchanging Numbers Between Subaccounts.

The Twilio-provided string that uniquely identifies the IncomingPhoneNumber resource to update.

The API version to use for incoming calls made to the phone number. The default is 2010-04-01.

A descriptive string that you created to describe this phone number. It can be up to 64 characters long. By default, this is a formatted version of the phone number.

The SID of the application that should handle SMS messages sent to the number. If an sms_application_sid is present, we ignore all of the sms_*_url urls and use those set on the application.

The HTTP method that we should use to call sms_fallback_url. Can be: GET or POST and defaults to POST.

The URL that we should call when an error occurs while requesting or executing the TwiML defined by sms_url.

The HTTP method that we should use to call sms_url. Can be: GET or POST and defaults to POST.

The URL we should call when the phone number receives an incoming SMS message.

The URL we should call using the status_callback_method to send status information to your application.

The HTTP method we should use to call status_callback. Can be: GET or POST and defaults to POST.

The SID of the application we should use to handle phone calls to the phone number. If a voice_application_sid is present, we ignore all of the voice urls and use only those set on the application. Setting a voice_application_sid will automatically delete your trunk_sid and vice versa.

Whether to lookup the caller's name from the CNAM database and post it to your app. Can be: true or false and defaults to false.

The HTTP method that we should use to call voice_fallback_url. Can be: GET or POST and defaults to POST.

The URL that we should call when an error occurs retrieving or executing the TwiML requested by url.

The HTTP method that we should use to call voice_url. Can be: GET or POST and defaults to POST.

The URL that we should call to answer a call to the phone number. The voice_url will not be called if a voice_application_sid or a trunk_sid is set.

The configuration status parameter that determines whether the phone number is enabled for emergency calling.

The SID of the emergency address configuration to use for emergency calling from this phone number.

The SID of the Trunk we should use to handle phone calls to the phone number. If a trunk_sid is present, we ignore all of the voice urls and voice applications and use only those set on the Trunk. Setting a trunk_sid will automatically delete your voice_application_sid and vice versa.

The configuration parameter for the phone number to receive incoming voice calls or faxes. Can be: fax or voice and defaults to voice.

The SID of the Identity resource that we should associate with the phone number. Some regions require an identity to meet local regulations.

The SID of the Address resource we should associate with the phone number. Some regions require addresses to meet local regulations.

The SID of the Account that created the IncomingPhoneNumber resources to delete.

The Twilio-provided string that uniquely identifies the IncomingPhoneNumber resource to delete.