You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2020/09/18 18:43:31 UTC
[camel] branch master updated: CAMEL-15478: Lets sort the APIs in
the docs
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new c15fe8f CAMEL-15478: Lets sort the APIs in the docs
c15fe8f is described below
commit c15fe8fff487079947483c065d00419cbf09192d
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Sep 18 20:39:23 2020 +0200
CAMEL-15478: Lets sort the APIs in the docs
---
.../camel/catalog/docs/twilio-component.adoc | 2626 ++++++++++----------
.../org/apache/camel/component/twilio/twilio.json | 8 +-
.../src/main/docs/twilio-component.adoc | 2626 ++++++++++----------
.../modules/ROOT/pages/twilio-component.adoc | 2626 ++++++++++----------
4 files changed, 3943 insertions(+), 3943 deletions(-)
diff --git a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/twilio-component.adoc b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/twilio-component.adoc
index 492a5cf..808161b 100644
--- a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/twilio-component.adoc
+++ b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/twilio-component.adoc
@@ -116,125 +116,111 @@ There are 56 API groups as listed in the table below:
[width="100%",cols="2,8",options="header"]
|===
| API Name | Description
-| *recording-add-on-result-payload* |
-| *usage-record-today* |
+| *account* |
+| *address* |
+| *address-dependent-phone-number* |
+| *application* |
+| *available-phone-number-country* |
| *available-phone-number-country-local* |
-| *call-recording* |
-| *queue-member* |
-| *usage-trigger* |
-| *usage-record-all-time* |
-| *usage-record-last-month* |
-| *recording-transcription* |
-| *message* |
+| *available-phone-number-country-mobile* |
+| *available-phone-number-country-toll-free* |
+| *call* |
+| *call-feedback* |
| *call-feedback-summary* |
-| *sip-credential-list-credential* |
-| *new-key* |
-| *incoming-phone-number* |
| *call-notification* |
-| *validation-request* |
-| *usage-record-yesterday* |
-| *usage-record-this-month* |
-| *new-signing-key* |
+| *call-recording* |
| *conference* |
-| *usage-record-daily* |
-| *application* |
-| *usage-record* |
-| *available-phone-number-country-mobile* |
| *conference-participant* |
+| *connect-app* |
+| *incoming-phone-number* |
+| *incoming-phone-number-local* |
+| *incoming-phone-number-mobile* |
+| *incoming-phone-number-toll-free* |
+| *key* |
+| *message* |
+| *message-feedback* |
+| *message-media* |
+| *new-key* |
+| *new-signing-key* |
| *notification* |
+| *outgoing-caller-id* |
+| *queue* |
+| *queue-member* |
+| *recording* |
| *recording-add-on-result* |
-| *sip-domain-ip-access-control-list-mapping* |
+| *recording-add-on-result-payload* |
+| *recording-transcription* |
+| *short-code* |
+| *signing-key* |
+| *sip-credential-list* |
+| *sip-credential-list-credential* |
| *sip-domain* |
-| *address* |
-| *message-media* |
-| *sip-ip-access-control-list-ip-address* |
-| *available-phone-number-country* |
-| *usage-record-yearly* |
-| *queue* |
-| *transcription* |
| *sip-domain-credential-list-mapping* |
-| *call-feedback* |
-| *key* |
-| *incoming-phone-number-toll-free* |
+| *sip-domain-ip-access-control-list-mapping* |
+| *sip-ip-access-control-list* |
+| *sip-ip-access-control-list-ip-address* |
| *token* |
-| *short-code* |
-| *available-phone-number-country-toll-free* |
+| *transcription* |
+| *usage-record* |
+| *usage-record-all-time* |
+| *usage-record-daily* |
+| *usage-record-last-month* |
| *usage-record-monthly* |
-| *sip-ip-access-control-list* |
-| *connect-app* |
-| *address-dependent-phone-number* |
-| *signing-key* |
-| *outgoing-caller-id* |
-| *call* |
-| *incoming-phone-number-local* |
-| *message-feedback* |
-| *recording* |
-| *incoming-phone-number-mobile* |
-| *account* |
-| *sip-credential-list* |
+| *usage-record-this-month* |
+| *usage-record-today* |
+| *usage-record-yearly* |
+| *usage-record-yesterday* |
+| *usage-trigger* |
+| *validation-request* |
|===
Each API is documented in the following sections to come.
-==== API: recording-add-on-result-payload
+==== API: account
-The recording-add-on-result-payload API has 3 method(s) which is represented by the following method signatures
+The account API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+com.twilio.rest.api.v2010.AccountFetcher fetcher();
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+com.twilio.rest.api.v2010.AccountFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid);
+com.twilio.rest.api.v2010.AccountUpdater updater();
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathReferenceSid, String pathAddOnResultSid);
+com.twilio.rest.api.v2010.AccountUpdater updater(String pathSid);
----
-The recording-add-on-result-payload API is defined in the syntax as follows:
+The account API is defined in the syntax as follows:
----
-twilio:recording-add-on-result-payload/methodName?[parameters]
+twilio:account/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a PayloadDeleter to execute delete
-| *fetcher* | fetch | Create a PayloadFetcher to execute fetch
-| *reader* | read | Create a PayloadReader to execute read
+| *fetcher* | fetch | Create a AccountFetcher to execute fetch
+| *updater* | update | Create a AccountUpdater to execute update
|===
-The recording-add-on-result-payload API method(s) has the following set of parameters listed in the table below:
+The account API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| deleter | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| fetcher | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
-| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| reader | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
+| fetcher | *pathSid* | Fetch by unique Account Sid | String
+| updater | *pathSid* | Update by unique Account Sid | String
|===
-In addition to the parameters above, the recording-add-on-result-payload API can also use from the 23 endpoint query option
+In addition to the parameters above, the account API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -244,44 +230,77 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-today
+==== API: address
-The usage-record-today API has 1 method(s) which is represented by the following method signatures
+The address API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.TodayReader reader();
+com.twilio.rest.api.v2010.account.AddressCreator creator(String customerName, String street, String city, String region, String postalCode, String isoCountry);
-com.twilio.rest.api.v2010.account.usage.record.TodayReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.AddressCreator creator(String pathAccountSid, String customerName, String street, String city, String region, String postalCode, String isoCountry);
+
+com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressReader reader();
+
+com.twilio.rest.api.v2010.account.AddressReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathSid);
----
-The usage-record-today API is defined in the syntax as follows:
+The address API is defined in the syntax as follows:
----
-twilio:usage-record-today/methodName?[parameters]
+twilio:address/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a TodayReader to execute read
+| *creator* | create | Create a AddressCreator to execute create
+| *deleter* | delete | Create a AddressDeleter to execute delete
+| *fetcher* | fetch | Create a AddressFetcher to execute fetch
+| *reader* | read | Create a AddressReader to execute read
+| *updater* | update | Create a AddressUpdater to execute update
|===
-The usage-record-today API method(s) has the following set of parameters listed in the table below:
+The address API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *city* | The city of the new address | String
+| creator | *customerName* | The name to associate with the new address | String
+| creator | *isoCountry* | The ISO country code of the new address | String
+| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Address resource | String
+| creator | *postalCode* | The postal code of the new address | String
+| creator | *region* | The state or region of the new address | String
+| creator | *street* | The number and street address of the new address | String
+| deleter | *pathAccountSid* | The SID of the Account that is responsible for the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that is responsible for this address | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that is responsible for this address | String
+| updater | *pathAccountSid* | The SID of the Account that is responsible for the resource to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the usage-record-today API can also use from the 23 endpoint query option
+In addition to the parameters above, the address API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -291,25 +310,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country-local
+==== API: address-dependent-phone-number
-The available-phone-number-country-local API has 1 method(s) which is represented by the following method signatures
+The address-dependent-phone-number API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAccountSid, String pathAddressSid);
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathCountryCode);
+com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAddressSid);
----
-The available-phone-number-country-local API is defined in the syntax as follows:
+The address-dependent-phone-number API is defined in the syntax as follows:
----
-twilio:available-phone-number-country-local/methodName?[parameters]
+twilio:address-dependent-phone-number/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -318,18 +337,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a LocalReader to execute read
+| *reader* | read | Create a DependentPhoneNumberReader to execute read
|===
-The available-phone-number-country-local API method(s) has the following set of parameters listed in the table below:
+The address-dependent-phone-number API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
-| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAddressSid* | The SID of the Address resource associated with the phone number | String
|===
-In addition to the parameters above, the available-phone-number-country-local API can also use from the 23 endpoint query option
+In addition to the parameters above, the address-dependent-phone-number API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -339,41 +358,41 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call-recording
+==== API: application
-The call-recording API has 5 method(s) which is represented by the following method signatures
+The application API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationCreator creator();
-com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationCreator creator(String pathAccountSid);
-com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationReader reader();
-com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathAccountSid, String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathSid);
----
-The call-recording API is defined in the syntax as follows:
+The application API is defined in the syntax as follows:
----
-twilio:call-recording/methodName?[parameters]
+twilio:application/methodName?[parameters]
----
The 5 method(s) is listed in the table below.
@@ -382,34 +401,28 @@ The 5 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a RecordingCreator to execute create
-| *deleter* | delete | Create a RecordingDeleter to execute delete
-| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
-| *reader* | read | Create a RecordingReader to execute read
-| *updater* | update | Create a RecordingUpdater to execute update
+| *creator* | create | Create a ApplicationCreator to execute create
+| *deleter* | delete | Create a ApplicationDeleter to execute delete
+| *fetcher* | fetch | Create a ApplicationFetcher to execute fetch
+| *reader* | read | Create a ApplicationReader to execute read
+| *updater* | update | Create a ApplicationUpdater to execute update
|===
-The call-recording API method(s) has the following set of parameters listed in the table below:
+The application API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *pathCallSid* | The SID of the Call to associate the resource with | String
| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathCallSid* | The SID of the Call to associate the resource with | String
| deleter | *pathSid* | The unique string that identifies the resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathCallSid* | The SID of the Call to associate the resource with | String
| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathCallSid* | The SID of the Call to associate the resource with | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
-| updater | *pathCallSid* | The SID of the Call to associate the resource with | String
+| updater | *pathAccountSid* | The SID of the Account that will create the resource | String
| updater | *pathSid* | The unique string that identifies the resource | String
-| updater | *status* | The new status of the recording | Status
|===
-In addition to the parameters above, the call-recording API can also use from the 23 endpoint query option
+In addition to the parameters above, the application API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -419,139 +432,99 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: queue-member
+==== API: available-phone-number-country
-The queue-member API has 3 method(s) which is represented by the following method signatures
+The available-phone-number-country API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathAccountSid, String pathQueueSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathQueueSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathAccountSid, String pathQueueSid);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathQueueSid);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathCountryCode);
-com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathAccountSid, String pathQueueSid, String pathCallSid, java.net.URI url);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader();
-com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathQueueSid, String pathCallSid, java.net.URI url);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader(String pathAccountSid);
----
-The queue-member API is defined in the syntax as follows:
+The available-phone-number-country API is defined in the syntax as follows:
----
-twilio:queue-member/methodName?[parameters]
+twilio:available-phone-number-country/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a MemberFetcher to execute fetch
-| *reader* | read | Create a MemberReader to execute read
-| *updater* | update | Create a MemberUpdater to execute update
+| *fetcher* | fetch | Create a AvailablePhoneNumberCountryFetcher to execute fetch
+| *reader* | read | Create a AvailablePhoneNumberCountryReader to execute read
|===
-The queue-member API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathCallSid* | The Call SID of the resource(s) to fetch | String
-| fetcher | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| reader | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathCallSid* | The Call SID of the resource(s) to update | String
-| updater | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| updater | *url* | The absolute URL of the Queue resource | URI
+| fetcher | *pathAccountSid* | The SID of the Account requesting the available phone number Country resource | String
+| fetcher | *pathCountryCode* | The ISO country code of the country to fetch available phone number information about | String
+| reader | *pathAccountSid* | The SID of the Account requesting the available phone number Country resources | String
|===
-In addition to the parameters above, the queue-member API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
-The message header name must be of the format `CamelTwilio.parameter`.
-The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
-would override a `CamelTwilio.myParameterNameHere` header.
-
-
-
-==== API: usage-trigger
-
-
-The usage-trigger API has 5 method(s) which is represented by the following method signatures
-(an API method may have multiple signatures due to overloading):
-
-[source,java]
-----
-
-com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(String pathAccountSid, java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
-
-com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
+The message header name must be of the format `CamelTwilio.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelTwilio.myParameterNameHere` header.
-com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathAccountSid, String pathSid);
+==== API: available-phone-number-country-local
-com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerReader reader();
+The available-phone-number-country-local API has 1 method(s) which is represented by the following method signatures
+(an API method may have multiple signatures due to overloading):
-com.twilio.rest.api.v2010.account.usage.TriggerReader reader(String pathAccountSid);
+[source,java]
+----
-com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathCountryCode);
----
-The usage-trigger API is defined in the syntax as follows:
+The available-phone-number-country-local API is defined in the syntax as follows:
----
-twilio:usage-trigger/methodName?[parameters]
+twilio:available-phone-number-country-local/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a TriggerCreator to execute create
-| *deleter* | delete | Create a TriggerDeleter to execute delete
-| *fetcher* | fetch | Create a TriggerFetcher to execute fetch
-| *reader* | read | Create a TriggerReader to execute read
-| *updater* | update | Create a TriggerUpdater to execute update
+| *reader* | read | Create a LocalReader to execute read
|===
-The usage-trigger API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country-local API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *callbackUrl* | The URL we call when the trigger fires | URI
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *triggerValue* | The usage value at which the trigger should fire | String
-| creator | *usageCategory* | The usage category the trigger watches | UsageCategory
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
+| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
|===
-In addition to the parameters above, the usage-trigger API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country-local API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -561,25 +534,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-all-time
+==== API: available-phone-number-country-mobile
-The usage-record-all-time API has 1 method(s) which is represented by the following method signatures
+The available-phone-number-country-mobile API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader();
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathCountryCode);
----
-The usage-record-all-time API is defined in the syntax as follows:
+The available-phone-number-country-mobile API is defined in the syntax as follows:
----
-twilio:usage-record-all-time/methodName?[parameters]
+twilio:available-phone-number-country-mobile/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -588,17 +561,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a AllTimeReader to execute read
+| *reader* | read | Create a MobileReader to execute read
|===
-The usage-record-all-time API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country-mobile API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
+| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
|===
-In addition to the parameters above, the usage-record-all-time API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country-mobile API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -608,25 +582,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-last-month
+==== API: available-phone-number-country-toll-free
-The usage-record-last-month API has 1 method(s) which is represented by the following method signatures
+The available-phone-number-country-toll-free API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader();
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathCountryCode);
----
-The usage-record-last-month API is defined in the syntax as follows:
+The available-phone-number-country-toll-free API is defined in the syntax as follows:
----
-twilio:usage-record-last-month/methodName?[parameters]
+twilio:available-phone-number-country-toll-free/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -635,17 +609,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a LastMonthReader to execute read
+| *reader* | read | Create a TollFreeReader to execute read
|===
-The usage-record-last-month API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country-toll-free API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
+| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
|===
-In addition to the parameters above, the usage-record-last-month API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country-toll-free API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -655,61 +630,84 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: recording-transcription
+==== API: call
-The recording-transcription API has 3 method(s) which is represented by the following method signatures
+The call API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathAccountSid, String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathAccountSid, String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
-com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathAccountSid, String pathRecordingSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathRecordingSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
+
+com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.CallReader reader();
+
+com.twilio.rest.api.v2010.account.CallReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.CallUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.CallUpdater updater(String pathSid);
----
-The recording-transcription API is defined in the syntax as follows:
+The call API is defined in the syntax as follows:
----
-twilio:recording-transcription/methodName?[parameters]
+twilio:call/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a TranscriptionDeleter to execute delete
-| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
-| *reader* | read | Create a TranscriptionReader to execute read
+| *creator* | create | Create a CallCreator to execute create
+| *deleter* | delete | Create a CallDeleter to execute delete
+| *fetcher* | fetch | Create a CallFetcher to execute fetch
+| *reader* | read | Create a CallReader to execute read
+| *updater* | update | Create a CallUpdater to execute update
|===
-The recording-transcription API method(s) has the following set of parameters listed in the table below:
+The call API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
+| creator | *applicationSid* | The SID of the Application resource that will handle the call | String
+| creator | *from* | Twilio number from which to originate the call | Endpoint
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *to* | Phone number, SIP address, or client identifier to call | Endpoint
+| creator | *twiml* | TwiML instructions for the call | Twiml
+| creator | *url* | The absolute URL that returns TwiML for this call | URI
+| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
+| deleter | *pathSid* | The unique string that identifies this resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathSid* | The SID of the Call resource to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the recording-transcription API can also use from the 23 endpoint query option
+In addition to the parameters above, the call API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -719,89 +717,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: message
+==== API: call-feedback
-The message API has 5 method(s) which is represented by the following method signatures
+The call-feedback API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathAccountSid, String pathCallSid, Integer qualityScore);
-com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathCallSid, Integer qualityScore);
-com.twilio.rest.api.v2010.account.MessageReader reader();
+com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathAccountSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.MessageReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathCallSid);
-com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathAccountSid, String pathSid, String body);
+com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathAccountSid, String pathCallSid, Integer qualityScore);
-com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathSid, String body);
+com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathCallSid, Integer qualityScore);
----
-The message API is defined in the syntax as follows:
+The call-feedback API is defined in the syntax as follows:
----
-twilio:message/methodName?[parameters]
+twilio:call-feedback/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a MessageCreator to execute create
-| *deleter* | delete | Create a MessageDeleter to execute delete
-| *fetcher* | fetch | Create a MessageFetcher to execute fetch
-| *reader* | read | Create a MessageReader to execute read
-| *updater* | update | Create a MessageUpdater to execute update
+| *creator* | create | Create a FeedbackCreator to execute create
+| *fetcher* | fetch | Create a FeedbackFetcher to execute fetch
+| *updater* | update | Create a FeedbackUpdater to execute update
|===
-The message API method(s) has the following set of parameters listed in the table below:
+The call-feedback API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *body* | The text of the message you want to send. Can be up to 1,600 characters in length. | String
-| creator | *from* | The phone number that initiated the message | PhoneNumber
-| creator | *mediaUrl* | The URL of the media to send with the message | List
-| creator | *messagingServiceSid* | The SID of the Messaging Service you want to associate with the message | String
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *to* | The destination phone number | PhoneNumber
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *body* | The text of the message you want to send | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| creator | *pathCallSid* | The call sid that uniquely identifies the call | String
+| creator | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathCallSid* | The call sid that uniquely identifies the call | String
+| updater | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *pathCallSid* | The call sid that uniquely identifies the call | String
+| updater | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
|===
-In addition to the parameters above, the message API can also use from the 23 endpoint query option
+In addition to the parameters above, the call-feedback API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -874,78 +844,53 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-credential-list-credential
+==== API: call-notification
-The sip-credential-list-credential API has 5 method(s) which is represented by the following method signatures
+The call-notification API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathAccountSid, String pathCredentialListSid, String username, String password);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathCredentialListSid, String username, String password);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathAccountSid, String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathAccountSid, String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathAccountSid, String pathCredentialListSid);
+com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathCredentialListSid);
+com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathCallSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathAccountSid, String pathCredentialListSid, String pathSid);
+com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathAccountSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathCredentialListSid, String pathSid);
+com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathCallSid);
----
-The sip-credential-list-credential API is defined in the syntax as follows:
+The call-notification API is defined in the syntax as follows:
----
-twilio:sip-credential-list-credential/methodName?[parameters]
+twilio:call-notification/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CredentialCreator to execute create
-| *deleter* | delete | Create a CredentialDeleter to execute delete
-| *fetcher* | fetch | Create a CredentialFetcher to execute fetch
-| *reader* | read | Create a CredentialReader to execute read
-| *updater* | update | Create a CredentialUpdater to execute update
+| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
+| *reader* | read | Create a NotificationReader to execute read
|===
-The sip-credential-list-credential API method(s) has the following set of parameters listed in the table below:
+The call-notification API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *password* | The password will not be returned in the response | String
-| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| creator | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| creator | *username* | The username for this credential | String
-| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| deleter | *pathSid* | The unique id that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| fetcher | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| fetcher | *pathSid* | The unique id that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| reader | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| updater | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| updater | *pathSid* | The unique id that identifies the resource to update | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathCallSid* | The Call SID of the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathCallSid* | The Call SID of the resource to fetch | String
|===
-In addition to the parameters above, the sip-credential-list-credential API can also use from the 23 endpoint query option
+In addition to the parameters above, the call-notification API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -955,44 +900,77 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: new-key
+==== API: call-recording
-The new-key API has 1 method(s) which is represented by the following method signatures
+The call-recording API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.NewKeyCreator creator();
+com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathAccountSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.NewKeyCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathCallSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathAccountSid, String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathAccountSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathCallSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathAccountSid, String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+
+com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
----
-The new-key API is defined in the syntax as follows:
+The call-recording API is defined in the syntax as follows:
----
-twilio:new-key/methodName?[parameters]
+twilio:call-recording/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a NewKeyCreator to execute create
+| *creator* | create | Create a RecordingCreator to execute create
+| *deleter* | delete | Create a RecordingDeleter to execute delete
+| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
+| *reader* | read | Create a RecordingReader to execute read
+| *updater* | update | Create a RecordingUpdater to execute update
|===
-The new-key API method(s) has the following set of parameters listed in the table below:
+The call-recording API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *pathCallSid* | The SID of the Call to associate the resource with | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathCallSid* | The SID of the Call to associate the resource with | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathCallSid* | The SID of the Call to associate the resource with | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathCallSid* | The SID of the Call to associate the resource with | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
+| updater | *pathCallSid* | The SID of the Call to associate the resource with | String
+| updater | *pathSid* | The unique string that identifies the resource | String
+| updater | *status* | The new status of the recording | Status
|===
-In addition to the parameters above, the new-key API can also use from the 23 endpoint query option
+In addition to the parameters above, the call-recording API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1002,77 +980,58 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number
+==== API: conference
-The incoming-phone-number API has 5 method(s) which is represented by the following method signatures
+The conference API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String areaCode);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, String areaCode);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader();
+com.twilio.rest.api.v2010.account.ConferenceReader reader();
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.ConferenceReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathSid);
----
-The incoming-phone-number API is defined in the syntax as follows:
+The conference API is defined in the syntax as follows:
----
-twilio:incoming-phone-number/methodName?[parameters]
+twilio:conference/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IncomingPhoneNumberCreator to execute create
-| *deleter* | delete | Create a IncomingPhoneNumberDeleter to execute delete
-| *fetcher* | fetch | Create a IncomingPhoneNumberFetcher to execute fetch
-| *reader* | read | Create a IncomingPhoneNumberReader to execute read
-| *updater* | update | Create a IncomingPhoneNumberUpdater to execute update
+| *fetcher* | fetch | Create a ConferenceFetcher to execute fetch
+| *reader* | read | Create a ConferenceReader to execute read
+| *updater* | update | Create a ConferenceUpdater to execute update
|===
-The incoming-phone-number API method(s) has the following set of parameters listed in the table below:
+The conference API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *areaCode* | The desired area code for the new phone number | String
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the incoming-phone-number API can also use from the 23 endpoint query option
+In addition to the parameters above, the conference API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1082,53 +1041,78 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call-notification
+==== API: conference-participant
-The call-notification API has 2 method(s) which is represented by the following method signatures
+The conference-participant API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathAccountSid, String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathAccountSid, String pathConferenceSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathCallSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathAccountSid, String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathAccountSid, String pathConferenceSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathConferenceSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathAccountSid, String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathConferenceSid, String pathCallSid);
----
-The call-notification API is defined in the syntax as follows:
+The conference-participant API is defined in the syntax as follows:
----
-twilio:call-notification/methodName?[parameters]
+twilio:conference-participant/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
-| *reader* | read | Create a NotificationReader to execute read
+| *creator* | create | Create a ParticipantCreator to execute create
+| *deleter* | delete | Create a ParticipantDeleter to execute delete
+| *fetcher* | fetch | Create a ParticipantFetcher to execute fetch
+| *reader* | read | Create a ParticipantReader to execute read
+| *updater* | update | Create a ParticipantUpdater to execute update
|===
-The call-notification API method(s) has the following set of parameters listed in the table below:
+The conference-participant API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *from* | The phone number, Client identifier, or username portion of SIP address that made this call. | PhoneNumber
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *pathConferenceSid* | The SID of the participant's conference | String
+| creator | *to* | The phone number, SIP address or Client identifier that received this call. | PhoneNumber
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathCallSid* | The Call SID or URL encoded label of the participant to delete | String
+| deleter | *pathConferenceSid* | The SID of the participant's conference | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathCallSid* | The Call SID of the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathCallSid* | The Call SID or URL encoded label of the participant to fetch | String
+| fetcher | *pathConferenceSid* | The SID of the participant's conference | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathCallSid* | The Call SID of the resource to fetch | String
+| reader | *pathConferenceSid* | The SID of the participant's conference | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathCallSid* | The Call SID or URL encoded label of the participant to update | String
+| updater | *pathConferenceSid* | The SID of the participant's conference | String
|===
-In addition to the parameters above, the call-notification API can also use from the 23 endpoint query option
+In addition to the parameters above, the conference-participant API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1138,45 +1122,65 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: validation-request
+==== API: connect-app
-The validation-request API has 1 method(s) which is represented by the following method signatures
+The connect-app API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppReader reader();
+
+com.twilio.rest.api.v2010.account.ConnectAppReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathSid);
----
-The validation-request API is defined in the syntax as follows:
+The connect-app API is defined in the syntax as follows:
----
-twilio:validation-request/methodName?[parameters]
+twilio:connect-app/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a ValidationRequestCreator to execute create
+| *deleter* | delete | Create a ConnectAppDeleter to execute delete
+| *fetcher* | fetch | Create a ConnectAppFetcher to execute fetch
+| *reader* | read | Create a ConnectAppReader to execute read
+| *updater* | update | Create a ConnectAppUpdater to execute update
|===
-The validation-request API method(s) has the following set of parameters listed in the table below:
+The connect-app API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account responsible for the new Caller ID | String
-| creator | *phoneNumber* | The phone number to verify in E.164 format | PhoneNumber
+| deleter | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the validation-request API can also use from the 23 endpoint query option
+In addition to the parameters above, the connect-app API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1186,44 +1190,77 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-yesterday
+==== API: incoming-phone-number
-The usage-record-yesterday API has 1 method(s) which is represented by the following method signatures
+The incoming-phone-number API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader();
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String areaCode);
-com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, String areaCode);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader();
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathSid);
----
-The usage-record-yesterday API is defined in the syntax as follows:
+The incoming-phone-number API is defined in the syntax as follows:
----
-twilio:usage-record-yesterday/methodName?[parameters]
+twilio:incoming-phone-number/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a YesterdayReader to execute read
+| *creator* | create | Create a IncomingPhoneNumberCreator to execute create
+| *deleter* | delete | Create a IncomingPhoneNumberDeleter to execute delete
+| *fetcher* | fetch | Create a IncomingPhoneNumberFetcher to execute fetch
+| *reader* | read | Create a IncomingPhoneNumberReader to execute read
+| *updater* | update | Create a IncomingPhoneNumberUpdater to execute update
|===
-The usage-record-yesterday API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *areaCode* | The desired area code for the new phone number | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the usage-record-yesterday API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1233,44 +1270,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-this-month
+==== API: incoming-phone-number-local
-The usage-record-this-month API has 1 method(s) which is represented by the following method signatures
+The incoming-phone-number-local API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader();
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader();
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader(String pathAccountSid);
----
-The usage-record-this-month API is defined in the syntax as follows:
+The incoming-phone-number-local API is defined in the syntax as follows:
----
-twilio:usage-record-this-month/methodName?[parameters]
+twilio:incoming-phone-number-local/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a ThisMonthReader to execute read
+| *creator* | create | Create a LocalCreator to execute create
+| *reader* | read | Create a LocalReader to execute read
|===
-The usage-record-this-month API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number-local API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the usage-record-this-month API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number-local API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1280,44 +1324,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: new-signing-key
+==== API: incoming-phone-number-mobile
-The new-signing-key API has 1 method(s) which is represented by the following method signatures
+The incoming-phone-number-mobile API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator();
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader();
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader(String pathAccountSid);
----
-The new-signing-key API is defined in the syntax as follows:
+The incoming-phone-number-mobile API is defined in the syntax as follows:
----
-twilio:new-signing-key/methodName?[parameters]
+twilio:incoming-phone-number-mobile/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a NewSigningKeyCreator to execute create
+| *creator* | create | Create a MobileCreator to execute create
+| *reader* | read | Create a MobileReader to execute read
|===
-The new-signing-key API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number-mobile API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the new-signing-key API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number-mobile API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1327,58 +1378,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: conference
+==== API: incoming-phone-number-toll-free
-The conference API has 3 method(s) which is represented by the following method signatures
+The incoming-phone-number-toll-free API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.ConferenceReader reader();
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.ConferenceReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader();
-com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader(String pathAccountSid);
----
-The conference API is defined in the syntax as follows:
+The incoming-phone-number-toll-free API is defined in the syntax as follows:
----
-twilio:conference/methodName?[parameters]
+twilio:incoming-phone-number-toll-free/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a ConferenceFetcher to execute fetch
-| *reader* | read | Create a ConferenceReader to execute read
-| *updater* | update | Create a ConferenceUpdater to execute update
+| *creator* | create | Create a TollFreeCreator to execute create
+| *reader* | read | Create a TollFreeReader to execute read
|===
-The conference API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number-toll-free API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathSid* | The unique string that identifies this resource | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the conference API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number-toll-free API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1388,44 +1432,65 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-daily
+==== API: key
-The usage-record-daily API has 1 method(s) which is represented by the following method signatures
+The key API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.DailyReader reader();
+com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.usage.record.DailyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyReader reader();
+
+com.twilio.rest.api.v2010.account.KeyReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathSid);
----
-The usage-record-daily API is defined in the syntax as follows:
+The key API is defined in the syntax as follows:
----
-twilio:usage-record-daily/methodName?[parameters]
+twilio:key/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a DailyReader to execute read
+| *deleter* | delete | Create a KeyDeleter to execute delete
+| *fetcher* | fetch | Create a KeyFetcher to execute fetch
+| *reader* | read | Create a KeyReader to execute read
+| *updater* | update | Create a KeyUpdater to execute update
|===
-The usage-record-daily API method(s) has the following set of parameters listed in the table below:
+The key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the usage-record-daily API can also use from the 23 endpoint query option
+In addition to the parameters above, the key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1435,41 +1500,53 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: application
+==== API: message
-The application API has 5 method(s) which is represented by the following method signatures
+The message API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ApplicationCreator creator();
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-com.twilio.rest.api.v2010.account.ApplicationCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationReader reader();
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-com.twilio.rest.api.v2010.account.ApplicationReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.MessageReader reader();
+
+com.twilio.rest.api.v2010.account.MessageReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathAccountSid, String pathSid, String body);
+
+com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathSid, String body);
----
-The application API is defined in the syntax as follows:
+The message API is defined in the syntax as follows:
----
-twilio:application/methodName?[parameters]
+twilio:message/methodName?[parameters]
----
The 5 method(s) is listed in the table below.
@@ -1478,28 +1555,34 @@ The 5 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a ApplicationCreator to execute create
-| *deleter* | delete | Create a ApplicationDeleter to execute delete
-| *fetcher* | fetch | Create a ApplicationFetcher to execute fetch
-| *reader* | read | Create a ApplicationReader to execute read
-| *updater* | update | Create a ApplicationUpdater to execute update
+| *creator* | create | Create a MessageCreator to execute create
+| *deleter* | delete | Create a MessageDeleter to execute delete
+| *fetcher* | fetch | Create a MessageFetcher to execute fetch
+| *reader* | read | Create a MessageReader to execute read
+| *updater* | update | Create a MessageUpdater to execute update
|===
-The application API method(s) has the following set of parameters listed in the table below:
+The message API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *body* | The text of the message you want to send. Can be up to 1,600 characters in length. | String
+| creator | *from* | The phone number that initiated the message | PhoneNumber
+| creator | *mediaUrl* | The URL of the media to send with the message | List
+| creator | *messagingServiceSid* | The SID of the Messaging Service you want to associate with the message | String
| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *to* | The destination phone number | PhoneNumber
| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
| deleter | *pathSid* | The unique string that identifies the resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that will create the resource | String
+| updater | *body* | The text of the message you want to send | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the application API can also use from the 23 endpoint query option
+In addition to the parameters above, the message API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1509,25 +1592,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record
+==== API: message-feedback
-The usage-record API has 1 method(s) which is represented by the following method signatures
+The message-feedback API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.RecordReader reader();
+com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathAccountSid, String pathMessageSid);
-com.twilio.rest.api.v2010.account.usage.RecordReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathMessageSid);
----
-The usage-record API is defined in the syntax as follows:
+The message-feedback API is defined in the syntax as follows:
----
-twilio:usage-record/methodName?[parameters]
+twilio:message-feedback/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -1536,17 +1619,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a RecordReader to execute read
+| *creator* | create | Create a FeedbackCreator to execute create
|===
-The usage-record API method(s) has the following set of parameters listed in the table below:
+The message-feedback API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *pathMessageSid* | The SID of the Message resource for which the feedback was provided | String
|===
-In addition to the parameters above, the usage-record API can also use from the 23 endpoint query option
+In addition to the parameters above, the message-feedback API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1556,45 +1640,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country-mobile
+==== API: message-media
-The available-phone-number-country-mobile API has 1 method(s) which is represented by the following method signatures
+The message-media API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathAccountSid, String pathMessageSid, String pathSid);
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathCountryCode);
+com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathMessageSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathAccountSid, String pathMessageSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathMessageSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathAccountSid, String pathMessageSid);
+
+com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathMessageSid);
----
-The available-phone-number-country-mobile API is defined in the syntax as follows:
+The message-media API is defined in the syntax as follows:
----
-twilio:available-phone-number-country-mobile/methodName?[parameters]
+twilio:message-media/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a MobileReader to execute read
+| *deleter* | delete | Create a MediaDeleter to execute delete
+| *fetcher* | fetch | Create a MediaFetcher to execute fetch
+| *reader* | read | Create a MediaReader to execute read
|===
-The available-phone-number-country-mobile API method(s) has the following set of parameters listed in the table below:
+The message-media API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
-| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
+| deleter | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
+| deleter | *pathSid* | The unique string that identifies this resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
+| fetcher | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| reader | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
|===
-In addition to the parameters above, the available-phone-number-country-mobile API can also use from the 23 endpoint query option
+In addition to the parameters above, the message-media API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1604,78 +1704,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: conference-participant
+==== API: new-key
-The conference-participant API has 5 method(s) which is represented by the following method signatures
+The new-key API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathAccountSid, String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathAccountSid, String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathAccountSid, String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathAccountSid, String pathConferenceSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathConferenceSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathAccountSid, String pathConferenceSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.NewKeyCreator creator();
-com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathConferenceSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.NewKeyCreator creator(String pathAccountSid);
----
-The conference-participant API is defined in the syntax as follows:
+The new-key API is defined in the syntax as follows:
----
-twilio:conference-participant/methodName?[parameters]
+twilio:new-key/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a ParticipantCreator to execute create
-| *deleter* | delete | Create a ParticipantDeleter to execute delete
-| *fetcher* | fetch | Create a ParticipantFetcher to execute fetch
-| *reader* | read | Create a ParticipantReader to execute read
-| *updater* | update | Create a ParticipantUpdater to execute update
+| *creator* | create | Create a NewKeyCreator to execute create
|===
-The conference-participant API method(s) has the following set of parameters listed in the table below:
+The new-key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *from* | The phone number, Client identifier, or username portion of SIP address that made this call. | PhoneNumber
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *pathConferenceSid* | The SID of the participant's conference | String
-| creator | *to* | The phone number, SIP address or Client identifier that received this call. | PhoneNumber
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathCallSid* | The Call SID or URL encoded label of the participant to delete | String
-| deleter | *pathConferenceSid* | The SID of the participant's conference | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathCallSid* | The Call SID or URL encoded label of the participant to fetch | String
-| fetcher | *pathConferenceSid* | The SID of the participant's conference | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathConferenceSid* | The SID of the participant's conference | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathCallSid* | The Call SID or URL encoded label of the participant to update | String
-| updater | *pathConferenceSid* | The SID of the participant's conference | String
+| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
|===
-In addition to the parameters above, the conference-participant API can also use from the 23 endpoint query option
+In addition to the parameters above, the new-key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1685,51 +1751,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: notification
+==== API: new-signing-key
-The notification API has 2 method(s) which is represented by the following method signatures
+The new-signing-key API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.NotificationReader reader();
+com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator();
-com.twilio.rest.api.v2010.account.NotificationReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator(String pathAccountSid);
----
-The notification API is defined in the syntax as follows:
+The new-signing-key API is defined in the syntax as follows:
----
-twilio:notification/methodName?[parameters]
+twilio:new-signing-key/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
-| *reader* | read | Create a NotificationReader to execute read
+| *creator* | create | Create a NewSigningKeyCreator to execute create
|===
-The notification API method(s) has the following set of parameters listed in the table below:
+The new-signing-key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
|===
-In addition to the parameters above, the notification API can also use from the 23 endpoint query option
+In addition to the parameters above, the new-signing-key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1739,61 +1798,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: recording-add-on-result
+==== API: notification
-The recording-add-on-result API has 3 method(s) which is represented by the following method signatures
+The notification API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathReferenceSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathSid);
+com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathReferenceSid, String pathSid);
+com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathAccountSid, String pathReferenceSid);
+com.twilio.rest.api.v2010.account.NotificationReader reader();
-com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathReferenceSid);
+com.twilio.rest.api.v2010.account.NotificationReader reader(String pathAccountSid);
----
-The recording-add-on-result API is defined in the syntax as follows:
+The notification API is defined in the syntax as follows:
----
-twilio:recording-add-on-result/methodName?[parameters]
+twilio:notification/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a AddOnResultDeleter to execute delete
-| *fetcher* | fetch | Create a AddOnResultFetcher to execute fetch
-| *reader* | read | Create a AddOnResultReader to execute read
+| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
+| *reader* | read | Create a NotificationReader to execute read
|===
-The recording-add-on-result API method(s) has the following set of parameters listed in the table below:
+The notification API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
-| deleter | *pathSid* | The unique string that identifies the resource to delete | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
-| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
|===
-In addition to the parameters above, the recording-add-on-result API can also use from the 23 endpoint query option
+In addition to the parameters above, the notification API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1803,37 +1852,37 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-domain-ip-access-control-list-mapping
+==== API: outgoing-caller-id
-The sip-domain-ip-access-control-list-mapping API has 4 method(s) which is represented by the following method signatures
+The outgoing-caller-id API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathAccountSid, String pathDomainSid, String ipAccessControlListSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathDomainSid, String ipAccessControlListSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader();
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathAccountSid, String pathDomainSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathDomainSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathSid);
----
-The sip-domain-ip-access-control-list-mapping API is defined in the syntax as follows:
+The outgoing-caller-id API is defined in the syntax as follows:
----
-twilio:sip-domain-ip-access-control-list-mapping/methodName?[parameters]
+twilio:outgoing-caller-id/methodName?[parameters]
----
The 4 method(s) is listed in the table below.
@@ -1842,30 +1891,26 @@ The 4 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IpAccessControlListMappingCreator to execute create
-| *deleter* | delete | Create a IpAccessControlListMappingDeleter to execute delete
-| *fetcher* | fetch | Create a IpAccessControlListMappingFetcher to execute fetch
-| *reader* | read | Create a IpAccessControlListMappingReader to execute read
+| *deleter* | delete | Create a OutgoingCallerIdDeleter to execute delete
+| *fetcher* | fetch | Create a OutgoingCallerIdFetcher to execute fetch
+| *reader* | read | Create a OutgoingCallerIdReader to execute read
+| *updater* | update | Create a OutgoingCallerIdUpdater to execute update
|===
-The sip-domain-ip-access-control-list-mapping API method(s) has the following set of parameters listed in the table below:
+The outgoing-caller-id API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *ipAccessControlListSid* | The unique id of the IP access control list to map to the SIP domain | String
-| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| creator | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
-| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
-| deleter | *pathSid* | A 34 character string that uniquely identifies the resource to delete. | String
-| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| fetcher | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
-| fetcher | *pathSid* | A 34 character string that uniquely identifies the resource to fetch. | String
-| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| reader | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the sip-domain-ip-access-control-list-mapping API can also use from the 23 endpoint query option
+In addition to the parameters above, the outgoing-caller-id API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1875,41 +1920,41 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-domain
+==== API: queue
-The sip-domain API has 5 method(s) which is represented by the following method signatures
+The queue API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String domainName);
+com.twilio.rest.api.v2010.account.QueueCreator creator(String friendlyName);
-com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String pathAccountSid, String domainName);
+com.twilio.rest.api.v2010.account.QueueCreator creator(String pathAccountSid, String friendlyName);
-com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainReader reader();
+com.twilio.rest.api.v2010.account.QueueReader reader();
-com.twilio.rest.api.v2010.account.sip.DomainReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.QueueReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathSid);
----
-The sip-domain API is defined in the syntax as follows:
+The queue API is defined in the syntax as follows:
----
-twilio:sip-domain/methodName?[parameters]
+twilio:queue/methodName?[parameters]
----
The 5 method(s) is listed in the table below.
@@ -1918,29 +1963,29 @@ The 5 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a DomainCreator to execute create
-| *deleter* | delete | Create a DomainDeleter to execute delete
-| *fetcher* | fetch | Create a DomainFetcher to execute fetch
-| *reader* | read | Create a DomainReader to execute read
-| *updater* | update | Create a DomainUpdater to execute update
+| *creator* | create | Create a QueueCreator to execute create
+| *deleter* | delete | Create a QueueDeleter to execute delete
+| *fetcher* | fetch | Create a QueueFetcher to execute fetch
+| *reader* | read | Create a QueueReader to execute read
+| *updater* | update | Create a QueueUpdater to execute update
|===
-The sip-domain API method(s) has the following set of parameters listed in the table below:
+The queue API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *domainName* | The unique address on Twilio to route SIP traffic | String
+| creator | *friendlyName* | A string to describe this resource | String
| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
+| deleter | *pathSid* | The unique string that identifies this resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the sip-domain API can also use from the 23 endpoint query option
+In addition to the parameters above, the queue API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1950,77 +1995,62 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: address
+==== API: queue-member
-The address API has 5 method(s) which is represented by the following method signatures
+The queue-member API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.AddressCreator creator(String customerName, String street, String city, String region, String postalCode, String isoCountry);
-
-com.twilio.rest.api.v2010.account.AddressCreator creator(String pathAccountSid, String customerName, String street, String city, String region, String postalCode, String isoCountry);
-
-com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathAccountSid, String pathQueueSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathQueueSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.AddressReader reader();
+com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathAccountSid, String pathQueueSid);
-com.twilio.rest.api.v2010.account.AddressReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathQueueSid);
-com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathAccountSid, String pathQueueSid, String pathCallSid, java.net.URI url);
-com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathQueueSid, String pathCallSid, java.net.URI url);
----
-The address API is defined in the syntax as follows:
+The queue-member API is defined in the syntax as follows:
----
-twilio:address/methodName?[parameters]
+twilio:queue-member/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a AddressCreator to execute create
-| *deleter* | delete | Create a AddressDeleter to execute delete
-| *fetcher* | fetch | Create a AddressFetcher to execute fetch
-| *reader* | read | Create a AddressReader to execute read
-| *updater* | update | Create a AddressUpdater to execute update
+| *fetcher* | fetch | Create a MemberFetcher to execute fetch
+| *reader* | read | Create a MemberReader to execute read
+| *updater* | update | Create a MemberUpdater to execute update
|===
-The address API method(s) has the following set of parameters listed in the table below:
+The queue-member API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *city* | The city of the new address | String
-| creator | *customerName* | The name to associate with the new address | String
-| creator | *isoCountry* | The ISO country code of the new address | String
-| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Address resource | String
-| creator | *postalCode* | The postal code of the new address | String
-| creator | *region* | The state or region of the new address | String
-| creator | *street* | The number and street address of the new address | String
-| deleter | *pathAccountSid* | The SID of the Account that is responsible for the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that is responsible for this address | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that is responsible for this address | String
-| updater | *pathAccountSid* | The SID of the Account that is responsible for the resource to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathCallSid* | The Call SID of the resource(s) to fetch | String
+| fetcher | *pathQueueSid* | The SID of the Queue in which to find the members | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| reader | *pathQueueSid* | The SID of the Queue in which to find the members | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathCallSid* | The Call SID of the resource(s) to update | String
+| updater | *pathQueueSid* | The SID of the Queue in which to find the members | String
+| updater | *url* | The absolute URL of the Queue resource | URI
|===
-In addition to the parameters above, the address API can also use from the 23 endpoint query option
+In addition to the parameters above, the queue-member API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2030,33 +2060,33 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: message-media
+==== API: recording
-The message-media API has 3 method(s) which is represented by the following method signatures
+The recording API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathAccountSid, String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathAccountSid, String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathAccountSid, String pathMessageSid);
+com.twilio.rest.api.v2010.account.RecordingReader reader();
-com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathMessageSid);
+com.twilio.rest.api.v2010.account.RecordingReader reader(String pathAccountSid);
----
-The message-media API is defined in the syntax as follows:
+The recording API is defined in the syntax as follows:
----
-twilio:message-media/methodName?[parameters]
+twilio:recording/methodName?[parameters]
----
The 3 method(s) is listed in the table below.
@@ -2065,26 +2095,23 @@ The 3 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a MediaDeleter to execute delete
-| *fetcher* | fetch | Create a MediaFetcher to execute fetch
-| *reader* | read | Create a MediaReader to execute read
+| *deleter* | delete | Create a RecordingDeleter to execute delete
+| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
+| *reader* | read | Create a RecordingReader to execute read
|===
-The message-media API method(s) has the following set of parameters listed in the table below:
+The recording API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
-| deleter | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
-| deleter | *pathSid* | The unique string that identifies this resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
-| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| reader | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the message-media API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2094,78 +2121,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-ip-access-control-list-ip-address
+==== API: recording-add-on-result
-The sip-ip-access-control-list-ip-address API has 5 method(s) which is represented by the following method signatures
+The recording-add-on-result API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathAccountSid, String pathIpAccessControlListSid, String friendlyName, String ipAddress);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathIpAccessControlListSid, String friendlyName, String ipAddress);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathIpAccessControlListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathAccountSid, String pathIpAccessControlListSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathIpAccessControlListSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathAccountSid, String pathReferenceSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathReferenceSid);
----
-The sip-ip-access-control-list-ip-address API is defined in the syntax as follows:
+The recording-add-on-result API is defined in the syntax as follows:
----
-twilio:sip-ip-access-control-list-ip-address/methodName?[parameters]
+twilio:recording-add-on-result/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IpAddressCreator to execute create
-| *deleter* | delete | Create a IpAddressDeleter to execute delete
-| *fetcher* | fetch | Create a IpAddressFetcher to execute fetch
-| *reader* | read | Create a IpAddressReader to execute read
-| *updater* | update | Create a IpAddressUpdater to execute update
+| *deleter* | delete | Create a AddOnResultDeleter to execute delete
+| *fetcher* | fetch | Create a AddOnResultFetcher to execute fetch
+| *reader* | read | Create a AddOnResultReader to execute read
|===
-The sip-ip-access-control-list-ip-address API method(s) has the following set of parameters listed in the table below:
+The recording-add-on-result API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | A human readable descriptive text for this resource, up to 64 characters long. | String
-| creator | *ipAddress* | An IP address in dotted decimal notation from which you want to accept traffic. Any SIP requests from this IP address will be allowed by Twilio. IPv4 only supported today. | String
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| creator | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| deleter | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| deleter | *pathSid* | A string that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| fetcher | *pathSid* | A string that identifies the IpAddress resource to fetch | String
-| reader | *pathAccountSid* | The unique sid that identifies this account | String
-| reader | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| updater | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| updater | *pathSid* | A string that identifies the IpAddress resource to update | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
+| deleter | *pathSid* | The unique string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
+| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
|===
-In addition to the parameters above, the sip-ip-access-control-list-ip-address API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording-add-on-result API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2175,51 +2185,64 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country
+==== API: recording-add-on-result-payload
-The available-phone-number-country API has 2 method(s) which is represented by the following method signatures
+The recording-add-on-result-payload API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathCountryCode);
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader();
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid);
+
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathReferenceSid, String pathAddOnResultSid);
----
-The available-phone-number-country API is defined in the syntax as follows:
+The recording-add-on-result-payload API is defined in the syntax as follows:
----
-twilio:available-phone-number-country/methodName?[parameters]
+twilio:recording-add-on-result-payload/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a AvailablePhoneNumberCountryFetcher to execute fetch
-| *reader* | read | Create a AvailablePhoneNumberCountryReader to execute read
+| *deleter* | delete | Create a PayloadDeleter to execute delete
+| *fetcher* | fetch | Create a PayloadFetcher to execute fetch
+| *reader* | read | Create a PayloadReader to execute read
|===
-The available-phone-number-country API method(s) has the following set of parameters listed in the table below:
+The recording-add-on-result-payload API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account requesting the available phone number Country resource | String
-| fetcher | *pathCountryCode* | The ISO country code of the country to fetch available phone number information about | String
-| reader | *pathAccountSid* | The SID of the Account requesting the available phone number Country resources | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
+| deleter | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
+| fetcher | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
+| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
+| reader | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
|===
-In addition to the parameters above, the available-phone-number-country API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording-add-on-result-payload API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2229,44 +2252,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-yearly
+==== API: recording-transcription
-The usage-record-yearly API has 1 method(s) which is represented by the following method signatures
+The recording-transcription API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader();
+com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathAccountSid, String pathRecordingSid, String pathSid);
-com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathRecordingSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathAccountSid, String pathRecordingSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathRecordingSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathAccountSid, String pathRecordingSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathRecordingSid);
----
-The usage-record-yearly API is defined in the syntax as follows:
+The recording-transcription API is defined in the syntax as follows:
----
-twilio:usage-record-yearly/methodName?[parameters]
+twilio:recording-transcription/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a YearlyReader to execute read
+| *deleter* | delete | Create a TranscriptionDeleter to execute delete
+| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
+| *reader* | read | Create a TranscriptionReader to execute read
|===
-The usage-record-yearly API method(s) has the following set of parameters listed in the table below:
+The recording-transcription API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
|===
-In addition to the parameters above, the usage-record-yearly API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording-transcription API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2276,72 +2316,58 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: queue
+==== API: short-code
-The queue API has 5 method(s) which is represented by the following method signatures
+The short-code API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.QueueCreator creator(String friendlyName);
-
-com.twilio.rest.api.v2010.account.QueueCreator creator(String pathAccountSid, String friendlyName);
-
-com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.QueueReader reader();
+com.twilio.rest.api.v2010.account.ShortCodeReader reader();
-com.twilio.rest.api.v2010.account.QueueReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.ShortCodeReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathSid);
----
-The queue API is defined in the syntax as follows:
+The short-code API is defined in the syntax as follows:
----
-twilio:queue/methodName?[parameters]
+twilio:short-code/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a QueueCreator to execute create
-| *deleter* | delete | Create a QueueDeleter to execute delete
-| *fetcher* | fetch | Create a QueueFetcher to execute fetch
-| *reader* | read | Create a QueueReader to execute read
-| *updater* | update | Create a QueueUpdater to execute update
+| *fetcher* | fetch | Create a ShortCodeFetcher to execute fetch
+| *reader* | read | Create a ShortCodeReader to execute read
+| *updater* | update | Create a ShortCodeUpdater to execute update
|===
-The queue API method(s) has the following set of parameters listed in the table below:
+The short-code API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | A string to describe this resource | String
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
-| deleter | *pathSid* | The unique string that identifies this resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the queue API can also use from the 23 endpoint query option
+In addition to the parameters above, the short-code API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2351,58 +2377,65 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: transcription
+==== API: signing-key
-The transcription API has 3 method(s) which is represented by the following method signatures
+The signing-key API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionReader reader();
+com.twilio.rest.api.v2010.account.SigningKeyReader reader();
-com.twilio.rest.api.v2010.account.TranscriptionReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.SigningKeyReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathSid);
----
-The transcription API is defined in the syntax as follows:
+The signing-key API is defined in the syntax as follows:
----
-twilio:transcription/methodName?[parameters]
+twilio:signing-key/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a TranscriptionDeleter to execute delete
-| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
-| *reader* | read | Create a TranscriptionReader to execute read
+| *deleter* | delete | Create a SigningKeyDeleter to execute delete
+| *fetcher* | fetch | Create a SigningKeyFetcher to execute fetch
+| *reader* | read | Create a SigningKeyReader to execute read
+| *updater* | update | Create a SigningKeyUpdater to execute update
|===
-The transcription API method(s) has the following set of parameters listed in the table below:
+The signing-key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| deleter | *pathAccountSid* | The account_sid | String
+| deleter | *pathSid* | The sid | String
+| fetcher | *pathAccountSid* | The account_sid | String
+| fetcher | *pathSid* | The sid | String
+| reader | *pathAccountSid* | The account_sid | String
+| updater | *pathAccountSid* | The account_sid | String
+| updater | *pathSid* | The sid | String
|===
-In addition to the parameters above, the transcription API can also use from the 23 endpoint query option
+In addition to the parameters above, the signing-key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2412,69 +2445,73 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-domain-credential-list-mapping
+==== API: sip-credential-list
-The sip-domain-credential-list-mapping API has 4 method(s) which is represented by the following method signatures
+The sip-credential-list API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathAccountSid, String pathDomainSid, String credentialListSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String friendlyName);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathDomainSid, String credentialListSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String pathAccountSid, String friendlyName);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathAccountSid, String pathDomainSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListReader reader();
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathDomainSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+
+com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathSid, String friendlyName);
----
-The sip-domain-credential-list-mapping API is defined in the syntax as follows:
+The sip-credential-list API is defined in the syntax as follows:
----
-twilio:sip-domain-credential-list-mapping/methodName?[parameters]
+twilio:sip-credential-list/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CredentialListMappingCreator to execute create
-| *deleter* | delete | Create a CredentialListMappingDeleter to execute delete
-| *fetcher* | fetch | Create a CredentialListMappingFetcher to execute fetch
-| *reader* | read | Create a CredentialListMappingReader to execute read
+| *creator* | create | Create a CredentialListCreator to execute create
+| *deleter* | delete | Create a CredentialListDeleter to execute delete
+| *fetcher* | fetch | Create a CredentialListFetcher to execute fetch
+| *reader* | read | Create a CredentialListReader to execute read
+| *updater* | update | Create a CredentialListUpdater to execute update
|===
-The sip-domain-credential-list-mapping API method(s) has the following set of parameters listed in the table below:
+The sip-credential-list API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *credentialListSid* | A string that identifies the CredentialList resource to map to the SIP domain | String
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| creator | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
-| deleter | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
-| deleter | *pathSid* | A string that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
-| fetcher | *pathSid* | A string that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The unique sid that identifies this account | String
-| reader | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| creator | *friendlyName* | Human readable descriptive text | String
+| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathSid* | Delete by unique credential list Sid | String
+| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| fetcher | *pathSid* | Fetch by unique credential list Sid | String
+| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| updater | *friendlyName* | Human readable descriptive text | String
+| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| updater | *pathSid* | Update by unique credential list Sid | String
|===
-In addition to the parameters above, the sip-domain-credential-list-mapping API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-credential-list API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2484,61 +2521,78 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call-feedback
+==== API: sip-credential-list-credential
-The call-feedback API has 3 method(s) which is represented by the following method signatures
+The sip-credential-list-credential API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathAccountSid, String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathAccountSid, String pathCredentialListSid, String username, String password);
-com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathCredentialListSid, String username, String password);
-com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathAccountSid, String pathCredentialListSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathCallSid);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathCredentialListSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathAccountSid, String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathAccountSid, String pathCredentialListSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathCredentialListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathAccountSid, String pathCredentialListSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathCredentialListSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathAccountSid, String pathCredentialListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathCredentialListSid, String pathSid);
----
-The call-feedback API is defined in the syntax as follows:
+The sip-credential-list-credential API is defined in the syntax as follows:
----
-twilio:call-feedback/methodName?[parameters]
+twilio:sip-credential-list-credential/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a FeedbackCreator to execute create
-| *fetcher* | fetch | Create a FeedbackFetcher to execute fetch
-| *updater* | update | Create a FeedbackUpdater to execute update
+| *creator* | create | Create a CredentialCreator to execute create
+| *deleter* | delete | Create a CredentialDeleter to execute delete
+| *fetcher* | fetch | Create a CredentialFetcher to execute fetch
+| *reader* | read | Create a CredentialReader to execute read
+| *updater* | update | Create a CredentialUpdater to execute update
|===
-The call-feedback API method(s) has the following set of parameters listed in the table below:
+The sip-credential-list-credential API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| creator | *pathCallSid* | The call sid that uniquely identifies the call | String
-| creator | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathCallSid* | The call sid that uniquely identifies the call | String
-| updater | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *pathCallSid* | The call sid that uniquely identifies the call | String
-| updater | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
+| creator | *password* | The password will not be returned in the response | String
+| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| creator | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| creator | *username* | The username for this credential | String
+| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| deleter | *pathSid* | The unique id that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| fetcher | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| fetcher | *pathSid* | The unique id that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| reader | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| updater | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| updater | *pathSid* | The unique id that identifies the resource to update | String
|===
-In addition to the parameters above, the call-feedback API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-credential-list-credential API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2548,65 +2602,72 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: key
+==== API: sip-domain
-The key API has 4 method(s) which is represented by the following method signatures
+The sip-domain API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String domainName);
-com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String pathAccountSid, String domainName);
-com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.KeyReader reader();
+com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.KeyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainReader reader();
-com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathSid);
----
-The key API is defined in the syntax as follows:
+The sip-domain API is defined in the syntax as follows:
----
-twilio:key/methodName?[parameters]
+twilio:sip-domain/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a KeyDeleter to execute delete
-| *fetcher* | fetch | Create a KeyFetcher to execute fetch
-| *reader* | read | Create a KeyReader to execute read
-| *updater* | update | Create a KeyUpdater to execute update
+| *creator* | create | Create a DomainCreator to execute create
+| *deleter* | delete | Create a DomainDeleter to execute delete
+| *fetcher* | fetch | Create a DomainFetcher to execute fetch
+| *reader* | read | Create a DomainReader to execute read
+| *updater* | update | Create a DomainUpdater to execute update
|===
-The key API method(s) has the following set of parameters listed in the table below:
+The sip-domain API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *domainName* | The unique address on Twilio to route SIP traffic | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
| deleter | *pathSid* | The unique string that identifies the resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the key API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-domain API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2616,51 +2677,69 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number-toll-free
+==== API: sip-domain-credential-list-mapping
-The incoming-phone-number-toll-free API has 2 method(s) which is represented by the following method signatures
+The sip-domain-credential-list-mapping API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathAccountSid, String pathDomainSid, String credentialListSid);
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathDomainSid, String credentialListSid);
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader();
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathAccountSid, String pathDomainSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathDomainSid);
----
-The incoming-phone-number-toll-free API is defined in the syntax as follows:
+The sip-domain-credential-list-mapping API is defined in the syntax as follows:
----
-twilio:incoming-phone-number-toll-free/methodName?[parameters]
+twilio:sip-domain-credential-list-mapping/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a TollFreeCreator to execute create
-| *reader* | read | Create a TollFreeReader to execute read
+| *creator* | create | Create a CredentialListMappingCreator to execute create
+| *deleter* | delete | Create a CredentialListMappingDeleter to execute delete
+| *fetcher* | fetch | Create a CredentialListMappingFetcher to execute fetch
+| *reader* | read | Create a CredentialListMappingReader to execute read
|===
-The incoming-phone-number-toll-free API method(s) has the following set of parameters listed in the table below:
+The sip-domain-credential-list-mapping API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *credentialListSid* | A string that identifies the CredentialList resource to map to the SIP domain | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| creator | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| deleter | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| deleter | *pathSid* | A string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| fetcher | *pathSid* | A string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The unique sid that identifies this account | String
+| reader | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
|===
-In addition to the parameters above, the incoming-phone-number-toll-free API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-domain-credential-list-mapping API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2670,44 +2749,69 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: token
+==== API: sip-domain-ip-access-control-list-mapping
-The token API has 1 method(s) which is represented by the following method signatures
+The sip-domain-ip-access-control-list-mapping API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.TokenCreator creator();
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathAccountSid, String pathDomainSid, String ipAccessControlListSid);
-com.twilio.rest.api.v2010.account.TokenCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathDomainSid, String ipAccessControlListSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathAccountSid, String pathDomainSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathDomainSid);
----
-The token API is defined in the syntax as follows:
+The sip-domain-ip-access-control-list-mapping API is defined in the syntax as follows:
----
-twilio:token/methodName?[parameters]
+twilio:sip-domain-ip-access-control-list-mapping/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a TokenCreator to execute create
+| *creator* | create | Create a IpAccessControlListMappingCreator to execute create
+| *deleter* | delete | Create a IpAccessControlListMappingDeleter to execute delete
+| *fetcher* | fetch | Create a IpAccessControlListMappingFetcher to execute fetch
+| *reader* | read | Create a IpAccessControlListMappingReader to execute read
|===
-The token API method(s) has the following set of parameters listed in the table below:
+The sip-domain-ip-access-control-list-mapping API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *ipAccessControlListSid* | The unique id of the IP access control list to map to the SIP domain | String
+| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| creator | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| deleter | *pathSid* | A 34 character string that uniquely identifies the resource to delete. | String
+| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| fetcher | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| fetcher | *pathSid* | A 34 character string that uniquely identifies the resource to fetch. | String
+| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| reader | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
|===
-In addition to the parameters above, the token API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-domain-ip-access-control-list-mapping API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2717,58 +2821,73 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: short-code
+==== API: sip-ip-access-control-list
-The short-code API has 3 method(s) which is represented by the following method signatures
+The sip-ip-access-control-list API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String friendlyName);
-com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String pathAccountSid, String friendlyName);
-com.twilio.rest.api.v2010.account.ShortCodeReader reader();
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ShortCodeReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader();
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathSid, String friendlyName);
----
-The short-code API is defined in the syntax as follows:
+The sip-ip-access-control-list API is defined in the syntax as follows:
----
-twilio:short-code/methodName?[parameters]
+twilio:sip-ip-access-control-list/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a ShortCodeFetcher to execute fetch
-| *reader* | read | Create a ShortCodeReader to execute read
-| *updater* | update | Create a ShortCodeUpdater to execute update
+| *creator* | create | Create a IpAccessControlListCreator to execute create
+| *deleter* | delete | Create a IpAccessControlListDeleter to execute delete
+| *fetcher* | fetch | Create a IpAccessControlListFetcher to execute fetch
+| *reader* | read | Create a IpAccessControlListReader to execute read
+| *updater* | update | Create a IpAccessControlListUpdater to execute update
|===
-The short-code API method(s) has the following set of parameters listed in the table below:
+The sip-ip-access-control-list API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathSid* | The unique string that identifies this resource | String
+| creator | *friendlyName* | A human readable description of this resource | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathSid* | A string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathSid* | A string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *friendlyName* | A human readable description of this resource | String
+| updater | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *pathSid* | A string that identifies the resource to update | String
|===
-In addition to the parameters above, the short-code API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-ip-access-control-list API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2778,45 +2897,78 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country-toll-free
+==== API: sip-ip-access-control-list-ip-address
-The available-phone-number-country-toll-free API has 1 method(s) which is represented by the following method signatures
+The sip-ip-access-control-list-ip-address API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathAccountSid, String pathIpAccessControlListSid, String friendlyName, String ipAddress);
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathCountryCode);
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathIpAccessControlListSid, String friendlyName, String ipAddress);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathAccountSid, String pathIpAccessControlListSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathIpAccessControlListSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathIpAccessControlListSid, String pathSid);
----
-The available-phone-number-country-toll-free API is defined in the syntax as follows:
+The sip-ip-access-control-list-ip-address API is defined in the syntax as follows:
----
-twilio:available-phone-number-country-toll-free/methodName?[parameters]
+twilio:sip-ip-access-control-list-ip-address/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a TollFreeReader to execute read
+| *creator* | create | Create a IpAddressCreator to execute create
+| *deleter* | delete | Create a IpAddressDeleter to execute delete
+| *fetcher* | fetch | Create a IpAddressFetcher to execute fetch
+| *reader* | read | Create a IpAddressReader to execute read
+| *updater* | update | Create a IpAddressUpdater to execute update
|===
-The available-phone-number-country-toll-free API method(s) has the following set of parameters listed in the table below:
+The sip-ip-access-control-list-ip-address API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
-| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
+| creator | *friendlyName* | A human readable descriptive text for this resource, up to 64 characters long. | String
+| creator | *ipAddress* | An IP address in dotted decimal notation from which you want to accept traffic. Any SIP requests from this IP address will be allowed by Twilio. IPv4 only supported today. | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| creator | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| deleter | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| deleter | *pathSid* | A string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| fetcher | *pathSid* | A string that identifies the IpAddress resource to fetch | String
+| reader | *pathAccountSid* | The unique sid that identifies this account | String
+| reader | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| updater | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| updater | *pathSid* | A string that identifies the IpAddress resource to update | String
|===
-In addition to the parameters above, the available-phone-number-country-toll-free API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-ip-access-control-list-ip-address API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2826,25 +2978,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-monthly
+==== API: token
-The usage-record-monthly API has 1 method(s) which is represented by the following method signatures
+The token API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader();
+com.twilio.rest.api.v2010.account.TokenCreator creator();
-com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.TokenCreator creator(String pathAccountSid);
----
-The usage-record-monthly API is defined in the syntax as follows:
+The token API is defined in the syntax as follows:
----
-twilio:usage-record-monthly/methodName?[parameters]
+twilio:token/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -2853,17 +3005,17 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a MonthlyReader to execute read
+| *creator* | create | Create a TokenCreator to execute create
|===
-The usage-record-monthly API method(s) has the following set of parameters listed in the table below:
+The token API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
|===
-In addition to the parameters above, the usage-record-monthly API can also use from the 23 endpoint query option
+In addition to the parameters above, the token API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2873,73 +3025,58 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-ip-access-control-list
+==== API: transcription
-The sip-ip-access-control-list API has 5 method(s) which is represented by the following method signatures
+The transcription API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String pathAccountSid, String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader();
+com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.TranscriptionReader reader();
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.TranscriptionReader reader(String pathAccountSid);
----
-The sip-ip-access-control-list API is defined in the syntax as follows:
+The transcription API is defined in the syntax as follows:
----
-twilio:sip-ip-access-control-list/methodName?[parameters]
+twilio:transcription/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IpAccessControlListCreator to execute create
-| *deleter* | delete | Create a IpAccessControlListDeleter to execute delete
-| *fetcher* | fetch | Create a IpAccessControlListFetcher to execute fetch
-| *reader* | read | Create a IpAccessControlListReader to execute read
-| *updater* | update | Create a IpAccessControlListUpdater to execute update
+| *deleter* | delete | Create a TranscriptionDeleter to execute delete
+| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
+| *reader* | read | Create a TranscriptionReader to execute read
|===
-The sip-ip-access-control-list API method(s) has the following set of parameters listed in the table below:
+The transcription API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | A human readable description of this resource | String
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathSid* | A string that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathSid* | A string that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *friendlyName* | A human readable description of this resource | String
-| updater | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *pathSid* | A string that identifies the resource to update | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the sip-ip-access-control-list API can also use from the 23 endpoint query option
+In addition to the parameters above, the transcription API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2949,65 +3086,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: connect-app
+==== API: usage-record
-The connect-app API has 4 method(s) which is represented by the following method signatures
+The usage-record API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppReader reader();
-
-com.twilio.rest.api.v2010.account.ConnectAppReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.RecordReader reader();
-com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.RecordReader reader(String pathAccountSid);
----
-The connect-app API is defined in the syntax as follows:
+The usage-record API is defined in the syntax as follows:
----
-twilio:connect-app/methodName?[parameters]
+twilio:usage-record/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a ConnectAppDeleter to execute delete
-| *fetcher* | fetch | Create a ConnectAppFetcher to execute fetch
-| *reader* | read | Create a ConnectAppReader to execute read
-| *updater* | update | Create a ConnectAppUpdater to execute update
+| *reader* | read | Create a RecordReader to execute read
|===
-The connect-app API method(s) has the following set of parameters listed in the table below:
+The usage-record API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the connect-app API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3017,25 +3133,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: address-dependent-phone-number
+==== API: usage-record-all-time
-The address-dependent-phone-number API has 1 method(s) which is represented by the following method signatures
+The usage-record-all-time API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAccountSid, String pathAddressSid);
+com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader();
-com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAddressSid);
+com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader(String pathAccountSid);
----
-The address-dependent-phone-number API is defined in the syntax as follows:
+The usage-record-all-time API is defined in the syntax as follows:
----
-twilio:address-dependent-phone-number/methodName?[parameters]
+twilio:usage-record-all-time/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -3044,18 +3160,17 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a DependentPhoneNumberReader to execute read
+| *reader* | read | Create a AllTimeReader to execute read
|===
-The address-dependent-phone-number API method(s) has the following set of parameters listed in the table below:
+The usage-record-all-time API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathAddressSid* | The SID of the Address resource associated with the phone number | String
|===
-In addition to the parameters above, the address-dependent-phone-number API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-all-time API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3065,65 +3180,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: signing-key
+==== API: usage-record-daily
-The signing-key API has 4 method(s) which is represented by the following method signatures
+The usage-record-daily API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyReader reader();
-
-com.twilio.rest.api.v2010.account.SigningKeyReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.DailyReader reader();
-com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.DailyReader reader(String pathAccountSid);
----
-The signing-key API is defined in the syntax as follows:
+The usage-record-daily API is defined in the syntax as follows:
----
-twilio:signing-key/methodName?[parameters]
+twilio:usage-record-daily/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a SigningKeyDeleter to execute delete
-| *fetcher* | fetch | Create a SigningKeyFetcher to execute fetch
-| *reader* | read | Create a SigningKeyReader to execute read
-| *updater* | update | Create a SigningKeyUpdater to execute update
+| *reader* | read | Create a DailyReader to execute read
|===
-The signing-key API method(s) has the following set of parameters listed in the table below:
+The usage-record-daily API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The account_sid | String
-| deleter | *pathSid* | The sid | String
-| fetcher | *pathAccountSid* | The account_sid | String
-| fetcher | *pathSid* | The sid | String
-| reader | *pathAccountSid* | The account_sid | String
-| updater | *pathAccountSid* | The account_sid | String
-| updater | *pathSid* | The sid | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the signing-key API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-daily API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3133,65 +3227,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: outgoing-caller-id
+==== API: usage-record-last-month
-The outgoing-caller-id API has 4 method(s) which is represented by the following method signatures
+The usage-record-last-month API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader();
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader();
-com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader(String pathAccountSid);
----
-The outgoing-caller-id API is defined in the syntax as follows:
+The usage-record-last-month API is defined in the syntax as follows:
----
-twilio:outgoing-caller-id/methodName?[parameters]
+twilio:usage-record-last-month/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a OutgoingCallerIdDeleter to execute delete
-| *fetcher* | fetch | Create a OutgoingCallerIdFetcher to execute fetch
-| *reader* | read | Create a OutgoingCallerIdReader to execute read
-| *updater* | update | Create a OutgoingCallerIdUpdater to execute update
+| *reader* | read | Create a LastMonthReader to execute read
|===
-The outgoing-caller-id API method(s) has the following set of parameters listed in the table below:
+The usage-record-last-month API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the outgoing-caller-id API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-last-month API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3201,84 +3274,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call
-
-
-The call API has 5 method(s) which is represented by the following method signatures
-(an API method may have multiple signatures due to overloading):
-
-[source,java]
-----
-
-com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
-
-com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathAccountSid, String pathSid);
+==== API: usage-record-monthly
-com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.CallReader reader();
+The usage-record-monthly API has 1 method(s) which is represented by the following method signatures
+(an API method may have multiple signatures due to overloading):
-com.twilio.rest.api.v2010.account.CallReader reader(String pathAccountSid);
+[source,java]
+----
-com.twilio.rest.api.v2010.account.CallUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader();
-com.twilio.rest.api.v2010.account.CallUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader(String pathAccountSid);
----
-The call API is defined in the syntax as follows:
+The usage-record-monthly API is defined in the syntax as follows:
----
-twilio:call/methodName?[parameters]
+twilio:usage-record-monthly/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CallCreator to execute create
-| *deleter* | delete | Create a CallDeleter to execute delete
-| *fetcher* | fetch | Create a CallFetcher to execute fetch
-| *reader* | read | Create a CallReader to execute read
-| *updater* | update | Create a CallUpdater to execute update
+| *reader* | read | Create a MonthlyReader to execute read
|===
-The call API method(s) has the following set of parameters listed in the table below:
+The usage-record-monthly API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *applicationSid* | The SID of the Application resource that will handle the call | String
-| creator | *from* | Twilio number from which to originate the call | Endpoint
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *to* | Phone number, SIP address, or client identifier to call | Endpoint
-| creator | *twiml* | TwiML instructions for the call | Twiml
-| creator | *url* | The absolute URL that returns TwiML for this call | URI
-| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
-| deleter | *pathSid* | The unique string that identifies this resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathSid* | The SID of the Call resource to fetch | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the call API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-monthly API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3288,51 +3321,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number-local
+==== API: usage-record-this-month
-The incoming-phone-number-local API has 2 method(s) which is represented by the following method signatures
+The usage-record-this-month API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader();
+com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader();
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader(String pathAccountSid);
----
-The incoming-phone-number-local API is defined in the syntax as follows:
+The usage-record-this-month API is defined in the syntax as follows:
----
-twilio:incoming-phone-number-local/methodName?[parameters]
+twilio:usage-record-this-month/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a LocalCreator to execute create
-| *reader* | read | Create a LocalReader to execute read
+| *reader* | read | Create a ThisMonthReader to execute read
|===
-The incoming-phone-number-local API method(s) has the following set of parameters listed in the table below:
+The usage-record-this-month API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the incoming-phone-number-local API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-this-month API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3342,25 +3368,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: message-feedback
+==== API: usage-record-today
-The message-feedback API has 1 method(s) which is represented by the following method signatures
+The usage-record-today API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathAccountSid, String pathMessageSid);
+com.twilio.rest.api.v2010.account.usage.record.TodayReader reader();
-com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathMessageSid);
+com.twilio.rest.api.v2010.account.usage.record.TodayReader reader(String pathAccountSid);
----
-The message-feedback API is defined in the syntax as follows:
+The usage-record-today API is defined in the syntax as follows:
----
-twilio:message-feedback/methodName?[parameters]
+twilio:usage-record-today/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -3369,18 +3395,17 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a FeedbackCreator to execute create
+| *reader* | read | Create a TodayReader to execute read
|===
-The message-feedback API method(s) has the following set of parameters listed in the table below:
+The usage-record-today API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *pathMessageSid* | The SID of the Message resource for which the feedback was provided | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the message-feedback API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-today API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3390,58 +3415,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: recording
+==== API: usage-record-yearly
-The recording API has 3 method(s) which is represented by the following method signatures
+The usage-record-yearly API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingReader reader();
+com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader();
-com.twilio.rest.api.v2010.account.RecordingReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader(String pathAccountSid);
----
-The recording API is defined in the syntax as follows:
+The usage-record-yearly API is defined in the syntax as follows:
----
-twilio:recording/methodName?[parameters]
+twilio:usage-record-yearly/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a RecordingDeleter to execute delete
-| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
-| *reader* | read | Create a RecordingReader to execute read
+| *reader* | read | Create a YearlyReader to execute read
|===
-The recording API method(s) has the following set of parameters listed in the table below:
+The usage-record-yearly API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the recording API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-yearly API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3451,51 +3462,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number-mobile
+==== API: usage-record-yesterday
-The incoming-phone-number-mobile API has 2 method(s) which is represented by the following method signatures
+The usage-record-yesterday API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader();
+com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader();
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader(String pathAccountSid);
----
-The incoming-phone-number-mobile API is defined in the syntax as follows:
+The usage-record-yesterday API is defined in the syntax as follows:
----
-twilio:incoming-phone-number-mobile/methodName?[parameters]
+twilio:usage-record-yesterday/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a MobileCreator to execute create
-| *reader* | read | Create a MobileReader to execute read
+| *reader* | read | Create a YesterdayReader to execute read
|===
-The incoming-phone-number-mobile API method(s) has the following set of parameters listed in the table below:
+The usage-record-yesterday API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the incoming-phone-number-mobile API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-yesterday API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3505,50 +3509,74 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: account
+==== API: usage-trigger
-The account API has 2 method(s) which is represented by the following method signatures
+The usage-trigger API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.AccountFetcher fetcher();
+com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(String pathAccountSid, java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
-com.twilio.rest.api.v2010.AccountFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
-com.twilio.rest.api.v2010.AccountUpdater updater();
+com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.AccountUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerReader reader();
+
+com.twilio.rest.api.v2010.account.usage.TriggerReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathSid);
----
-The account API is defined in the syntax as follows:
+The usage-trigger API is defined in the syntax as follows:
----
-twilio:account/methodName?[parameters]
+twilio:usage-trigger/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a AccountFetcher to execute fetch
-| *updater* | update | Create a AccountUpdater to execute update
+| *creator* | create | Create a TriggerCreator to execute create
+| *deleter* | delete | Create a TriggerDeleter to execute delete
+| *fetcher* | fetch | Create a TriggerFetcher to execute fetch
+| *reader* | read | Create a TriggerReader to execute read
+| *updater* | update | Create a TriggerUpdater to execute update
|===
-The account API method(s) has the following set of parameters listed in the table below:
+The usage-trigger API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathSid* | Fetch by unique Account Sid | String
-| updater | *pathSid* | Update by unique Account Sid | String
+| creator | *callbackUrl* | The URL we call when the trigger fires | URI
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *triggerValue* | The usage value at which the trigger should fire | String
+| creator | *usageCategory* | The usage category the trigger watches | UsageCategory
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the account API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-trigger API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3558,73 +3586,45 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-credential-list
+==== API: validation-request
-The sip-credential-list API has 5 method(s) which is represented by the following method signatures
+The validation-request API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String pathAccountSid, String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListReader reader();
-
-com.twilio.rest.api.v2010.account.sip.CredentialListReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(com.twilio.type.PhoneNumber phoneNumber);
----
-The sip-credential-list API is defined in the syntax as follows:
+The validation-request API is defined in the syntax as follows:
----
-twilio:sip-credential-list/methodName?[parameters]
+twilio:validation-request/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CredentialListCreator to execute create
-| *deleter* | delete | Create a CredentialListDeleter to execute delete
-| *fetcher* | fetch | Create a CredentialListFetcher to execute fetch
-| *reader* | read | Create a CredentialListReader to execute read
-| *updater* | update | Create a CredentialListUpdater to execute update
+| *creator* | create | Create a ValidationRequestCreator to execute create
|===
-The sip-credential-list API method(s) has the following set of parameters listed in the table below:
+The validation-request API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | Human readable descriptive text | String
-| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathSid* | Delete by unique credential list Sid | String
-| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| fetcher | *pathSid* | Fetch by unique credential list Sid | String
-| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| updater | *friendlyName* | Human readable descriptive text | String
-| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| updater | *pathSid* | Update by unique credential list Sid | String
+| creator | *pathAccountSid* | The SID of the Account responsible for the new Caller ID | String
+| creator | *phoneNumber* | The phone number to verify in E.164 format | PhoneNumber
|===
-In addition to the parameters above, the sip-credential-list API can also use from the 23 endpoint query option
+In addition to the parameters above, the validation-request API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
diff --git a/components/camel-twilio/src/generated/resources/org/apache/camel/component/twilio/twilio.json b/components/camel-twilio/src/generated/resources/org/apache/camel/component/twilio/twilio.json
index e70c8db..29b7721 100644
--- a/components/camel-twilio/src/generated/resources/org/apache/camel/component/twilio/twilio.json
+++ b/components/camel-twilio/src/generated/resources/org/apache/camel/component/twilio/twilio.json
@@ -66,8 +66,8 @@
"call-recording": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a RecordingCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathAccountSid, String pathCallSid)", "com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathCallSid)" ] }, "deleter": { "description": "Crea [...]
"queue-member": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "fetcher": { "description": "Create a MemberFetcher to execute fetch", "signatures": [ "com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathAccountSid, String pathQueueSid, String pathCallSid)", "com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathQueueSid, String pathCallSid)" ] }, " [...]
"usage-trigger": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a TriggerCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(String pathAccountSid, java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger$UsageCategory usageCategory)", "com.twilio.rest.api.v20 [...]
- "usage-record-all-time": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "reader": { "description": "Create a AllTimeReader to execute read", "signatures": [ "com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader()", "com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader(String pathAccountSid)" ] } } },
"usage-record-last-month": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "reader": { "description": "Create a LastMonthReader to execute read", "signatures": [ "com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader()", "com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader(String pathAccountSid)" ] } } },
+ "usage-record-all-time": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "reader": { "description": "Create a AllTimeReader to execute read", "signatures": [ "com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader()", "com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader(String pathAccountSid)" ] } } },
"recording-transcription": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "deleter": { "description": "Create a TranscriptionDeleter to execute delete", "signatures": [ "com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathAccountSid, String pathRecordingSid, String pathSid)", "com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String [...]
"message": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a MessageCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, String body)", "com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.tw [...]
"call-feedback-summary": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a FeedbackSummaryCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.call.FeedbackSummaryCreator creator(String pathAccountSid, org.joda.time.LocalDate startDate, org.joda.time.LocalDate endDate)", "com.twilio.rest.api.v2010.account.call.FeedbackSummaryCr [...]
@@ -85,8 +85,8 @@
"usage-record": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "reader": { "description": "Create a RecordReader to execute read", "signatures": [ "com.twilio.rest.api.v2010.account.usage.RecordReader reader()", "com.twilio.rest.api.v2010.account.usage.RecordReader reader(String pathAccountSid)" ] } } },
"available-phone-number-country-mobile": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "reader": { "description": "Create a MobileReader to execute read", "signatures": [ "com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathAccountSid, String pathCountryCode)", "com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(Str [...]
"conference-participant": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a ParticipantCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathAccountSid, String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to)", "com.twilio.rest.api.v2010.account [...]
- "notification": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "fetcher": { "description": "Create a NotificationFetcher to execute fetch", "signatures": [ "com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathAccountSid, String pathSid)", "com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathSid)" ] }, "reader": { "description": "Create a Notifica [...]
"recording-add-on-result": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "deleter": { "description": "Create a AddOnResultDeleter to execute delete", "signatures": [ "com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathSid)", "com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathRe [...]
+ "notification": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "fetcher": { "description": "Create a NotificationFetcher to execute fetch", "signatures": [ "com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathAccountSid, String pathSid)", "com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathSid)" ] }, "reader": { "description": "Create a Notifica [...]
"sip-domain-ip-access-control-list-mapping": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a IpAccessControlListMappingCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathAccountSid, String pathDomainSid, String ipAccessControlListSid)", "com.twilio.rest.api.v20 [...]
"sip-domain": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a DomainCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String domainName)", "com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String pathAccountSid, String domainName)" ] }, "deleter": { "description": "Create a DomainDelete [...]
"address": { "description": "", "aliases": [ "^creator$=create", "^deleter$=delete", "^fetcher$=fetch", "^reader$=read", "^updater$=update" ], "methods": { "creator": { "description": "Create a AddressCreator to execute create", "signatures": [ "com.twilio.rest.api.v2010.account.AddressCreator creator(String customerName, String street, String city, String region, String postalCode, String isoCountry)", "com.twilio.rest.api.v2010.account.AddressCreator creator(String pathAccountSid, [...]
@@ -124,8 +124,8 @@
"call-recording": { "methods": { "creator": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that will create the resource", "optional": false }, "pathCallSid": { "kind": "parameter", "displayName": "Path Call Sid", "group": "common", "label": "", "required": false [...]
"queue-member": { "methods": { "fetcher": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resource(s) to fetch", "optional": false }, "pathCallSid": { "kind": "parameter", "displayName": "Path Call Sid", "group": "common", "label": "", "required": [...]
"usage-trigger": { "methods": { "creator": { "properties": { "callbackUrl": { "kind": "parameter", "displayName": "Callback Url", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.net.URI", "deprecated": false, "secret": false, "description": "The URL we call when the trigger fires", "optional": false }, "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", [...]
- "usage-record-all-time": { "methods": { "reader": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resources to read", "optional": false } } } } },
"usage-record-last-month": { "methods": { "reader": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resources to read", "optional": false } } } } },
+ "usage-record-all-time": { "methods": { "reader": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resources to read", "optional": false } } } } },
"recording-transcription": { "methods": { "deleter": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resources to delete", "optional": false }, "pathRecordingSid": { "kind": "parameter", "displayName": "Path Recording Sid", "group": "common", "lab [...]
"message": { "methods": { "creator": { "properties": { "body": { "kind": "parameter", "displayName": "Body", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The text of the message you want to send. Can be up to 1,600 characters in length.", "optional": false }, "from": { "kind": "parameter", "displayName": "From", "group": "common", "label": "", "required": false, "type": "obje [...]
"call-feedback-summary": { "methods": { "creator": { "properties": { "endDate": { "kind": "parameter", "displayName": "End Date", "group": "common", "label": "", "required": false, "type": "object", "javaType": "org.joda.time.LocalDate", "deprecated": false, "secret": false, "description": "Only include feedback given on or before this date", "optional": false }, "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": fa [...]
@@ -143,8 +143,8 @@
"usage-record": { "methods": { "reader": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resources to read", "optional": false } } } } },
"available-phone-number-country-mobile": { "methods": { "reader": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account requesting the AvailablePhoneNumber resources", "optional": false }, "pathCountryCode": { "kind": "parameter", "displayName": "Path Country Code", "gr [...]
"conference-participant": { "methods": { "creator": { "properties": { "from": { "kind": "parameter", "displayName": "From", "group": "common", "label": "", "required": false, "type": "object", "javaType": "com.twilio.type.PhoneNumber", "deprecated": false, "secret": false, "description": "The phone number, Client identifier, or username portion of SIP address that made this call.", "optional": false }, "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group [...]
- "notification": { "methods": { "fetcher": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resource to fetch", "optional": false }, "pathSid": { "kind": "parameter", "displayName": "Path Sid", "group": "common", "label": "", "required": false, "typ [...]
"recording-add-on-result": { "methods": { "deleter": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resources to delete", "optional": false }, "pathReferenceSid": { "kind": "parameter", "displayName": "Path Reference Sid", "group": "common", "lab [...]
+ "notification": { "methods": { "fetcher": { "properties": { "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The SID of the Account that created the resource to fetch", "optional": false }, "pathSid": { "kind": "parameter", "displayName": "Path Sid", "group": "common", "label": "", "required": false, "typ [...]
"sip-domain-ip-access-control-list-mapping": { "methods": { "creator": { "properties": { "ipAccessControlListSid": { "kind": "parameter", "displayName": "Ip Access Control List Sid", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The unique id of the IP access control list to map to the SIP domain", "optional": false }, "pathAccountSid": { "kind": "parameter", "displayName": "P [...]
"sip-domain": { "methods": { "creator": { "properties": { "domainName": { "kind": "parameter", "displayName": "Domain Name", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The unique address on Twilio to route SIP traffic", "optional": false }, "pathAccountSid": { "kind": "parameter", "displayName": "Path Account Sid", "group": "common", "label": "", "required": false, "type": [...]
"address": { "methods": { "creator": { "properties": { "city": { "kind": "parameter", "displayName": "City", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", "deprecated": false, "secret": false, "description": "The city of the new address", "optional": false }, "customerName": { "kind": "parameter", "displayName": "Customer Name", "group": "common", "label": "", "required": false, "type": "string", "javaType": "java.lang.String", " [...]
diff --git a/components/camel-twilio/src/main/docs/twilio-component.adoc b/components/camel-twilio/src/main/docs/twilio-component.adoc
index 492a5cf..808161b 100644
--- a/components/camel-twilio/src/main/docs/twilio-component.adoc
+++ b/components/camel-twilio/src/main/docs/twilio-component.adoc
@@ -116,125 +116,111 @@ There are 56 API groups as listed in the table below:
[width="100%",cols="2,8",options="header"]
|===
| API Name | Description
-| *recording-add-on-result-payload* |
-| *usage-record-today* |
+| *account* |
+| *address* |
+| *address-dependent-phone-number* |
+| *application* |
+| *available-phone-number-country* |
| *available-phone-number-country-local* |
-| *call-recording* |
-| *queue-member* |
-| *usage-trigger* |
-| *usage-record-all-time* |
-| *usage-record-last-month* |
-| *recording-transcription* |
-| *message* |
+| *available-phone-number-country-mobile* |
+| *available-phone-number-country-toll-free* |
+| *call* |
+| *call-feedback* |
| *call-feedback-summary* |
-| *sip-credential-list-credential* |
-| *new-key* |
-| *incoming-phone-number* |
| *call-notification* |
-| *validation-request* |
-| *usage-record-yesterday* |
-| *usage-record-this-month* |
-| *new-signing-key* |
+| *call-recording* |
| *conference* |
-| *usage-record-daily* |
-| *application* |
-| *usage-record* |
-| *available-phone-number-country-mobile* |
| *conference-participant* |
+| *connect-app* |
+| *incoming-phone-number* |
+| *incoming-phone-number-local* |
+| *incoming-phone-number-mobile* |
+| *incoming-phone-number-toll-free* |
+| *key* |
+| *message* |
+| *message-feedback* |
+| *message-media* |
+| *new-key* |
+| *new-signing-key* |
| *notification* |
+| *outgoing-caller-id* |
+| *queue* |
+| *queue-member* |
+| *recording* |
| *recording-add-on-result* |
-| *sip-domain-ip-access-control-list-mapping* |
+| *recording-add-on-result-payload* |
+| *recording-transcription* |
+| *short-code* |
+| *signing-key* |
+| *sip-credential-list* |
+| *sip-credential-list-credential* |
| *sip-domain* |
-| *address* |
-| *message-media* |
-| *sip-ip-access-control-list-ip-address* |
-| *available-phone-number-country* |
-| *usage-record-yearly* |
-| *queue* |
-| *transcription* |
| *sip-domain-credential-list-mapping* |
-| *call-feedback* |
-| *key* |
-| *incoming-phone-number-toll-free* |
+| *sip-domain-ip-access-control-list-mapping* |
+| *sip-ip-access-control-list* |
+| *sip-ip-access-control-list-ip-address* |
| *token* |
-| *short-code* |
-| *available-phone-number-country-toll-free* |
+| *transcription* |
+| *usage-record* |
+| *usage-record-all-time* |
+| *usage-record-daily* |
+| *usage-record-last-month* |
| *usage-record-monthly* |
-| *sip-ip-access-control-list* |
-| *connect-app* |
-| *address-dependent-phone-number* |
-| *signing-key* |
-| *outgoing-caller-id* |
-| *call* |
-| *incoming-phone-number-local* |
-| *message-feedback* |
-| *recording* |
-| *incoming-phone-number-mobile* |
-| *account* |
-| *sip-credential-list* |
+| *usage-record-this-month* |
+| *usage-record-today* |
+| *usage-record-yearly* |
+| *usage-record-yesterday* |
+| *usage-trigger* |
+| *validation-request* |
|===
Each API is documented in the following sections to come.
-==== API: recording-add-on-result-payload
+==== API: account
-The recording-add-on-result-payload API has 3 method(s) which is represented by the following method signatures
+The account API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+com.twilio.rest.api.v2010.AccountFetcher fetcher();
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+com.twilio.rest.api.v2010.AccountFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid);
+com.twilio.rest.api.v2010.AccountUpdater updater();
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathReferenceSid, String pathAddOnResultSid);
+com.twilio.rest.api.v2010.AccountUpdater updater(String pathSid);
----
-The recording-add-on-result-payload API is defined in the syntax as follows:
+The account API is defined in the syntax as follows:
----
-twilio:recording-add-on-result-payload/methodName?[parameters]
+twilio:account/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a PayloadDeleter to execute delete
-| *fetcher* | fetch | Create a PayloadFetcher to execute fetch
-| *reader* | read | Create a PayloadReader to execute read
+| *fetcher* | fetch | Create a AccountFetcher to execute fetch
+| *updater* | update | Create a AccountUpdater to execute update
|===
-The recording-add-on-result-payload API method(s) has the following set of parameters listed in the table below:
+The account API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| deleter | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| fetcher | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
-| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| reader | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
+| fetcher | *pathSid* | Fetch by unique Account Sid | String
+| updater | *pathSid* | Update by unique Account Sid | String
|===
-In addition to the parameters above, the recording-add-on-result-payload API can also use from the 23 endpoint query option
+In addition to the parameters above, the account API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -244,44 +230,77 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-today
+==== API: address
-The usage-record-today API has 1 method(s) which is represented by the following method signatures
+The address API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.TodayReader reader();
+com.twilio.rest.api.v2010.account.AddressCreator creator(String customerName, String street, String city, String region, String postalCode, String isoCountry);
-com.twilio.rest.api.v2010.account.usage.record.TodayReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.AddressCreator creator(String pathAccountSid, String customerName, String street, String city, String region, String postalCode, String isoCountry);
+
+com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressReader reader();
+
+com.twilio.rest.api.v2010.account.AddressReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathSid);
----
-The usage-record-today API is defined in the syntax as follows:
+The address API is defined in the syntax as follows:
----
-twilio:usage-record-today/methodName?[parameters]
+twilio:address/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a TodayReader to execute read
+| *creator* | create | Create a AddressCreator to execute create
+| *deleter* | delete | Create a AddressDeleter to execute delete
+| *fetcher* | fetch | Create a AddressFetcher to execute fetch
+| *reader* | read | Create a AddressReader to execute read
+| *updater* | update | Create a AddressUpdater to execute update
|===
-The usage-record-today API method(s) has the following set of parameters listed in the table below:
+The address API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *city* | The city of the new address | String
+| creator | *customerName* | The name to associate with the new address | String
+| creator | *isoCountry* | The ISO country code of the new address | String
+| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Address resource | String
+| creator | *postalCode* | The postal code of the new address | String
+| creator | *region* | The state or region of the new address | String
+| creator | *street* | The number and street address of the new address | String
+| deleter | *pathAccountSid* | The SID of the Account that is responsible for the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that is responsible for this address | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that is responsible for this address | String
+| updater | *pathAccountSid* | The SID of the Account that is responsible for the resource to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the usage-record-today API can also use from the 23 endpoint query option
+In addition to the parameters above, the address API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -291,25 +310,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country-local
+==== API: address-dependent-phone-number
-The available-phone-number-country-local API has 1 method(s) which is represented by the following method signatures
+The address-dependent-phone-number API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAccountSid, String pathAddressSid);
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathCountryCode);
+com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAddressSid);
----
-The available-phone-number-country-local API is defined in the syntax as follows:
+The address-dependent-phone-number API is defined in the syntax as follows:
----
-twilio:available-phone-number-country-local/methodName?[parameters]
+twilio:address-dependent-phone-number/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -318,18 +337,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a LocalReader to execute read
+| *reader* | read | Create a DependentPhoneNumberReader to execute read
|===
-The available-phone-number-country-local API method(s) has the following set of parameters listed in the table below:
+The address-dependent-phone-number API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
-| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAddressSid* | The SID of the Address resource associated with the phone number | String
|===
-In addition to the parameters above, the available-phone-number-country-local API can also use from the 23 endpoint query option
+In addition to the parameters above, the address-dependent-phone-number API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -339,41 +358,41 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call-recording
+==== API: application
-The call-recording API has 5 method(s) which is represented by the following method signatures
+The application API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationCreator creator();
-com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationCreator creator(String pathAccountSid);
-com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationReader reader();
-com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathAccountSid, String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathSid);
----
-The call-recording API is defined in the syntax as follows:
+The application API is defined in the syntax as follows:
----
-twilio:call-recording/methodName?[parameters]
+twilio:application/methodName?[parameters]
----
The 5 method(s) is listed in the table below.
@@ -382,34 +401,28 @@ The 5 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a RecordingCreator to execute create
-| *deleter* | delete | Create a RecordingDeleter to execute delete
-| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
-| *reader* | read | Create a RecordingReader to execute read
-| *updater* | update | Create a RecordingUpdater to execute update
+| *creator* | create | Create a ApplicationCreator to execute create
+| *deleter* | delete | Create a ApplicationDeleter to execute delete
+| *fetcher* | fetch | Create a ApplicationFetcher to execute fetch
+| *reader* | read | Create a ApplicationReader to execute read
+| *updater* | update | Create a ApplicationUpdater to execute update
|===
-The call-recording API method(s) has the following set of parameters listed in the table below:
+The application API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *pathCallSid* | The SID of the Call to associate the resource with | String
| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathCallSid* | The SID of the Call to associate the resource with | String
| deleter | *pathSid* | The unique string that identifies the resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathCallSid* | The SID of the Call to associate the resource with | String
| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathCallSid* | The SID of the Call to associate the resource with | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
-| updater | *pathCallSid* | The SID of the Call to associate the resource with | String
+| updater | *pathAccountSid* | The SID of the Account that will create the resource | String
| updater | *pathSid* | The unique string that identifies the resource | String
-| updater | *status* | The new status of the recording | Status
|===
-In addition to the parameters above, the call-recording API can also use from the 23 endpoint query option
+In addition to the parameters above, the application API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -419,139 +432,99 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: queue-member
+==== API: available-phone-number-country
-The queue-member API has 3 method(s) which is represented by the following method signatures
+The available-phone-number-country API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathAccountSid, String pathQueueSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathQueueSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathAccountSid, String pathQueueSid);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathQueueSid);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathCountryCode);
-com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathAccountSid, String pathQueueSid, String pathCallSid, java.net.URI url);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader();
-com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathQueueSid, String pathCallSid, java.net.URI url);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader(String pathAccountSid);
----
-The queue-member API is defined in the syntax as follows:
+The available-phone-number-country API is defined in the syntax as follows:
----
-twilio:queue-member/methodName?[parameters]
+twilio:available-phone-number-country/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a MemberFetcher to execute fetch
-| *reader* | read | Create a MemberReader to execute read
-| *updater* | update | Create a MemberUpdater to execute update
+| *fetcher* | fetch | Create a AvailablePhoneNumberCountryFetcher to execute fetch
+| *reader* | read | Create a AvailablePhoneNumberCountryReader to execute read
|===
-The queue-member API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathCallSid* | The Call SID of the resource(s) to fetch | String
-| fetcher | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| reader | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathCallSid* | The Call SID of the resource(s) to update | String
-| updater | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| updater | *url* | The absolute URL of the Queue resource | URI
+| fetcher | *pathAccountSid* | The SID of the Account requesting the available phone number Country resource | String
+| fetcher | *pathCountryCode* | The ISO country code of the country to fetch available phone number information about | String
+| reader | *pathAccountSid* | The SID of the Account requesting the available phone number Country resources | String
|===
-In addition to the parameters above, the queue-member API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
-The message header name must be of the format `CamelTwilio.parameter`.
-The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
-would override a `CamelTwilio.myParameterNameHere` header.
-
-
-
-==== API: usage-trigger
-
-
-The usage-trigger API has 5 method(s) which is represented by the following method signatures
-(an API method may have multiple signatures due to overloading):
-
-[source,java]
-----
-
-com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(String pathAccountSid, java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
-
-com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
+The message header name must be of the format `CamelTwilio.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelTwilio.myParameterNameHere` header.
-com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathAccountSid, String pathSid);
+==== API: available-phone-number-country-local
-com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerReader reader();
+The available-phone-number-country-local API has 1 method(s) which is represented by the following method signatures
+(an API method may have multiple signatures due to overloading):
-com.twilio.rest.api.v2010.account.usage.TriggerReader reader(String pathAccountSid);
+[source,java]
+----
-com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathCountryCode);
----
-The usage-trigger API is defined in the syntax as follows:
+The available-phone-number-country-local API is defined in the syntax as follows:
----
-twilio:usage-trigger/methodName?[parameters]
+twilio:available-phone-number-country-local/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a TriggerCreator to execute create
-| *deleter* | delete | Create a TriggerDeleter to execute delete
-| *fetcher* | fetch | Create a TriggerFetcher to execute fetch
-| *reader* | read | Create a TriggerReader to execute read
-| *updater* | update | Create a TriggerUpdater to execute update
+| *reader* | read | Create a LocalReader to execute read
|===
-The usage-trigger API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country-local API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *callbackUrl* | The URL we call when the trigger fires | URI
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *triggerValue* | The usage value at which the trigger should fire | String
-| creator | *usageCategory* | The usage category the trigger watches | UsageCategory
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
+| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
|===
-In addition to the parameters above, the usage-trigger API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country-local API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -561,25 +534,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-all-time
+==== API: available-phone-number-country-mobile
-The usage-record-all-time API has 1 method(s) which is represented by the following method signatures
+The available-phone-number-country-mobile API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader();
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathCountryCode);
----
-The usage-record-all-time API is defined in the syntax as follows:
+The available-phone-number-country-mobile API is defined in the syntax as follows:
----
-twilio:usage-record-all-time/methodName?[parameters]
+twilio:available-phone-number-country-mobile/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -588,17 +561,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a AllTimeReader to execute read
+| *reader* | read | Create a MobileReader to execute read
|===
-The usage-record-all-time API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country-mobile API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
+| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
|===
-In addition to the parameters above, the usage-record-all-time API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country-mobile API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -608,25 +582,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-last-month
+==== API: available-phone-number-country-toll-free
-The usage-record-last-month API has 1 method(s) which is represented by the following method signatures
+The available-phone-number-country-toll-free API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader();
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathCountryCode);
----
-The usage-record-last-month API is defined in the syntax as follows:
+The available-phone-number-country-toll-free API is defined in the syntax as follows:
----
-twilio:usage-record-last-month/methodName?[parameters]
+twilio:available-phone-number-country-toll-free/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -635,17 +609,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a LastMonthReader to execute read
+| *reader* | read | Create a TollFreeReader to execute read
|===
-The usage-record-last-month API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country-toll-free API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
+| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
|===
-In addition to the parameters above, the usage-record-last-month API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country-toll-free API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -655,61 +630,84 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: recording-transcription
+==== API: call
-The recording-transcription API has 3 method(s) which is represented by the following method signatures
+The call API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathAccountSid, String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathAccountSid, String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
-com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathRecordingSid, String pathSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathAccountSid, String pathRecordingSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathRecordingSid);
+com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
+
+com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.CallReader reader();
+
+com.twilio.rest.api.v2010.account.CallReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.CallUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.CallUpdater updater(String pathSid);
----
-The recording-transcription API is defined in the syntax as follows:
+The call API is defined in the syntax as follows:
----
-twilio:recording-transcription/methodName?[parameters]
+twilio:call/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a TranscriptionDeleter to execute delete
-| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
-| *reader* | read | Create a TranscriptionReader to execute read
+| *creator* | create | Create a CallCreator to execute create
+| *deleter* | delete | Create a CallDeleter to execute delete
+| *fetcher* | fetch | Create a CallFetcher to execute fetch
+| *reader* | read | Create a CallReader to execute read
+| *updater* | update | Create a CallUpdater to execute update
|===
-The recording-transcription API method(s) has the following set of parameters listed in the table below:
+The call API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
+| creator | *applicationSid* | The SID of the Application resource that will handle the call | String
+| creator | *from* | Twilio number from which to originate the call | Endpoint
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *to* | Phone number, SIP address, or client identifier to call | Endpoint
+| creator | *twiml* | TwiML instructions for the call | Twiml
+| creator | *url* | The absolute URL that returns TwiML for this call | URI
+| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
+| deleter | *pathSid* | The unique string that identifies this resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathSid* | The SID of the Call resource to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the recording-transcription API can also use from the 23 endpoint query option
+In addition to the parameters above, the call API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -719,89 +717,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: message
+==== API: call-feedback
-The message API has 5 method(s) which is represented by the following method signatures
+The call-feedback API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-
-com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-
-com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathAccountSid, String pathCallSid, Integer qualityScore);
-com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathCallSid, Integer qualityScore);
-com.twilio.rest.api.v2010.account.MessageReader reader();
+com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathAccountSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.MessageReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathCallSid);
-com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathAccountSid, String pathSid, String body);
+com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathAccountSid, String pathCallSid, Integer qualityScore);
-com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathSid, String body);
+com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathCallSid, Integer qualityScore);
----
-The message API is defined in the syntax as follows:
+The call-feedback API is defined in the syntax as follows:
----
-twilio:message/methodName?[parameters]
+twilio:call-feedback/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a MessageCreator to execute create
-| *deleter* | delete | Create a MessageDeleter to execute delete
-| *fetcher* | fetch | Create a MessageFetcher to execute fetch
-| *reader* | read | Create a MessageReader to execute read
-| *updater* | update | Create a MessageUpdater to execute update
+| *creator* | create | Create a FeedbackCreator to execute create
+| *fetcher* | fetch | Create a FeedbackFetcher to execute fetch
+| *updater* | update | Create a FeedbackUpdater to execute update
|===
-The message API method(s) has the following set of parameters listed in the table below:
+The call-feedback API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *body* | The text of the message you want to send. Can be up to 1,600 characters in length. | String
-| creator | *from* | The phone number that initiated the message | PhoneNumber
-| creator | *mediaUrl* | The URL of the media to send with the message | List
-| creator | *messagingServiceSid* | The SID of the Messaging Service you want to associate with the message | String
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *to* | The destination phone number | PhoneNumber
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *body* | The text of the message you want to send | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| creator | *pathCallSid* | The call sid that uniquely identifies the call | String
+| creator | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathCallSid* | The call sid that uniquely identifies the call | String
+| updater | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *pathCallSid* | The call sid that uniquely identifies the call | String
+| updater | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
|===
-In addition to the parameters above, the message API can also use from the 23 endpoint query option
+In addition to the parameters above, the call-feedback API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -874,78 +844,53 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-credential-list-credential
+==== API: call-notification
-The sip-credential-list-credential API has 5 method(s) which is represented by the following method signatures
+The call-notification API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathAccountSid, String pathCredentialListSid, String username, String password);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathCredentialListSid, String username, String password);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathAccountSid, String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathAccountSid, String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathCredentialListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathAccountSid, String pathCredentialListSid);
+com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathCredentialListSid);
+com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathCallSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathAccountSid, String pathCredentialListSid, String pathSid);
+com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathAccountSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathCredentialListSid, String pathSid);
+com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathCallSid);
----
-The sip-credential-list-credential API is defined in the syntax as follows:
+The call-notification API is defined in the syntax as follows:
----
-twilio:sip-credential-list-credential/methodName?[parameters]
+twilio:call-notification/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CredentialCreator to execute create
-| *deleter* | delete | Create a CredentialDeleter to execute delete
-| *fetcher* | fetch | Create a CredentialFetcher to execute fetch
-| *reader* | read | Create a CredentialReader to execute read
-| *updater* | update | Create a CredentialUpdater to execute update
+| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
+| *reader* | read | Create a NotificationReader to execute read
|===
-The sip-credential-list-credential API method(s) has the following set of parameters listed in the table below:
+The call-notification API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *password* | The password will not be returned in the response | String
-| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| creator | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| creator | *username* | The username for this credential | String
-| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| deleter | *pathSid* | The unique id that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| fetcher | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| fetcher | *pathSid* | The unique id that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| reader | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| updater | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
-| updater | *pathSid* | The unique id that identifies the resource to update | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathCallSid* | The Call SID of the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathCallSid* | The Call SID of the resource to fetch | String
|===
-In addition to the parameters above, the sip-credential-list-credential API can also use from the 23 endpoint query option
+In addition to the parameters above, the call-notification API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -955,44 +900,77 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: new-key
+==== API: call-recording
-The new-key API has 1 method(s) which is represented by the following method signatures
+The call-recording API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.NewKeyCreator creator();
+com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathAccountSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.NewKeyCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathCallSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathAccountSid, String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathCallSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathAccountSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathCallSid);
+
+com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathAccountSid, String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+
+com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
----
-The new-key API is defined in the syntax as follows:
+The call-recording API is defined in the syntax as follows:
----
-twilio:new-key/methodName?[parameters]
+twilio:call-recording/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a NewKeyCreator to execute create
+| *creator* | create | Create a RecordingCreator to execute create
+| *deleter* | delete | Create a RecordingDeleter to execute delete
+| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
+| *reader* | read | Create a RecordingReader to execute read
+| *updater* | update | Create a RecordingUpdater to execute update
|===
-The new-key API method(s) has the following set of parameters listed in the table below:
+The call-recording API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *pathCallSid* | The SID of the Call to associate the resource with | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathCallSid* | The SID of the Call to associate the resource with | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathCallSid* | The SID of the Call to associate the resource with | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathCallSid* | The SID of the Call to associate the resource with | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
+| updater | *pathCallSid* | The SID of the Call to associate the resource with | String
+| updater | *pathSid* | The unique string that identifies the resource | String
+| updater | *status* | The new status of the recording | Status
|===
-In addition to the parameters above, the new-key API can also use from the 23 endpoint query option
+In addition to the parameters above, the call-recording API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1002,77 +980,58 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number
+==== API: conference
-The incoming-phone-number API has 5 method(s) which is represented by the following method signatures
+The conference API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String areaCode);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, String areaCode);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader();
+com.twilio.rest.api.v2010.account.ConferenceReader reader();
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.ConferenceReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathSid);
----
-The incoming-phone-number API is defined in the syntax as follows:
+The conference API is defined in the syntax as follows:
----
-twilio:incoming-phone-number/methodName?[parameters]
+twilio:conference/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IncomingPhoneNumberCreator to execute create
-| *deleter* | delete | Create a IncomingPhoneNumberDeleter to execute delete
-| *fetcher* | fetch | Create a IncomingPhoneNumberFetcher to execute fetch
-| *reader* | read | Create a IncomingPhoneNumberReader to execute read
-| *updater* | update | Create a IncomingPhoneNumberUpdater to execute update
+| *fetcher* | fetch | Create a ConferenceFetcher to execute fetch
+| *reader* | read | Create a ConferenceReader to execute read
+| *updater* | update | Create a ConferenceUpdater to execute update
|===
-The incoming-phone-number API method(s) has the following set of parameters listed in the table below:
+The conference API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *areaCode* | The desired area code for the new phone number | String
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the incoming-phone-number API can also use from the 23 endpoint query option
+In addition to the parameters above, the conference API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1082,53 +1041,78 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call-notification
+==== API: conference-participant
-The call-notification API has 2 method(s) which is represented by the following method signatures
+The conference-participant API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathAccountSid, String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-com.twilio.rest.api.v2010.account.call.NotificationFetcher fetcher(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathAccountSid, String pathConferenceSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.call.NotificationReader reader(String pathCallSid);
+com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathAccountSid, String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathAccountSid, String pathConferenceSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathConferenceSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathAccountSid, String pathConferenceSid, String pathCallSid);
+
+com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathConferenceSid, String pathCallSid);
----
-The call-notification API is defined in the syntax as follows:
+The conference-participant API is defined in the syntax as follows:
----
-twilio:call-notification/methodName?[parameters]
+twilio:conference-participant/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
-| *reader* | read | Create a NotificationReader to execute read
+| *creator* | create | Create a ParticipantCreator to execute create
+| *deleter* | delete | Create a ParticipantDeleter to execute delete
+| *fetcher* | fetch | Create a ParticipantFetcher to execute fetch
+| *reader* | read | Create a ParticipantReader to execute read
+| *updater* | update | Create a ParticipantUpdater to execute update
|===
-The call-notification API method(s) has the following set of parameters listed in the table below:
+The conference-participant API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *from* | The phone number, Client identifier, or username portion of SIP address that made this call. | PhoneNumber
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *pathConferenceSid* | The SID of the participant's conference | String
+| creator | *to* | The phone number, SIP address or Client identifier that received this call. | PhoneNumber
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathCallSid* | The Call SID or URL encoded label of the participant to delete | String
+| deleter | *pathConferenceSid* | The SID of the participant's conference | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathCallSid* | The Call SID of the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathCallSid* | The Call SID or URL encoded label of the participant to fetch | String
+| fetcher | *pathConferenceSid* | The SID of the participant's conference | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathCallSid* | The Call SID of the resource to fetch | String
+| reader | *pathConferenceSid* | The SID of the participant's conference | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathCallSid* | The Call SID or URL encoded label of the participant to update | String
+| updater | *pathConferenceSid* | The SID of the participant's conference | String
|===
-In addition to the parameters above, the call-notification API can also use from the 23 endpoint query option
+In addition to the parameters above, the conference-participant API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1138,45 +1122,65 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: validation-request
+==== API: connect-app
-The validation-request API has 1 method(s) which is represented by the following method signatures
+The connect-app API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppReader reader();
+
+com.twilio.rest.api.v2010.account.ConnectAppReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathSid);
----
-The validation-request API is defined in the syntax as follows:
+The connect-app API is defined in the syntax as follows:
----
-twilio:validation-request/methodName?[parameters]
+twilio:connect-app/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a ValidationRequestCreator to execute create
+| *deleter* | delete | Create a ConnectAppDeleter to execute delete
+| *fetcher* | fetch | Create a ConnectAppFetcher to execute fetch
+| *reader* | read | Create a ConnectAppReader to execute read
+| *updater* | update | Create a ConnectAppUpdater to execute update
|===
-The validation-request API method(s) has the following set of parameters listed in the table below:
+The connect-app API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account responsible for the new Caller ID | String
-| creator | *phoneNumber* | The phone number to verify in E.164 format | PhoneNumber
+| deleter | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the validation-request API can also use from the 23 endpoint query option
+In addition to the parameters above, the connect-app API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1186,44 +1190,77 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-yesterday
+==== API: incoming-phone-number
-The usage-record-yesterday API has 1 method(s) which is represented by the following method signatures
+The incoming-phone-number API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader();
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String areaCode);
-com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, String areaCode);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader();
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.IncomingPhoneNumberUpdater updater(String pathSid);
----
-The usage-record-yesterday API is defined in the syntax as follows:
+The incoming-phone-number API is defined in the syntax as follows:
----
-twilio:usage-record-yesterday/methodName?[parameters]
+twilio:incoming-phone-number/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a YesterdayReader to execute read
+| *creator* | create | Create a IncomingPhoneNumberCreator to execute create
+| *deleter* | delete | Create a IncomingPhoneNumberDeleter to execute delete
+| *fetcher* | fetch | Create a IncomingPhoneNumberFetcher to execute fetch
+| *reader* | read | Create a IncomingPhoneNumberReader to execute read
+| *updater* | update | Create a IncomingPhoneNumberUpdater to execute update
|===
-The usage-record-yesterday API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *areaCode* | The desired area code for the new phone number | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the usage-record-yesterday API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1233,44 +1270,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-this-month
+==== API: incoming-phone-number-local
-The usage-record-this-month API has 1 method(s) which is represented by the following method signatures
+The incoming-phone-number-local API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader();
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader();
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader(String pathAccountSid);
----
-The usage-record-this-month API is defined in the syntax as follows:
+The incoming-phone-number-local API is defined in the syntax as follows:
----
-twilio:usage-record-this-month/methodName?[parameters]
+twilio:incoming-phone-number-local/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a ThisMonthReader to execute read
+| *creator* | create | Create a LocalCreator to execute create
+| *reader* | read | Create a LocalReader to execute read
|===
-The usage-record-this-month API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number-local API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the usage-record-this-month API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number-local API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1280,44 +1324,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: new-signing-key
+==== API: incoming-phone-number-mobile
-The new-signing-key API has 1 method(s) which is represented by the following method signatures
+The incoming-phone-number-mobile API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator();
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader();
+
+com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader(String pathAccountSid);
----
-The new-signing-key API is defined in the syntax as follows:
+The incoming-phone-number-mobile API is defined in the syntax as follows:
----
-twilio:new-signing-key/methodName?[parameters]
+twilio:incoming-phone-number-mobile/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a NewSigningKeyCreator to execute create
+| *creator* | create | Create a MobileCreator to execute create
+| *reader* | read | Create a MobileReader to execute read
|===
-The new-signing-key API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number-mobile API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the new-signing-key API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number-mobile API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1327,58 +1378,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: conference
+==== API: incoming-phone-number-toll-free
-The conference API has 3 method(s) which is represented by the following method signatures
+The incoming-phone-number-toll-free API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.ConferenceFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.ConferenceReader reader();
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.ConferenceReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader();
-com.twilio.rest.api.v2010.account.ConferenceUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader(String pathAccountSid);
----
-The conference API is defined in the syntax as follows:
+The incoming-phone-number-toll-free API is defined in the syntax as follows:
----
-twilio:conference/methodName?[parameters]
+twilio:incoming-phone-number-toll-free/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a ConferenceFetcher to execute fetch
-| *reader* | read | Create a ConferenceReader to execute read
-| *updater* | update | Create a ConferenceUpdater to execute update
+| *creator* | create | Create a TollFreeCreator to execute create
+| *reader* | read | Create a TollFreeReader to execute read
|===
-The conference API method(s) has the following set of parameters listed in the table below:
+The incoming-phone-number-toll-free API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathSid* | The unique string that identifies this resource | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the conference API can also use from the 23 endpoint query option
+In addition to the parameters above, the incoming-phone-number-toll-free API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1388,44 +1432,65 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-daily
+==== API: key
-The usage-record-daily API has 1 method(s) which is represented by the following method signatures
+The key API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.DailyReader reader();
+com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.usage.record.DailyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyReader reader();
+
+com.twilio.rest.api.v2010.account.KeyReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathSid);
----
-The usage-record-daily API is defined in the syntax as follows:
+The key API is defined in the syntax as follows:
----
-twilio:usage-record-daily/methodName?[parameters]
+twilio:key/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a DailyReader to execute read
+| *deleter* | delete | Create a KeyDeleter to execute delete
+| *fetcher* | fetch | Create a KeyFetcher to execute fetch
+| *reader* | read | Create a KeyReader to execute read
+| *updater* | update | Create a KeyUpdater to execute update
|===
-The usage-record-daily API method(s) has the following set of parameters listed in the table below:
+The key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the usage-record-daily API can also use from the 23 endpoint query option
+In addition to the parameters above, the key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1435,41 +1500,53 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: application
+==== API: message
-The application API has 5 method(s) which is represented by the following method signatures
+The message API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ApplicationCreator creator();
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-com.twilio.rest.api.v2010.account.ApplicationCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, String body);
-com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, String messagingServiceSid, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationReader reader();
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, String body);
-com.twilio.rest.api.v2010.account.ApplicationReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.MessageCreator creator(com.twilio.type.PhoneNumber to, com.twilio.type.PhoneNumber from, java.util.List<java.net.URI> mediaUrl);
-com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.MessageDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.MessageFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.MessageReader reader();
+
+com.twilio.rest.api.v2010.account.MessageReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathAccountSid, String pathSid, String body);
+
+com.twilio.rest.api.v2010.account.MessageUpdater updater(String pathSid, String body);
----
-The application API is defined in the syntax as follows:
+The message API is defined in the syntax as follows:
----
-twilio:application/methodName?[parameters]
+twilio:message/methodName?[parameters]
----
The 5 method(s) is listed in the table below.
@@ -1478,28 +1555,34 @@ The 5 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a ApplicationCreator to execute create
-| *deleter* | delete | Create a ApplicationDeleter to execute delete
-| *fetcher* | fetch | Create a ApplicationFetcher to execute fetch
-| *reader* | read | Create a ApplicationReader to execute read
-| *updater* | update | Create a ApplicationUpdater to execute update
+| *creator* | create | Create a MessageCreator to execute create
+| *deleter* | delete | Create a MessageDeleter to execute delete
+| *fetcher* | fetch | Create a MessageFetcher to execute fetch
+| *reader* | read | Create a MessageReader to execute read
+| *updater* | update | Create a MessageUpdater to execute update
|===
-The application API method(s) has the following set of parameters listed in the table below:
+The message API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *body* | The text of the message you want to send. Can be up to 1,600 characters in length. | String
+| creator | *from* | The phone number that initiated the message | PhoneNumber
+| creator | *mediaUrl* | The URL of the media to send with the message | List
+| creator | *messagingServiceSid* | The SID of the Messaging Service you want to associate with the message | String
| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *to* | The destination phone number | PhoneNumber
| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
| deleter | *pathSid* | The unique string that identifies the resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that will create the resource | String
+| updater | *body* | The text of the message you want to send | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the application API can also use from the 23 endpoint query option
+In addition to the parameters above, the message API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1509,25 +1592,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record
+==== API: message-feedback
-The usage-record API has 1 method(s) which is represented by the following method signatures
+The message-feedback API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.RecordReader reader();
+com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathAccountSid, String pathMessageSid);
-com.twilio.rest.api.v2010.account.usage.RecordReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathMessageSid);
----
-The usage-record API is defined in the syntax as follows:
+The message-feedback API is defined in the syntax as follows:
----
-twilio:usage-record/methodName?[parameters]
+twilio:message-feedback/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -1536,17 +1619,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a RecordReader to execute read
+| *creator* | create | Create a FeedbackCreator to execute create
|===
-The usage-record API method(s) has the following set of parameters listed in the table below:
+The message-feedback API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *pathMessageSid* | The SID of the Message resource for which the feedback was provided | String
|===
-In addition to the parameters above, the usage-record API can also use from the 23 endpoint query option
+In addition to the parameters above, the message-feedback API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1556,45 +1640,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country-mobile
+==== API: message-media
-The available-phone-number-country-mobile API has 1 method(s) which is represented by the following method signatures
+The message-media API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathAccountSid, String pathMessageSid, String pathSid);
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathCountryCode);
+com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathMessageSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathAccountSid, String pathMessageSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathMessageSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathAccountSid, String pathMessageSid);
+
+com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathMessageSid);
----
-The available-phone-number-country-mobile API is defined in the syntax as follows:
+The message-media API is defined in the syntax as follows:
----
-twilio:available-phone-number-country-mobile/methodName?[parameters]
+twilio:message-media/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a MobileReader to execute read
+| *deleter* | delete | Create a MediaDeleter to execute delete
+| *fetcher* | fetch | Create a MediaFetcher to execute fetch
+| *reader* | read | Create a MediaReader to execute read
|===
-The available-phone-number-country-mobile API method(s) has the following set of parameters listed in the table below:
+The message-media API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
-| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
+| deleter | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
+| deleter | *pathSid* | The unique string that identifies this resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
+| fetcher | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| reader | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
|===
-In addition to the parameters above, the available-phone-number-country-mobile API can also use from the 23 endpoint query option
+In addition to the parameters above, the message-media API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1604,78 +1704,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: conference-participant
+==== API: new-key
-The conference-participant API has 5 method(s) which is represented by the following method signatures
+The new-key API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathAccountSid, String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantCreator creator(String pathConferenceSid, com.twilio.type.PhoneNumber from, com.twilio.type.PhoneNumber to);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathAccountSid, String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantDeleter deleter(String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathAccountSid, String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantFetcher fetcher(String pathConferenceSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathAccountSid, String pathConferenceSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantReader reader(String pathConferenceSid);
-
-com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathAccountSid, String pathConferenceSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.NewKeyCreator creator();
-com.twilio.rest.api.v2010.account.conference.ParticipantUpdater updater(String pathConferenceSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.NewKeyCreator creator(String pathAccountSid);
----
-The conference-participant API is defined in the syntax as follows:
+The new-key API is defined in the syntax as follows:
----
-twilio:conference-participant/methodName?[parameters]
+twilio:new-key/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a ParticipantCreator to execute create
-| *deleter* | delete | Create a ParticipantDeleter to execute delete
-| *fetcher* | fetch | Create a ParticipantFetcher to execute fetch
-| *reader* | read | Create a ParticipantReader to execute read
-| *updater* | update | Create a ParticipantUpdater to execute update
+| *creator* | create | Create a NewKeyCreator to execute create
|===
-The conference-participant API method(s) has the following set of parameters listed in the table below:
+The new-key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *from* | The phone number, Client identifier, or username portion of SIP address that made this call. | PhoneNumber
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *pathConferenceSid* | The SID of the participant's conference | String
-| creator | *to* | The phone number, SIP address or Client identifier that received this call. | PhoneNumber
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathCallSid* | The Call SID or URL encoded label of the participant to delete | String
-| deleter | *pathConferenceSid* | The SID of the participant's conference | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathCallSid* | The Call SID or URL encoded label of the participant to fetch | String
-| fetcher | *pathConferenceSid* | The SID of the participant's conference | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathConferenceSid* | The SID of the participant's conference | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathCallSid* | The Call SID or URL encoded label of the participant to update | String
-| updater | *pathConferenceSid* | The SID of the participant's conference | String
+| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
|===
-In addition to the parameters above, the conference-participant API can also use from the 23 endpoint query option
+In addition to the parameters above, the new-key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1685,51 +1751,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: notification
+==== API: new-signing-key
-The notification API has 2 method(s) which is represented by the following method signatures
+The new-signing-key API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.NotificationReader reader();
+com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator();
-com.twilio.rest.api.v2010.account.NotificationReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.NewSigningKeyCreator creator(String pathAccountSid);
----
-The notification API is defined in the syntax as follows:
+The new-signing-key API is defined in the syntax as follows:
----
-twilio:notification/methodName?[parameters]
+twilio:new-signing-key/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
-| *reader* | read | Create a NotificationReader to execute read
+| *creator* | create | Create a NewSigningKeyCreator to execute create
|===
-The notification API method(s) has the following set of parameters listed in the table below:
+The new-signing-key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Key resource | String
|===
-In addition to the parameters above, the notification API can also use from the 23 endpoint query option
+In addition to the parameters above, the new-signing-key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1739,61 +1798,51 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: recording-add-on-result
+==== API: notification
-The recording-add-on-result API has 3 method(s) which is represented by the following method signatures
+The notification API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathReferenceSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathSid);
+com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathReferenceSid, String pathSid);
+com.twilio.rest.api.v2010.account.NotificationFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathAccountSid, String pathReferenceSid);
+com.twilio.rest.api.v2010.account.NotificationReader reader();
-com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathReferenceSid);
+com.twilio.rest.api.v2010.account.NotificationReader reader(String pathAccountSid);
----
-The recording-add-on-result API is defined in the syntax as follows:
+The notification API is defined in the syntax as follows:
----
-twilio:recording-add-on-result/methodName?[parameters]
+twilio:notification/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a AddOnResultDeleter to execute delete
-| *fetcher* | fetch | Create a AddOnResultFetcher to execute fetch
-| *reader* | read | Create a AddOnResultReader to execute read
+| *fetcher* | fetch | Create a NotificationFetcher to execute fetch
+| *reader* | read | Create a NotificationReader to execute read
|===
-The recording-add-on-result API method(s) has the following set of parameters listed in the table below:
+The notification API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
-| deleter | *pathSid* | The unique string that identifies the resource to delete | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
-| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
|===
-In addition to the parameters above, the recording-add-on-result API can also use from the 23 endpoint query option
+In addition to the parameters above, the notification API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1803,37 +1852,37 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-domain-ip-access-control-list-mapping
+==== API: outgoing-caller-id
-The sip-domain-ip-access-control-list-mapping API has 4 method(s) which is represented by the following method signatures
+The outgoing-caller-id API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathAccountSid, String pathDomainSid, String ipAccessControlListSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathDomainSid, String ipAccessControlListSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader();
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathAccountSid, String pathDomainSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathDomainSid);
+com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathSid);
----
-The sip-domain-ip-access-control-list-mapping API is defined in the syntax as follows:
+The outgoing-caller-id API is defined in the syntax as follows:
----
-twilio:sip-domain-ip-access-control-list-mapping/methodName?[parameters]
+twilio:outgoing-caller-id/methodName?[parameters]
----
The 4 method(s) is listed in the table below.
@@ -1842,30 +1891,26 @@ The 4 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IpAccessControlListMappingCreator to execute create
-| *deleter* | delete | Create a IpAccessControlListMappingDeleter to execute delete
-| *fetcher* | fetch | Create a IpAccessControlListMappingFetcher to execute fetch
-| *reader* | read | Create a IpAccessControlListMappingReader to execute read
+| *deleter* | delete | Create a OutgoingCallerIdDeleter to execute delete
+| *fetcher* | fetch | Create a OutgoingCallerIdFetcher to execute fetch
+| *reader* | read | Create a OutgoingCallerIdReader to execute read
+| *updater* | update | Create a OutgoingCallerIdUpdater to execute update
|===
-The sip-domain-ip-access-control-list-mapping API method(s) has the following set of parameters listed in the table below:
+The outgoing-caller-id API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *ipAccessControlListSid* | The unique id of the IP access control list to map to the SIP domain | String
-| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| creator | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
-| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
-| deleter | *pathSid* | A 34 character string that uniquely identifies the resource to delete. | String
-| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| fetcher | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
-| fetcher | *pathSid* | A 34 character string that uniquely identifies the resource to fetch. | String
-| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| reader | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the sip-domain-ip-access-control-list-mapping API can also use from the 23 endpoint query option
+In addition to the parameters above, the outgoing-caller-id API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1875,41 +1920,41 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-domain
+==== API: queue
-The sip-domain API has 5 method(s) which is represented by the following method signatures
+The queue API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String domainName);
+com.twilio.rest.api.v2010.account.QueueCreator creator(String friendlyName);
-com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String pathAccountSid, String domainName);
+com.twilio.rest.api.v2010.account.QueueCreator creator(String pathAccountSid, String friendlyName);
-com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainReader reader();
+com.twilio.rest.api.v2010.account.QueueReader reader();
-com.twilio.rest.api.v2010.account.sip.DomainReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.QueueReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathSid);
----
-The sip-domain API is defined in the syntax as follows:
+The queue API is defined in the syntax as follows:
----
-twilio:sip-domain/methodName?[parameters]
+twilio:queue/methodName?[parameters]
----
The 5 method(s) is listed in the table below.
@@ -1918,29 +1963,29 @@ The 5 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a DomainCreator to execute create
-| *deleter* | delete | Create a DomainDeleter to execute delete
-| *fetcher* | fetch | Create a DomainFetcher to execute fetch
-| *reader* | read | Create a DomainReader to execute read
-| *updater* | update | Create a DomainUpdater to execute update
+| *creator* | create | Create a QueueCreator to execute create
+| *deleter* | delete | Create a QueueDeleter to execute delete
+| *fetcher* | fetch | Create a QueueFetcher to execute fetch
+| *reader* | read | Create a QueueReader to execute read
+| *updater* | update | Create a QueueUpdater to execute update
|===
-The sip-domain API method(s) has the following set of parameters listed in the table below:
+The queue API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *domainName* | The unique address on Twilio to route SIP traffic | String
+| creator | *friendlyName* | A string to describe this resource | String
| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
+| deleter | *pathSid* | The unique string that identifies this resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the sip-domain API can also use from the 23 endpoint query option
+In addition to the parameters above, the queue API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -1950,77 +1995,62 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: address
+==== API: queue-member
-The address API has 5 method(s) which is represented by the following method signatures
+The queue-member API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.AddressCreator creator(String customerName, String street, String city, String region, String postalCode, String isoCountry);
-
-com.twilio.rest.api.v2010.account.AddressCreator creator(String pathAccountSid, String customerName, String street, String city, String region, String postalCode, String isoCountry);
-
-com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathAccountSid, String pathQueueSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathQueueSid, String pathCallSid);
-com.twilio.rest.api.v2010.account.AddressReader reader();
+com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathAccountSid, String pathQueueSid);
-com.twilio.rest.api.v2010.account.AddressReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathQueueSid);
-com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathAccountSid, String pathQueueSid, String pathCallSid, java.net.URI url);
-com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathQueueSid, String pathCallSid, java.net.URI url);
----
-The address API is defined in the syntax as follows:
+The queue-member API is defined in the syntax as follows:
----
-twilio:address/methodName?[parameters]
+twilio:queue-member/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a AddressCreator to execute create
-| *deleter* | delete | Create a AddressDeleter to execute delete
-| *fetcher* | fetch | Create a AddressFetcher to execute fetch
-| *reader* | read | Create a AddressReader to execute read
-| *updater* | update | Create a AddressUpdater to execute update
+| *fetcher* | fetch | Create a MemberFetcher to execute fetch
+| *reader* | read | Create a MemberReader to execute read
+| *updater* | update | Create a MemberUpdater to execute update
|===
-The address API method(s) has the following set of parameters listed in the table below:
+The queue-member API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *city* | The city of the new address | String
-| creator | *customerName* | The name to associate with the new address | String
-| creator | *isoCountry* | The ISO country code of the new address | String
-| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Address resource | String
-| creator | *postalCode* | The postal code of the new address | String
-| creator | *region* | The state or region of the new address | String
-| creator | *street* | The number and street address of the new address | String
-| deleter | *pathAccountSid* | The SID of the Account that is responsible for the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that is responsible for this address | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that is responsible for this address | String
-| updater | *pathAccountSid* | The SID of the Account that is responsible for the resource to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| fetcher | *pathCallSid* | The Call SID of the resource(s) to fetch | String
+| fetcher | *pathQueueSid* | The SID of the Queue in which to find the members | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
+| reader | *pathQueueSid* | The SID of the Queue in which to find the members | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
+| updater | *pathCallSid* | The Call SID of the resource(s) to update | String
+| updater | *pathQueueSid* | The SID of the Queue in which to find the members | String
+| updater | *url* | The absolute URL of the Queue resource | URI
|===
-In addition to the parameters above, the address API can also use from the 23 endpoint query option
+In addition to the parameters above, the queue-member API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2030,33 +2060,33 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: message-media
+==== API: recording
-The message-media API has 3 method(s) which is represented by the following method signatures
+The recording API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathAccountSid, String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaDeleter deleter(String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathAccountSid, String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaFetcher fetcher(String pathMessageSid, String pathSid);
+com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathAccountSid, String pathMessageSid);
+com.twilio.rest.api.v2010.account.RecordingReader reader();
-com.twilio.rest.api.v2010.account.message.MediaReader reader(String pathMessageSid);
+com.twilio.rest.api.v2010.account.RecordingReader reader(String pathAccountSid);
----
-The message-media API is defined in the syntax as follows:
+The recording API is defined in the syntax as follows:
----
-twilio:message-media/methodName?[parameters]
+twilio:recording/methodName?[parameters]
----
The 3 method(s) is listed in the table below.
@@ -2065,26 +2095,23 @@ The 3 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a MediaDeleter to execute delete
-| *fetcher* | fetch | Create a MediaFetcher to execute fetch
-| *reader* | read | Create a MediaReader to execute read
+| *deleter* | delete | Create a RecordingDeleter to execute delete
+| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
+| *reader* | read | Create a RecordingReader to execute read
|===
-The message-media API method(s) has the following set of parameters listed in the table below:
+The recording API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
-| deleter | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
-| deleter | *pathSid* | The unique string that identifies this resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
-| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| reader | *pathMessageSid* | The SID of the Message resource that this Media resource belongs to | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the message-media API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2094,78 +2121,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-ip-access-control-list-ip-address
+==== API: recording-add-on-result
-The sip-ip-access-control-list-ip-address API has 5 method(s) which is represented by the following method signatures
+The recording-add-on-result API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathAccountSid, String pathIpAccessControlListSid, String friendlyName, String ipAddress);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathIpAccessControlListSid, String friendlyName, String ipAddress);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathIpAccessControlListSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultDeleter deleter(String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathAccountSid, String pathIpAccessControlListSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathIpAccessControlListSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultFetcher fetcher(String pathReferenceSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathAccountSid, String pathReferenceSid);
-com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathIpAccessControlListSid, String pathSid);
+com.twilio.rest.api.v2010.account.recording.AddOnResultReader reader(String pathReferenceSid);
----
-The sip-ip-access-control-list-ip-address API is defined in the syntax as follows:
+The recording-add-on-result API is defined in the syntax as follows:
----
-twilio:sip-ip-access-control-list-ip-address/methodName?[parameters]
+twilio:recording-add-on-result/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IpAddressCreator to execute create
-| *deleter* | delete | Create a IpAddressDeleter to execute delete
-| *fetcher* | fetch | Create a IpAddressFetcher to execute fetch
-| *reader* | read | Create a IpAddressReader to execute read
-| *updater* | update | Create a IpAddressUpdater to execute update
+| *deleter* | delete | Create a AddOnResultDeleter to execute delete
+| *fetcher* | fetch | Create a AddOnResultFetcher to execute fetch
+| *reader* | read | Create a AddOnResultReader to execute read
|===
-The sip-ip-access-control-list-ip-address API method(s) has the following set of parameters listed in the table below:
+The recording-add-on-result API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | A human readable descriptive text for this resource, up to 64 characters long. | String
-| creator | *ipAddress* | An IP address in dotted decimal notation from which you want to accept traffic. Any SIP requests from this IP address will be allowed by Twilio. IPv4 only supported today. | String
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| creator | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| deleter | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| deleter | *pathSid* | A string that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| fetcher | *pathSid* | A string that identifies the IpAddress resource to fetch | String
-| reader | *pathAccountSid* | The unique sid that identifies this account | String
-| reader | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| updater | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
-| updater | *pathSid* | A string that identifies the IpAddress resource to update | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
+| deleter | *pathSid* | The unique string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
+| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathReferenceSid* | The SID of the recording to which the result to delete belongs | String
|===
-In addition to the parameters above, the sip-ip-access-control-list-ip-address API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording-add-on-result API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2175,51 +2185,64 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country
+==== API: recording-add-on-result-payload
-The available-phone-number-country API has 2 method(s) which is represented by the following method signatures
+The recording-add-on-result-payload API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathCountryCode);
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader();
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid);
+
+com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathReferenceSid, String pathAddOnResultSid);
----
-The available-phone-number-country API is defined in the syntax as follows:
+The recording-add-on-result-payload API is defined in the syntax as follows:
----
-twilio:available-phone-number-country/methodName?[parameters]
+twilio:recording-add-on-result-payload/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a AvailablePhoneNumberCountryFetcher to execute fetch
-| *reader* | read | Create a AvailablePhoneNumberCountryReader to execute read
+| *deleter* | delete | Create a PayloadDeleter to execute delete
+| *fetcher* | fetch | Create a PayloadFetcher to execute fetch
+| *reader* | read | Create a PayloadReader to execute read
|===
-The available-phone-number-country API method(s) has the following set of parameters listed in the table below:
+The recording-add-on-result-payload API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account requesting the available phone number Country resource | String
-| fetcher | *pathCountryCode* | The ISO country code of the country to fetch available phone number information about | String
-| reader | *pathAccountSid* | The SID of the Account requesting the available phone number Country resources | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
+| deleter | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
+| fetcher | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
+| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
+| reader | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
|===
-In addition to the parameters above, the available-phone-number-country API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording-add-on-result-payload API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2229,44 +2252,61 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-yearly
+==== API: recording-transcription
-The usage-record-yearly API has 1 method(s) which is represented by the following method signatures
+The recording-transcription API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader();
+com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathAccountSid, String pathRecordingSid, String pathSid);
-com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.recording.TranscriptionDeleter deleter(String pathRecordingSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathAccountSid, String pathRecordingSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionFetcher fetcher(String pathRecordingSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathAccountSid, String pathRecordingSid);
+
+com.twilio.rest.api.v2010.account.recording.TranscriptionReader reader(String pathRecordingSid);
----
-The usage-record-yearly API is defined in the syntax as follows:
+The recording-transcription API is defined in the syntax as follows:
----
-twilio:usage-record-yearly/methodName?[parameters]
+twilio:recording-transcription/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a YearlyReader to execute read
+| *deleter* | delete | Create a TranscriptionDeleter to execute delete
+| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
+| *reader* | read | Create a TranscriptionReader to execute read
|===
-The usage-record-yearly API method(s) has the following set of parameters listed in the table below:
+The recording-transcription API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathRecordingSid* | The SID of the recording that created the transcription to delete | String
|===
-In addition to the parameters above, the usage-record-yearly API can also use from the 23 endpoint query option
+In addition to the parameters above, the recording-transcription API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2276,72 +2316,58 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: queue
+==== API: short-code
-The queue API has 5 method(s) which is represented by the following method signatures
+The short-code API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.QueueCreator creator(String friendlyName);
-
-com.twilio.rest.api.v2010.account.QueueCreator creator(String pathAccountSid, String friendlyName);
-
-com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.QueueDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.QueueFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.QueueReader reader();
+com.twilio.rest.api.v2010.account.ShortCodeReader reader();
-com.twilio.rest.api.v2010.account.QueueReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.ShortCodeReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.QueueUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathSid);
----
-The queue API is defined in the syntax as follows:
+The short-code API is defined in the syntax as follows:
----
-twilio:queue/methodName?[parameters]
+twilio:short-code/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a QueueCreator to execute create
-| *deleter* | delete | Create a QueueDeleter to execute delete
-| *fetcher* | fetch | Create a QueueFetcher to execute fetch
-| *reader* | read | Create a QueueReader to execute read
-| *updater* | update | Create a QueueUpdater to execute update
+| *fetcher* | fetch | Create a ShortCodeFetcher to execute fetch
+| *reader* | read | Create a ShortCodeReader to execute read
+| *updater* | update | Create a ShortCodeUpdater to execute update
|===
-The queue API method(s) has the following set of parameters listed in the table below:
+The short-code API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | A string to describe this resource | String
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
-| deleter | *pathSid* | The unique string that identifies this resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
+| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
| updater | *pathSid* | The unique string that identifies this resource | String
|===
-In addition to the parameters above, the queue API can also use from the 23 endpoint query option
+In addition to the parameters above, the short-code API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2351,58 +2377,65 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: transcription
+==== API: signing-key
-The transcription API has 3 method(s) which is represented by the following method signatures
+The signing-key API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.TranscriptionReader reader();
+com.twilio.rest.api.v2010.account.SigningKeyReader reader();
-com.twilio.rest.api.v2010.account.TranscriptionReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.SigningKeyReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathSid);
----
-The transcription API is defined in the syntax as follows:
+The signing-key API is defined in the syntax as follows:
----
-twilio:transcription/methodName?[parameters]
+twilio:signing-key/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a TranscriptionDeleter to execute delete
-| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
-| *reader* | read | Create a TranscriptionReader to execute read
+| *deleter* | delete | Create a SigningKeyDeleter to execute delete
+| *fetcher* | fetch | Create a SigningKeyFetcher to execute fetch
+| *reader* | read | Create a SigningKeyReader to execute read
+| *updater* | update | Create a SigningKeyUpdater to execute update
|===
-The transcription API method(s) has the following set of parameters listed in the table below:
+The signing-key API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| deleter | *pathAccountSid* | The account_sid | String
+| deleter | *pathSid* | The sid | String
+| fetcher | *pathAccountSid* | The account_sid | String
+| fetcher | *pathSid* | The sid | String
+| reader | *pathAccountSid* | The account_sid | String
+| updater | *pathAccountSid* | The account_sid | String
+| updater | *pathSid* | The sid | String
|===
-In addition to the parameters above, the transcription API can also use from the 23 endpoint query option
+In addition to the parameters above, the signing-key API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2412,69 +2445,73 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-domain-credential-list-mapping
+==== API: sip-credential-list
-The sip-domain-credential-list-mapping API has 4 method(s) which is represented by the following method signatures
+The sip-credential-list API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathAccountSid, String pathDomainSid, String credentialListSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String friendlyName);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathDomainSid, String credentialListSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String pathAccountSid, String friendlyName);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathAccountSid, String pathDomainSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListReader reader();
-com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathDomainSid);
+com.twilio.rest.api.v2010.account.sip.CredentialListReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+
+com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathSid, String friendlyName);
----
-The sip-domain-credential-list-mapping API is defined in the syntax as follows:
+The sip-credential-list API is defined in the syntax as follows:
----
-twilio:sip-domain-credential-list-mapping/methodName?[parameters]
+twilio:sip-credential-list/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CredentialListMappingCreator to execute create
-| *deleter* | delete | Create a CredentialListMappingDeleter to execute delete
-| *fetcher* | fetch | Create a CredentialListMappingFetcher to execute fetch
-| *reader* | read | Create a CredentialListMappingReader to execute read
+| *creator* | create | Create a CredentialListCreator to execute create
+| *deleter* | delete | Create a CredentialListDeleter to execute delete
+| *fetcher* | fetch | Create a CredentialListFetcher to execute fetch
+| *reader* | read | Create a CredentialListReader to execute read
+| *updater* | update | Create a CredentialListUpdater to execute update
|===
-The sip-domain-credential-list-mapping API method(s) has the following set of parameters listed in the table below:
+The sip-credential-list API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *credentialListSid* | A string that identifies the CredentialList resource to map to the SIP domain | String
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| creator | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
-| deleter | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
-| deleter | *pathSid* | A string that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
-| fetcher | *pathSid* | A string that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The unique sid that identifies this account | String
-| reader | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| creator | *friendlyName* | Human readable descriptive text | String
+| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathSid* | Delete by unique credential list Sid | String
+| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| fetcher | *pathSid* | Fetch by unique credential list Sid | String
+| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| updater | *friendlyName* | Human readable descriptive text | String
+| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| updater | *pathSid* | Update by unique credential list Sid | String
|===
-In addition to the parameters above, the sip-domain-credential-list-mapping API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-credential-list API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2484,61 +2521,78 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call-feedback
+==== API: sip-credential-list-credential
-The call-feedback API has 3 method(s) which is represented by the following method signatures
+The sip-credential-list-credential API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathAccountSid, String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathAccountSid, String pathCredentialListSid, String username, String password);
-com.twilio.rest.api.v2010.account.call.FeedbackCreator creator(String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialCreator creator(String pathCredentialListSid, String username, String password);
-com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathAccountSid, String pathCredentialListSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.FeedbackFetcher fetcher(String pathCallSid);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialDeleter deleter(String pathCredentialListSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathAccountSid, String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathAccountSid, String pathCredentialListSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.FeedbackUpdater updater(String pathCallSid, Integer qualityScore);
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialFetcher fetcher(String pathCredentialListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathAccountSid, String pathCredentialListSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialReader reader(String pathCredentialListSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathAccountSid, String pathCredentialListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.credentiallist.CredentialUpdater updater(String pathCredentialListSid, String pathSid);
----
-The call-feedback API is defined in the syntax as follows:
+The sip-credential-list-credential API is defined in the syntax as follows:
----
-twilio:call-feedback/methodName?[parameters]
+twilio:sip-credential-list-credential/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a FeedbackCreator to execute create
-| *fetcher* | fetch | Create a FeedbackFetcher to execute fetch
-| *updater* | update | Create a FeedbackUpdater to execute update
+| *creator* | create | Create a CredentialCreator to execute create
+| *deleter* | delete | Create a CredentialDeleter to execute delete
+| *fetcher* | fetch | Create a CredentialFetcher to execute fetch
+| *reader* | read | Create a CredentialReader to execute read
+| *updater* | update | Create a CredentialUpdater to execute update
|===
-The call-feedback API method(s) has the following set of parameters listed in the table below:
+The sip-credential-list-credential API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| creator | *pathCallSid* | The call sid that uniquely identifies the call | String
-| creator | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathCallSid* | The call sid that uniquely identifies the call | String
-| updater | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *pathCallSid* | The call sid that uniquely identifies the call | String
-| updater | *qualityScore* | The call quality expressed as an integer from 1 to 5 | Integer
+| creator | *password* | The password will not be returned in the response | String
+| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| creator | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| creator | *username* | The username for this credential | String
+| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| deleter | *pathSid* | The unique id that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| fetcher | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| fetcher | *pathSid* | The unique id that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| reader | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| updater | *pathCredentialListSid* | The unique id that identifies the credential list to include the created credential | String
+| updater | *pathSid* | The unique id that identifies the resource to update | String
|===
-In addition to the parameters above, the call-feedback API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-credential-list-credential API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2548,65 +2602,72 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: key
+==== API: sip-domain
-The key API has 4 method(s) which is represented by the following method signatures
+The sip-domain API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String domainName);
-com.twilio.rest.api.v2010.account.KeyDeleter deleter(String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainCreator creator(String pathAccountSid, String domainName);
-com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.KeyFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.KeyReader reader();
+com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.KeyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.DomainFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainReader reader();
-com.twilio.rest.api.v2010.account.KeyUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.sip.DomainReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.DomainUpdater updater(String pathSid);
----
-The key API is defined in the syntax as follows:
+The sip-domain API is defined in the syntax as follows:
----
-twilio:key/methodName?[parameters]
+twilio:sip-domain/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a KeyDeleter to execute delete
-| *fetcher* | fetch | Create a KeyFetcher to execute fetch
-| *reader* | read | Create a KeyReader to execute read
-| *updater* | update | Create a KeyUpdater to execute update
+| *creator* | create | Create a DomainCreator to execute create
+| *deleter* | delete | Create a DomainDeleter to execute delete
+| *fetcher* | fetch | Create a DomainFetcher to execute fetch
+| *reader* | read | Create a DomainReader to execute read
+| *updater* | update | Create a DomainUpdater to execute update
|===
-The key API method(s) has the following set of parameters listed in the table below:
+The sip-domain API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
+| creator | *domainName* | The unique address on Twilio to route SIP traffic | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
| deleter | *pathSid* | The unique string that identifies the resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the key API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-domain API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2616,51 +2677,69 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number-toll-free
+==== API: sip-domain-credential-list-mapping
-The incoming-phone-number-toll-free API has 2 method(s) which is represented by the following method signatures
+The sip-domain-credential-list-mapping API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathAccountSid, String pathDomainSid, String credentialListSid);
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeCreator creator(com.twilio.type.PhoneNumber phoneNumber);
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingCreator creator(String pathDomainSid, String credentialListSid);
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader();
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
-com.twilio.rest.api.v2010.account.incomingphonenumber.TollFreeReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingDeleter deleter(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathAccountSid, String pathDomainSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.CredentialListMappingReader reader(String pathDomainSid);
----
-The incoming-phone-number-toll-free API is defined in the syntax as follows:
+The sip-domain-credential-list-mapping API is defined in the syntax as follows:
----
-twilio:incoming-phone-number-toll-free/methodName?[parameters]
+twilio:sip-domain-credential-list-mapping/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a TollFreeCreator to execute create
-| *reader* | read | Create a TollFreeReader to execute read
+| *creator* | create | Create a CredentialListMappingCreator to execute create
+| *deleter* | delete | Create a CredentialListMappingDeleter to execute delete
+| *fetcher* | fetch | Create a CredentialListMappingFetcher to execute fetch
+| *reader* | read | Create a CredentialListMappingReader to execute read
|===
-The incoming-phone-number-toll-free API method(s) has the following set of parameters listed in the table below:
+The sip-domain-credential-list-mapping API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *credentialListSid* | A string that identifies the CredentialList resource to map to the SIP domain | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| creator | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| deleter | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| deleter | *pathSid* | A string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
+| fetcher | *pathSid* | A string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The unique sid that identifies this account | String
+| reader | *pathDomainSid* | A string that identifies the SIP Domain for which the CredentialList resource will be mapped | String
|===
-In addition to the parameters above, the incoming-phone-number-toll-free API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-domain-credential-list-mapping API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2670,44 +2749,69 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: token
+==== API: sip-domain-ip-access-control-list-mapping
-The token API has 1 method(s) which is represented by the following method signatures
+The sip-domain-ip-access-control-list-mapping API has 4 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.TokenCreator creator();
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathAccountSid, String pathDomainSid, String ipAccessControlListSid);
-com.twilio.rest.api.v2010.account.TokenCreator creator(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingCreator creator(String pathDomainSid, String ipAccessControlListSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathAccountSid, String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingDeleter deleter(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathAccountSid, String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingFetcher fetcher(String pathDomainSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathAccountSid, String pathDomainSid);
+
+com.twilio.rest.api.v2010.account.sip.domain.IpAccessControlListMappingReader reader(String pathDomainSid);
----
-The token API is defined in the syntax as follows:
+The sip-domain-ip-access-control-list-mapping API is defined in the syntax as follows:
----
-twilio:token/methodName?[parameters]
+twilio:sip-domain-ip-access-control-list-mapping/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 4 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a TokenCreator to execute create
+| *creator* | create | Create a IpAccessControlListMappingCreator to execute create
+| *deleter* | delete | Create a IpAccessControlListMappingDeleter to execute delete
+| *fetcher* | fetch | Create a IpAccessControlListMappingFetcher to execute fetch
+| *reader* | read | Create a IpAccessControlListMappingReader to execute read
|===
-The token API method(s) has the following set of parameters listed in the table below:
+The sip-domain-ip-access-control-list-mapping API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *ipAccessControlListSid* | The unique id of the IP access control list to map to the SIP domain | String
+| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| creator | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| deleter | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| deleter | *pathSid* | A 34 character string that uniquely identifies the resource to delete. | String
+| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| fetcher | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
+| fetcher | *pathSid* | A 34 character string that uniquely identifies the resource to fetch. | String
+| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
+| reader | *pathDomainSid* | A string that uniquely identifies the SIP Domain | String
|===
-In addition to the parameters above, the token API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-domain-ip-access-control-list-mapping API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2717,58 +2821,73 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: short-code
+==== API: sip-ip-access-control-list
-The short-code API has 3 method(s) which is represented by the following method signatures
+The sip-ip-access-control-list API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String friendlyName);
-com.twilio.rest.api.v2010.account.ShortCodeFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String pathAccountSid, String friendlyName);
-com.twilio.rest.api.v2010.account.ShortCodeReader reader();
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ShortCodeReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.ShortCodeUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader();
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+
+com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathSid, String friendlyName);
----
-The short-code API is defined in the syntax as follows:
+The sip-ip-access-control-list API is defined in the syntax as follows:
----
-twilio:short-code/methodName?[parameters]
+twilio:sip-ip-access-control-list/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a ShortCodeFetcher to execute fetch
-| *reader* | read | Create a ShortCodeReader to execute read
-| *updater* | update | Create a ShortCodeUpdater to execute update
+| *creator* | create | Create a IpAccessControlListCreator to execute create
+| *deleter* | delete | Create a IpAccessControlListDeleter to execute delete
+| *fetcher* | fetch | Create a IpAccessControlListFetcher to execute fetch
+| *reader* | read | Create a IpAccessControlListReader to execute read
+| *updater* | update | Create a IpAccessControlListUpdater to execute update
|===
-The short-code API method(s) has the following set of parameters listed in the table below:
+The sip-ip-access-control-list API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathSid* | The unique string that identifies this resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathSid* | The unique string that identifies this resource | String
+| creator | *friendlyName* | A human readable description of this resource | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathSid* | A string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathSid* | A string that identifies the resource to fetch | String
+| reader | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *friendlyName* | A human readable description of this resource | String
+| updater | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *pathSid* | A string that identifies the resource to update | String
|===
-In addition to the parameters above, the short-code API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-ip-access-control-list API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2778,45 +2897,78 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country-toll-free
+==== API: sip-ip-access-control-list-ip-address
-The available-phone-number-country-toll-free API has 1 method(s) which is represented by the following method signatures
+The sip-ip-access-control-list-ip-address API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathAccountSid, String pathIpAccessControlListSid, String friendlyName, String ipAddress);
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.TollFreeReader reader(String pathCountryCode);
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressCreator creator(String pathIpAccessControlListSid, String friendlyName, String ipAddress);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressDeleter deleter(String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressFetcher fetcher(String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathAccountSid, String pathIpAccessControlListSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressReader reader(String pathIpAccessControlListSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathAccountSid, String pathIpAccessControlListSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.sip.ipaccesscontrollist.IpAddressUpdater updater(String pathIpAccessControlListSid, String pathSid);
----
-The available-phone-number-country-toll-free API is defined in the syntax as follows:
+The sip-ip-access-control-list-ip-address API is defined in the syntax as follows:
----
-twilio:available-phone-number-country-toll-free/methodName?[parameters]
+twilio:sip-ip-access-control-list-ip-address/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a TollFreeReader to execute read
+| *creator* | create | Create a IpAddressCreator to execute create
+| *deleter* | delete | Create a IpAddressDeleter to execute delete
+| *fetcher* | fetch | Create a IpAddressFetcher to execute fetch
+| *reader* | read | Create a IpAddressReader to execute read
+| *updater* | update | Create a IpAddressUpdater to execute update
|===
-The available-phone-number-country-toll-free API method(s) has the following set of parameters listed in the table below:
+The sip-ip-access-control-list-ip-address API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
-| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
+| creator | *friendlyName* | A human readable descriptive text for this resource, up to 64 characters long. | String
+| creator | *ipAddress* | An IP address in dotted decimal notation from which you want to accept traffic. Any SIP requests from this IP address will be allowed by Twilio. IPv4 only supported today. | String
+| creator | *pathAccountSid* | The unique sid that identifies this account | String
+| creator | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| deleter | *pathAccountSid* | The unique sid that identifies this account | String
+| deleter | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| deleter | *pathSid* | A string that identifies the resource to delete | String
+| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
+| fetcher | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| fetcher | *pathSid* | A string that identifies the IpAddress resource to fetch | String
+| reader | *pathAccountSid* | The unique sid that identifies this account | String
+| reader | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| updater | *pathAccountSid* | The unique sid that identifies this account | String
+| updater | *pathIpAccessControlListSid* | The IpAccessControlList Sid with which to associate the created IpAddress resource | String
+| updater | *pathSid* | A string that identifies the IpAddress resource to update | String
|===
-In addition to the parameters above, the available-phone-number-country-toll-free API can also use from the 23 endpoint query option
+In addition to the parameters above, the sip-ip-access-control-list-ip-address API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2826,25 +2978,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-monthly
+==== API: token
-The usage-record-monthly API has 1 method(s) which is represented by the following method signatures
+The token API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader();
+com.twilio.rest.api.v2010.account.TokenCreator creator();
-com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.TokenCreator creator(String pathAccountSid);
----
-The usage-record-monthly API is defined in the syntax as follows:
+The token API is defined in the syntax as follows:
----
-twilio:usage-record-monthly/methodName?[parameters]
+twilio:token/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -2853,17 +3005,17 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a MonthlyReader to execute read
+| *creator* | create | Create a TokenCreator to execute create
|===
-The usage-record-monthly API method(s) has the following set of parameters listed in the table below:
+The token API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
|===
-In addition to the parameters above, the usage-record-monthly API can also use from the 23 endpoint query option
+In addition to the parameters above, the token API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2873,73 +3025,58 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-ip-access-control-list
+==== API: transcription
-The sip-ip-access-control-list API has 5 method(s) which is represented by the following method signatures
+The transcription API has 3 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListCreator creator(String pathAccountSid, String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.TranscriptionDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader();
+com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.TranscriptionFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.TranscriptionReader reader();
-com.twilio.rest.api.v2010.account.sip.IpAccessControlListUpdater updater(String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.TranscriptionReader reader(String pathAccountSid);
----
-The sip-ip-access-control-list API is defined in the syntax as follows:
+The transcription API is defined in the syntax as follows:
----
-twilio:sip-ip-access-control-list/methodName?[parameters]
+twilio:transcription/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 3 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a IpAccessControlListCreator to execute create
-| *deleter* | delete | Create a IpAccessControlListDeleter to execute delete
-| *fetcher* | fetch | Create a IpAccessControlListFetcher to execute fetch
-| *reader* | read | Create a IpAccessControlListReader to execute read
-| *updater* | update | Create a IpAccessControlListUpdater to execute update
+| *deleter* | delete | Create a TranscriptionDeleter to execute delete
+| *fetcher* | fetch | Create a TranscriptionFetcher to execute fetch
+| *reader* | read | Create a TranscriptionReader to execute read
|===
-The sip-ip-access-control-list API method(s) has the following set of parameters listed in the table below:
+The transcription API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | A human readable description of this resource | String
-| creator | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathAccountSid* | The unique sid that identifies this account | String
-| deleter | *pathSid* | A string that identifies the resource to delete | String
-| fetcher | *pathAccountSid* | The unique sid that identifies this account | String
-| fetcher | *pathSid* | A string that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *friendlyName* | A human readable description of this resource | String
-| updater | *pathAccountSid* | The unique sid that identifies this account | String
-| updater | *pathSid* | A string that identifies the resource to update | String
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the sip-ip-access-control-list API can also use from the 23 endpoint query option
+In addition to the parameters above, the transcription API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -2949,65 +3086,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: connect-app
+==== API: usage-record
-The connect-app API has 4 method(s) which is represented by the following method signatures
+The usage-record API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppReader reader();
-
-com.twilio.rest.api.v2010.account.ConnectAppReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.RecordReader reader();
-com.twilio.rest.api.v2010.account.ConnectAppUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.RecordReader reader(String pathAccountSid);
----
-The connect-app API is defined in the syntax as follows:
+The usage-record API is defined in the syntax as follows:
----
-twilio:connect-app/methodName?[parameters]
+twilio:usage-record/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a ConnectAppDeleter to execute delete
-| *fetcher* | fetch | Create a ConnectAppFetcher to execute fetch
-| *reader* | read | Create a ConnectAppReader to execute read
-| *updater* | update | Create a ConnectAppUpdater to execute update
+| *reader* | read | Create a RecordReader to execute read
|===
-The connect-app API method(s) has the following set of parameters listed in the table below:
+The usage-record API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the connect-app API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3017,25 +3133,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: address-dependent-phone-number
+==== API: usage-record-all-time
-The address-dependent-phone-number API has 1 method(s) which is represented by the following method signatures
+The usage-record-all-time API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAccountSid, String pathAddressSid);
+com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader();
-com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAddressSid);
+com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader(String pathAccountSid);
----
-The address-dependent-phone-number API is defined in the syntax as follows:
+The usage-record-all-time API is defined in the syntax as follows:
----
-twilio:address-dependent-phone-number/methodName?[parameters]
+twilio:usage-record-all-time/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -3044,18 +3160,17 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a DependentPhoneNumberReader to execute read
+| *reader* | read | Create a AllTimeReader to execute read
|===
-The address-dependent-phone-number API method(s) has the following set of parameters listed in the table below:
+The usage-record-all-time API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathAddressSid* | The SID of the Address resource associated with the phone number | String
|===
-In addition to the parameters above, the address-dependent-phone-number API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-all-time API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3065,65 +3180,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: signing-key
+==== API: usage-record-daily
-The signing-key API has 4 method(s) which is represented by the following method signatures
+The usage-record-daily API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyReader reader();
-
-com.twilio.rest.api.v2010.account.SigningKeyReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.DailyReader reader();
-com.twilio.rest.api.v2010.account.SigningKeyUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.DailyReader reader(String pathAccountSid);
----
-The signing-key API is defined in the syntax as follows:
+The usage-record-daily API is defined in the syntax as follows:
----
-twilio:signing-key/methodName?[parameters]
+twilio:usage-record-daily/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a SigningKeyDeleter to execute delete
-| *fetcher* | fetch | Create a SigningKeyFetcher to execute fetch
-| *reader* | read | Create a SigningKeyReader to execute read
-| *updater* | update | Create a SigningKeyUpdater to execute update
+| *reader* | read | Create a DailyReader to execute read
|===
-The signing-key API method(s) has the following set of parameters listed in the table below:
+The usage-record-daily API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The account_sid | String
-| deleter | *pathSid* | The sid | String
-| fetcher | *pathAccountSid* | The account_sid | String
-| fetcher | *pathSid* | The sid | String
-| reader | *pathAccountSid* | The account_sid | String
-| updater | *pathAccountSid* | The account_sid | String
-| updater | *pathSid* | The sid | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the signing-key API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-daily API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3133,65 +3227,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: outgoing-caller-id
+==== API: usage-record-last-month
-The outgoing-caller-id API has 4 method(s) which is represented by the following method signatures
+The usage-record-last-month API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader();
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader();
-com.twilio.rest.api.v2010.account.OutgoingCallerIdUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.LastMonthReader reader(String pathAccountSid);
----
-The outgoing-caller-id API is defined in the syntax as follows:
+The usage-record-last-month API is defined in the syntax as follows:
----
-twilio:outgoing-caller-id/methodName?[parameters]
+twilio:usage-record-last-month/methodName?[parameters]
----
-The 4 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a OutgoingCallerIdDeleter to execute delete
-| *fetcher* | fetch | Create a OutgoingCallerIdFetcher to execute fetch
-| *reader* | read | Create a OutgoingCallerIdReader to execute read
-| *updater* | update | Create a OutgoingCallerIdUpdater to execute update
+| *reader* | read | Create a LastMonthReader to execute read
|===
-The outgoing-caller-id API method(s) has the following set of parameters listed in the table below:
+The usage-record-last-month API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the outgoing-caller-id API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-last-month API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3201,84 +3274,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call
-
-
-The call API has 5 method(s) which is represented by the following method signatures
-(an API method may have multiple signatures due to overloading):
-
-[source,java]
-----
-
-com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(String pathAccountSid, com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, String applicationSid);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, com.twilio.type.Twiml twiml);
-
-com.twilio.rest.api.v2010.account.CallCreator creator(com.twilio.type.Endpoint to, com.twilio.type.Endpoint from, java.net.URI url);
-
-com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.CallDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathAccountSid, String pathSid);
+==== API: usage-record-monthly
-com.twilio.rest.api.v2010.account.CallFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.CallReader reader();
+The usage-record-monthly API has 1 method(s) which is represented by the following method signatures
+(an API method may have multiple signatures due to overloading):
-com.twilio.rest.api.v2010.account.CallReader reader(String pathAccountSid);
+[source,java]
+----
-com.twilio.rest.api.v2010.account.CallUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader();
-com.twilio.rest.api.v2010.account.CallUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.record.MonthlyReader reader(String pathAccountSid);
----
-The call API is defined in the syntax as follows:
+The usage-record-monthly API is defined in the syntax as follows:
----
-twilio:call/methodName?[parameters]
+twilio:usage-record-monthly/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CallCreator to execute create
-| *deleter* | delete | Create a CallDeleter to execute delete
-| *fetcher* | fetch | Create a CallFetcher to execute fetch
-| *reader* | read | Create a CallReader to execute read
-| *updater* | update | Create a CallUpdater to execute update
+| *reader* | read | Create a MonthlyReader to execute read
|===
-The call API method(s) has the following set of parameters listed in the table below:
+The usage-record-monthly API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *applicationSid* | The SID of the Application resource that will handle the call | String
-| creator | *from* | Twilio number from which to originate the call | Endpoint
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *to* | Phone number, SIP address, or client identifier to call | Endpoint
-| creator | *twiml* | TwiML instructions for the call | Twiml
-| creator | *url* | The absolute URL that returns TwiML for this call | URI
-| deleter | *pathAccountSid* | The SID of the Account that created the resource(s) to delete | String
-| deleter | *pathSid* | The unique string that identifies this resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathSid* | The SID of the Call resource to fetch | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathSid* | The unique string that identifies this resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the call API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-monthly API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3288,51 +3321,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number-local
+==== API: usage-record-this-month
-The incoming-phone-number-local API has 2 method(s) which is represented by the following method signatures
+The usage-record-this-month API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader();
+com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader();
-com.twilio.rest.api.v2010.account.incomingphonenumber.LocalReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.usage.record.ThisMonthReader reader(String pathAccountSid);
----
-The incoming-phone-number-local API is defined in the syntax as follows:
+The usage-record-this-month API is defined in the syntax as follows:
----
-twilio:incoming-phone-number-local/methodName?[parameters]
+twilio:usage-record-this-month/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a LocalCreator to execute create
-| *reader* | read | Create a LocalReader to execute read
+| *reader* | read | Create a ThisMonthReader to execute read
|===
-The incoming-phone-number-local API method(s) has the following set of parameters listed in the table below:
+The usage-record-this-month API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the incoming-phone-number-local API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-this-month API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3342,25 +3368,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: message-feedback
+==== API: usage-record-today
-The message-feedback API has 1 method(s) which is represented by the following method signatures
+The usage-record-today API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathAccountSid, String pathMessageSid);
+com.twilio.rest.api.v2010.account.usage.record.TodayReader reader();
-com.twilio.rest.api.v2010.account.message.FeedbackCreator creator(String pathMessageSid);
+com.twilio.rest.api.v2010.account.usage.record.TodayReader reader(String pathAccountSid);
----
-The message-feedback API is defined in the syntax as follows:
+The usage-record-today API is defined in the syntax as follows:
----
-twilio:message-feedback/methodName?[parameters]
+twilio:usage-record-today/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -3369,18 +3395,17 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a FeedbackCreator to execute create
+| *reader* | read | Create a TodayReader to execute read
|===
-The message-feedback API method(s) has the following set of parameters listed in the table below:
+The usage-record-today API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *pathMessageSid* | The SID of the Message resource for which the feedback was provided | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the message-feedback API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-today API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3390,58 +3415,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: recording
+==== API: usage-record-yearly
-The recording API has 3 method(s) which is represented by the following method signatures
+The usage-record-yearly API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.RecordingReader reader();
+com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader();
-com.twilio.rest.api.v2010.account.RecordingReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.usage.record.YearlyReader reader(String pathAccountSid);
----
-The recording API is defined in the syntax as follows:
+The usage-record-yearly API is defined in the syntax as follows:
----
-twilio:recording/methodName?[parameters]
+twilio:usage-record-yearly/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a RecordingDeleter to execute delete
-| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
-| *reader* | read | Create a RecordingReader to execute read
+| *reader* | read | Create a YearlyReader to execute read
|===
-The recording API method(s) has the following set of parameters listed in the table below:
+The usage-record-yearly API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the recording API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-yearly API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3451,51 +3462,44 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: incoming-phone-number-mobile
+==== API: usage-record-yesterday
-The incoming-phone-number-mobile API has 2 method(s) which is represented by the following method signatures
+The usage-record-yesterday API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileCreator creator(com.twilio.type.PhoneNumber phoneNumber);
-
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader();
+com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader();
-com.twilio.rest.api.v2010.account.incomingphonenumber.MobileReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.usage.record.YesterdayReader reader(String pathAccountSid);
----
-The incoming-phone-number-mobile API is defined in the syntax as follows:
+The usage-record-yesterday API is defined in the syntax as follows:
----
-twilio:incoming-phone-number-mobile/methodName?[parameters]
+twilio:usage-record-yesterday/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a MobileCreator to execute create
-| *reader* | read | Create a MobileReader to execute read
+| *reader* | read | Create a YesterdayReader to execute read
|===
-The incoming-phone-number-mobile API method(s) has the following set of parameters listed in the table below:
+The usage-record-yesterday API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *phoneNumber* | The phone number to purchase in E.164 format | PhoneNumber
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
|===
-In addition to the parameters above, the incoming-phone-number-mobile API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-record-yesterday API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3505,50 +3509,74 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: account
+==== API: usage-trigger
-The account API has 2 method(s) which is represented by the following method signatures
+The usage-trigger API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.AccountFetcher fetcher();
+com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(String pathAccountSid, java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
-com.twilio.rest.api.v2010.AccountFetcher fetcher(String pathSid);
+com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
-com.twilio.rest.api.v2010.AccountUpdater updater();
+com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.AccountUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerReader reader();
+
+com.twilio.rest.api.v2010.account.usage.TriggerReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathSid);
----
-The account API is defined in the syntax as follows:
+The usage-trigger API is defined in the syntax as follows:
----
-twilio:account/methodName?[parameters]
+twilio:usage-trigger/methodName?[parameters]
----
-The 2 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a AccountFetcher to execute fetch
-| *updater* | update | Create a AccountUpdater to execute update
+| *creator* | create | Create a TriggerCreator to execute create
+| *deleter* | delete | Create a TriggerDeleter to execute delete
+| *fetcher* | fetch | Create a TriggerFetcher to execute fetch
+| *reader* | read | Create a TriggerReader to execute read
+| *updater* | update | Create a TriggerUpdater to execute update
|===
-The account API method(s) has the following set of parameters listed in the table below:
+The usage-trigger API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathSid* | Fetch by unique Account Sid | String
-| updater | *pathSid* | Update by unique Account Sid | String
+| creator | *callbackUrl* | The URL we call when the trigger fires | URI
+| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
+| creator | *triggerValue* | The usage value at which the trigger should fire | String
+| creator | *usageCategory* | The usage category the trigger watches | UsageCategory
+| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the account API can also use from the 23 endpoint query option
+In addition to the parameters above, the usage-trigger API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -3558,73 +3586,45 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: sip-credential-list
+==== API: validation-request
-The sip-credential-list API has 5 method(s) which is represented by the following method signatures
+The validation-request API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListCreator creator(String pathAccountSid, String friendlyName);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListDeleter deleter(String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathAccountSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListFetcher fetcher(String pathSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListReader reader();
-
-com.twilio.rest.api.v2010.account.sip.CredentialListReader reader(String pathAccountSid);
-
-com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathAccountSid, String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(String pathAccountSid, com.twilio.type.PhoneNumber phoneNumber);
-com.twilio.rest.api.v2010.account.sip.CredentialListUpdater updater(String pathSid, String friendlyName);
+com.twilio.rest.api.v2010.account.ValidationRequestCreator creator(com.twilio.type.PhoneNumber phoneNumber);
----
-The sip-credential-list API is defined in the syntax as follows:
+The validation-request API is defined in the syntax as follows:
----
-twilio:sip-credential-list/methodName?[parameters]
+twilio:validation-request/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a CredentialListCreator to execute create
-| *deleter* | delete | Create a CredentialListDeleter to execute delete
-| *fetcher* | fetch | Create a CredentialListFetcher to execute fetch
-| *reader* | read | Create a CredentialListReader to execute read
-| *updater* | update | Create a CredentialListUpdater to execute update
+| *creator* | create | Create a ValidationRequestCreator to execute create
|===
-The sip-credential-list API method(s) has the following set of parameters listed in the table below:
+The validation-request API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *friendlyName* | Human readable descriptive text | String
-| creator | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| deleter | *pathSid* | Delete by unique credential list Sid | String
-| fetcher | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| fetcher | *pathSid* | Fetch by unique credential list Sid | String
-| reader | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| updater | *friendlyName* | Human readable descriptive text | String
-| updater | *pathAccountSid* | The unique id of the Account that is responsible for this resource | String
-| updater | *pathSid* | Update by unique credential list Sid | String
+| creator | *pathAccountSid* | The SID of the Account responsible for the new Caller ID | String
+| creator | *phoneNumber* | The phone number to verify in E.164 format | PhoneNumber
|===
-In addition to the parameters above, the sip-credential-list API can also use from the 23 endpoint query option
+In addition to the parameters above, the validation-request API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
diff --git a/docs/components/modules/ROOT/pages/twilio-component.adoc b/docs/components/modules/ROOT/pages/twilio-component.adoc
index c222545..6f6d91e 100644
--- a/docs/components/modules/ROOT/pages/twilio-component.adoc
+++ b/docs/components/modules/ROOT/pages/twilio-component.adoc
@@ -118,125 +118,111 @@ There are 56 API groups as listed in the table below:
[width="100%",cols="2,8",options="header"]
|===
| API Name | Description
-| *recording-add-on-result-payload* |
-| *usage-record-today* |
+| *account* |
+| *address* |
+| *address-dependent-phone-number* |
+| *application* |
+| *available-phone-number-country* |
| *available-phone-number-country-local* |
-| *call-recording* |
-| *queue-member* |
-| *usage-trigger* |
-| *usage-record-all-time* |
-| *usage-record-last-month* |
-| *recording-transcription* |
-| *message* |
+| *available-phone-number-country-mobile* |
+| *available-phone-number-country-toll-free* |
+| *call* |
+| *call-feedback* |
| *call-feedback-summary* |
-| *sip-credential-list-credential* |
-| *new-key* |
-| *incoming-phone-number* |
| *call-notification* |
-| *validation-request* |
-| *usage-record-yesterday* |
-| *usage-record-this-month* |
-| *new-signing-key* |
+| *call-recording* |
| *conference* |
-| *usage-record-daily* |
-| *application* |
-| *usage-record* |
-| *available-phone-number-country-mobile* |
| *conference-participant* |
+| *connect-app* |
+| *incoming-phone-number* |
+| *incoming-phone-number-local* |
+| *incoming-phone-number-mobile* |
+| *incoming-phone-number-toll-free* |
+| *key* |
+| *message* |
+| *message-feedback* |
+| *message-media* |
+| *new-key* |
+| *new-signing-key* |
| *notification* |
+| *outgoing-caller-id* |
+| *queue* |
+| *queue-member* |
+| *recording* |
| *recording-add-on-result* |
-| *sip-domain-ip-access-control-list-mapping* |
+| *recording-add-on-result-payload* |
+| *recording-transcription* |
+| *short-code* |
+| *signing-key* |
+| *sip-credential-list* |
+| *sip-credential-list-credential* |
| *sip-domain* |
-| *address* |
-| *message-media* |
-| *sip-ip-access-control-list-ip-address* |
-| *available-phone-number-country* |
-| *usage-record-yearly* |
-| *queue* |
-| *transcription* |
| *sip-domain-credential-list-mapping* |
-| *call-feedback* |
-| *key* |
-| *incoming-phone-number-toll-free* |
+| *sip-domain-ip-access-control-list-mapping* |
+| *sip-ip-access-control-list* |
+| *sip-ip-access-control-list-ip-address* |
| *token* |
-| *short-code* |
-| *available-phone-number-country-toll-free* |
+| *transcription* |
+| *usage-record* |
+| *usage-record-all-time* |
+| *usage-record-daily* |
+| *usage-record-last-month* |
| *usage-record-monthly* |
-| *sip-ip-access-control-list* |
-| *connect-app* |
-| *address-dependent-phone-number* |
-| *signing-key* |
-| *outgoing-caller-id* |
-| *call* |
-| *incoming-phone-number-local* |
-| *message-feedback* |
-| *recording* |
-| *incoming-phone-number-mobile* |
-| *account* |
-| *sip-credential-list* |
+| *usage-record-this-month* |
+| *usage-record-today* |
+| *usage-record-yearly* |
+| *usage-record-yesterday* |
+| *usage-trigger* |
+| *validation-request* |
|===
Each API is documented in the following sections to come.
-==== API: recording-add-on-result-payload
+==== API: account
-The recording-add-on-result-payload API has 3 method(s) which is represented by the following method signatures
+The account API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadDeleter deleter(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
-
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+com.twilio.rest.api.v2010.AccountFetcher fetcher();
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadFetcher fetcher(String pathReferenceSid, String pathAddOnResultSid, String pathSid);
+com.twilio.rest.api.v2010.AccountFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathAccountSid, String pathReferenceSid, String pathAddOnResultSid);
+com.twilio.rest.api.v2010.AccountUpdater updater();
-com.twilio.rest.api.v2010.account.recording.addonresult.PayloadReader reader(String pathReferenceSid, String pathAddOnResultSid);
+com.twilio.rest.api.v2010.AccountUpdater updater(String pathSid);
----
-The recording-add-on-result-payload API is defined in the syntax as follows:
+The account API is defined in the syntax as follows:
----
-twilio:recording-add-on-result-payload/methodName?[parameters]
+twilio:account/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *deleter* | delete | Create a PayloadDeleter to execute delete
-| *fetcher* | fetch | Create a PayloadFetcher to execute fetch
-| *reader* | read | Create a PayloadReader to execute read
+| *fetcher* | fetch | Create a AccountFetcher to execute fetch
+| *updater* | update | Create a AccountUpdater to execute update
|===
-The recording-add-on-result-payload API method(s) has the following set of parameters listed in the table below:
+The account API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| deleter | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| fetcher | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
-| fetcher | *pathSid* | The unique string that identifies the resource to fetch | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathAddOnResultSid* | The SID of the AddOnResult to which the payloads to delete belongs | String
-| reader | *pathReferenceSid* | The SID of the recording to which the AddOnResult resource that contains the payloads to delete belongs | String
+| fetcher | *pathSid* | Fetch by unique Account Sid | String
+| updater | *pathSid* | Update by unique Account Sid | String
|===
-In addition to the parameters above, the recording-add-on-result-payload API can also use from the 23 endpoint query option
+In addition to the parameters above, the account API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -246,44 +232,77 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-today
+==== API: address
-The usage-record-today API has 1 method(s) which is represented by the following method signatures
+The address API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.TodayReader reader();
+com.twilio.rest.api.v2010.account.AddressCreator creator(String customerName, String street, String city, String region, String postalCode, String isoCountry);
-com.twilio.rest.api.v2010.account.usage.record.TodayReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.AddressCreator creator(String pathAccountSid, String customerName, String street, String city, String region, String postalCode, String isoCountry);
+
+com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressDeleter deleter(String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressFetcher fetcher(String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressReader reader();
+
+com.twilio.rest.api.v2010.account.AddressReader reader(String pathAccountSid);
+
+com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathAccountSid, String pathSid);
+
+com.twilio.rest.api.v2010.account.AddressUpdater updater(String pathSid);
----
-The usage-record-today API is defined in the syntax as follows:
+The address API is defined in the syntax as follows:
----
-twilio:usage-record-today/methodName?[parameters]
+twilio:address/methodName?[parameters]
----
-The 1 method(s) is listed in the table below.
+The 5 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a TodayReader to execute read
+| *creator* | create | Create a AddressCreator to execute create
+| *deleter* | delete | Create a AddressDeleter to execute delete
+| *fetcher* | fetch | Create a AddressFetcher to execute fetch
+| *reader* | read | Create a AddressReader to execute read
+| *updater* | update | Create a AddressUpdater to execute update
|===
-The usage-record-today API method(s) has the following set of parameters listed in the table below:
+The address API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| creator | *city* | The city of the new address | String
+| creator | *customerName* | The name to associate with the new address | String
+| creator | *isoCountry* | The ISO country code of the new address | String
+| creator | *pathAccountSid* | The SID of the Account that will be responsible for the new Address resource | String
+| creator | *postalCode* | The postal code of the new address | String
+| creator | *region* | The state or region of the new address | String
+| creator | *street* | The number and street address of the new address | String
+| deleter | *pathAccountSid* | The SID of the Account that is responsible for the resources to delete | String
+| deleter | *pathSid* | The unique string that identifies the resource | String
+| fetcher | *pathAccountSid* | The SID of the Account that is responsible for this address | String
+| fetcher | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account that is responsible for this address | String
+| updater | *pathAccountSid* | The SID of the Account that is responsible for the resource to update | String
+| updater | *pathSid* | The unique string that identifies the resource | String
|===
-In addition to the parameters above, the usage-record-today API can also use from the 23 endpoint query option
+In addition to the parameters above, the address API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -293,25 +312,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: available-phone-number-country-local
+==== API: address-dependent-phone-number
-The available-phone-number-country-local API has 1 method(s) which is represented by the following method signatures
+The address-dependent-phone-number API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathAccountSid, String pathCountryCode);
+com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAccountSid, String pathAddressSid);
-com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathCountryCode);
+com.twilio.rest.api.v2010.account.address.DependentPhoneNumberReader reader(String pathAddressSid);
----
-The available-phone-number-country-local API is defined in the syntax as follows:
+The address-dependent-phone-number API is defined in the syntax as follows:
----
-twilio:available-phone-number-country-local/methodName?[parameters]
+twilio:address-dependent-phone-number/methodName?[parameters]
----
The 1 method(s) is listed in the table below.
@@ -320,18 +339,18 @@ The 1 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *reader* | read | Create a LocalReader to execute read
+| *reader* | read | Create a DependentPhoneNumberReader to execute read
|===
-The available-phone-number-country-local API method(s) has the following set of parameters listed in the table below:
+The address-dependent-phone-number API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
-| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
+| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
+| reader | *pathAddressSid* | The SID of the Address resource associated with the phone number | String
|===
-In addition to the parameters above, the available-phone-number-country-local API can also use from the 23 endpoint query option
+In addition to the parameters above, the address-dependent-phone-number API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -341,41 +360,41 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: call-recording
+==== API: application
-The call-recording API has 5 method(s) which is represented by the following method signatures
+The application API has 5 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationCreator creator();
-com.twilio.rest.api.v2010.account.call.RecordingCreator creator(String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationCreator creator(String pathAccountSid);
-com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingDeleter deleter(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathAccountSid, String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingFetcher fetcher(String pathCallSid, String pathSid);
+com.twilio.rest.api.v2010.account.ApplicationFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathAccountSid, String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationReader reader();
-com.twilio.rest.api.v2010.account.call.RecordingReader reader(String pathCallSid);
+com.twilio.rest.api.v2010.account.ApplicationReader reader(String pathAccountSid);
-com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathAccountSid, String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.call.RecordingUpdater updater(String pathCallSid, String pathSid, com.twilio.rest.api.v2010.account.call.Recording.Status status);
+com.twilio.rest.api.v2010.account.ApplicationUpdater updater(String pathSid);
----
-The call-recording API is defined in the syntax as follows:
+The application API is defined in the syntax as follows:
----
-twilio:call-recording/methodName?[parameters]
+twilio:application/methodName?[parameters]
----
The 5 method(s) is listed in the table below.
@@ -384,34 +403,28 @@ The 5 method(s) is listed in the table below.
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a RecordingCreator to execute create
-| *deleter* | delete | Create a RecordingDeleter to execute delete
-| *fetcher* | fetch | Create a RecordingFetcher to execute fetch
-| *reader* | read | Create a RecordingReader to execute read
-| *updater* | update | Create a RecordingUpdater to execute update
+| *creator* | create | Create a ApplicationCreator to execute create
+| *deleter* | delete | Create a ApplicationDeleter to execute delete
+| *fetcher* | fetch | Create a ApplicationFetcher to execute fetch
+| *reader* | read | Create a ApplicationReader to execute read
+| *updater* | update | Create a ApplicationUpdater to execute update
|===
-The call-recording API method(s) has the following set of parameters listed in the table below:
+The application API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *pathCallSid* | The SID of the Call to associate the resource with | String
| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathCallSid* | The SID of the Call to associate the resource with | String
| deleter | *pathSid* | The unique string that identifies the resource | String
| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathCallSid* | The SID of the Call to associate the resource with | String
| fetcher | *pathSid* | The unique string that identifies the resource | String
| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| reader | *pathCallSid* | The SID of the Call to associate the resource with | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource to update | String
-| updater | *pathCallSid* | The SID of the Call to associate the resource with | String
+| updater | *pathAccountSid* | The SID of the Account that will create the resource | String
| updater | *pathSid* | The unique string that identifies the resource | String
-| updater | *status* | The new status of the recording | Status
|===
-In addition to the parameters above, the call-recording API can also use from the 23 endpoint query option
+In addition to the parameters above, the application API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -421,139 +434,99 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: queue-member
+==== API: available-phone-number-country
-The queue-member API has 3 method(s) which is represented by the following method signatures
+The available-phone-number-country API has 2 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathAccountSid, String pathQueueSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.queue.MemberFetcher fetcher(String pathQueueSid, String pathCallSid);
-
-com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathAccountSid, String pathQueueSid);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.queue.MemberReader reader(String pathQueueSid);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryFetcher fetcher(String pathCountryCode);
-com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathAccountSid, String pathQueueSid, String pathCallSid, java.net.URI url);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader();
-com.twilio.rest.api.v2010.account.queue.MemberUpdater updater(String pathQueueSid, String pathCallSid, java.net.URI url);
+com.twilio.rest.api.v2010.account.AvailablePhoneNumberCountryReader reader(String pathAccountSid);
----
-The queue-member API is defined in the syntax as follows:
+The available-phone-number-country API is defined in the syntax as follows:
----
-twilio:queue-member/methodName?[parameters]
+twilio:available-phone-number-country/methodName?[parameters]
----
-The 3 method(s) is listed in the table below.
+The 2 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *fetcher* | fetch | Create a MemberFetcher to execute fetch
-| *reader* | read | Create a MemberReader to execute read
-| *updater* | update | Create a MemberUpdater to execute update
+| *fetcher* | fetch | Create a AvailablePhoneNumberCountryFetcher to execute fetch
+| *reader* | read | Create a AvailablePhoneNumberCountryReader to execute read
|===
-The queue-member API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource(s) to fetch | String
-| fetcher | *pathCallSid* | The Call SID of the resource(s) to fetch | String
-| fetcher | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| reader | *pathAccountSid* | The SID of the Account that created the resource(s) to read | String
-| reader | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| updater | *pathAccountSid* | The SID of the Account that created the resource(s) to update | String
-| updater | *pathCallSid* | The Call SID of the resource(s) to update | String
-| updater | *pathQueueSid* | The SID of the Queue in which to find the members | String
-| updater | *url* | The absolute URL of the Queue resource | URI
+| fetcher | *pathAccountSid* | The SID of the Account requesting the available phone number Country resource | String
+| fetcher | *pathCountryCode* | The ISO country code of the country to fetch available phone number information about | String
+| reader | *pathAccountSid* | The SID of the Account requesting the available phone number Country resources | String
|===
-In addition to the parameters above, the queue-member API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
-The message header name must be of the format `CamelTwilio.parameter`.
-The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
-would override a `CamelTwilio.myParameterNameHere` header.
-
-
-
-==== API: usage-trigger
-
-
-The usage-trigger API has 5 method(s) which is represented by the following method signatures
-(an API method may have multiple signatures due to overloading):
-
-[source,java]
-----
-
-com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(String pathAccountSid, java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
-
-com.twilio.rest.api.v2010.account.usage.TriggerCreator creator(java.net.URI callbackUrl, String triggerValue, com.twilio.rest.api.v2010.account.usage.Trigger.UsageCategory usageCategory);
+The message header name must be of the format `CamelTwilio.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelTwilio.myParameterNameHere` header.
-com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathAccountSid, String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerDeleter deleter(String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathAccountSid, String pathSid);
+==== API: available-phone-number-country-local
-com.twilio.rest.api.v2010.account.usage.TriggerFetcher fetcher(String pathSid);
-com.twilio.rest.api.v2010.account.usage.TriggerReader reader();
+The available-phone-number-country-local API has 1 method(s) which is represented by the following method signatures
+(an API method may have multiple signatures due to overloading):
-com.twilio.rest.api.v2010.account.usage.TriggerReader reader(String pathAccountSid);
+[source,java]
+----
-com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathAccountSid, String pathSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.TriggerUpdater updater(String pathSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.LocalReader reader(String pathCountryCode);
----
-The usage-trigger API is defined in the syntax as follows:
+The available-phone-number-country-local API is defined in the syntax as follows:
----
-twilio:usage-trigger/methodName?[parameters]
+twilio:available-phone-number-country-local/methodName?[parameters]
----
-The 5 method(s) is listed in the table below.
+The 1 method(s) is listed in the table below.
(API methods can have a shorthand alias name which can be used in the syntax instead of the name)
[width="100%",cols="2,2,6",options="header"]
|===
| Method | Alias | Description
-| *creator* | create | Create a TriggerCreator to execute create
-| *deleter* | delete | Create a TriggerDeleter to execute delete
-| *fetcher* | fetch | Create a TriggerFetcher to execute fetch
-| *reader* | read | Create a TriggerReader to execute read
-| *updater* | update | Create a TriggerUpdater to execute update
+| *reader* | read | Create a LocalReader to execute read
|===
-The usage-trigger API method(s) has the following set of parameters listed in the table below:
+The available-phone-number-country-local API method(s) has the following set of parameters listed in the table below:
[width="100%",cols="2,2,4,2",options="header"]
|===
| Method | Parameter | Description | Type
-| creator | *callbackUrl* | The URL we call when the trigger fires | URI
-| creator | *pathAccountSid* | The SID of the Account that will create the resource | String
-| creator | *triggerValue* | The usage value at which the trigger should fire | String
-| creator | *usageCategory* | The usage category the trigger watches | UsageCategory
-| deleter | *pathAccountSid* | The SID of the Account that created the resources to delete | String
-| deleter | *pathSid* | The unique string that identifies the resource | String
-| fetcher | *pathAccountSid* | The SID of the Account that created the resource to fetch | String
-| fetcher | *pathSid* | The unique string that identifies the resource | String
-| reader | *pathAccountSid* | The SID of the Account that created the resources to read | String
-| updater | *pathAccountSid* | The SID of the Account that created the resources to update | String
-| updater | *pathSid* | The unique string that identifies the resource | String
+| reader | *pathAccountSid* | The SID of the Account requesting the AvailablePhoneNumber resources | String
+| reader | *pathCountryCode* | The ISO Country code of the country from which to read phone numbers | String
|===
-In addition to the parameters above, the usage-trigger API can also use from the 23 endpoint query option
+In addition to the parameters above, the available-phone-number-country-local API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
Any of the parameters can be provided in either the endpoint URI, or dynamically in a message header.
@@ -563,25 +536,25 @@ would override a `CamelTwilio.myParameterNameHere` header.
-==== API: usage-record-all-time
+==== API: available-phone-number-country-mobile
-The usage-record-all-time API has 1 method(s) which is represented by the following method signatures
+The available-phone-number-country-mobile API has 1 method(s) which is represented by the following method signatures
(an API method may have multiple signatures due to overloading):
[source,java]
----
-com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader();
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathAccountSid, String pathCountryCode);
-com.twilio.rest.api.v2010.account.usage.record.AllTimeReader reader(String pathAccountSid);
+com.twilio.rest.api.v2010.account.availablephonenumbercountry.MobileReader reader(String pathCountryCode);
----
-The usage-record-all-time API is defined in the syntax as follows:
+The available-phone-number-country-mobile API is defined in the syntax as follows:
----
-twilio:usage-record-all-time/methodName?[parameters]
... 4016 lines suppressed ...