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/17 16:23:44 UTC
[camel] branch api updated (378b199 -> c9e2f4a)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch api
in repository https://gitbox.apache.org/repos/asf/camel.git.
from 378b199 CAMEL-15478: Docs include method table
new 941d444 CAMEL-15478: Include more details in docs
new 399200e CAMEL-15478: Delete file no longer in use
new c9e2f4a CAMEL-15478: Include more details in docs
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../src/main/docs/as2-component.adoc | 14 +
.../src/main/docs/box-component.adoc | 70 ++++
.../src/main/docs/braintree-component.adoc | 98 ++++++
.../src/main/docs/fhir-component.adoc | 91 +++++
.../src/main/docs/google-calendar-component.adoc | 49 +++
.../docs/google-calendar-stream-component.adoc | 49 +++
.../src/main/docs/google-drive-component.adoc | 84 +++++
.../src/main/docs/google-mail-component.adoc | 49 +++
.../main/docs/google-mail-stream-component.adoc | 49 +++
.../src/main/docs/google-sheets-component.adoc | 14 +
.../main/docs/google-sheets-stream-component.adoc | 14 +
.../src/main/docs/olingo2-component.adoc | 7 +
.../src/main/docs/olingo4-component.adoc | 7 +
.../src/main/docs/twilio-component.adoc | 392 +++++++++++++++++++++
.../src/main/docs/zendesk-component.adoc | 7 +
.../java/org/apache/camel/util/StringHelper.java | 6 +
.../src/main/resources/api-document.vm | 242 -------------
.../apache/camel/maven/packaging/MvelHelper.java | 6 +
.../apache/camel/maven/packaging/SchemaHelper.java | 38 ++
.../src/main/resources/endpoint-options.mvel | 7 +
20 files changed, 1051 insertions(+), 242 deletions(-)
delete mode 100644 tooling/maven/camel-api-component-maven-plugin/src/main/resources/api-document.vm
[camel] 02/03: CAMEL-15478: Delete file no longer in use
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch api
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 399200e7c9181c2f1fc1e94f0fa9f322c648a780
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Thu Sep 17 18:00:29 2020 +0200
CAMEL-15478: Delete file no longer in use
---
.../src/main/resources/api-document.vm | 242 ---------------------
1 file changed, 242 deletions(-)
diff --git a/tooling/maven/camel-api-component-maven-plugin/src/main/resources/api-document.vm b/tooling/maven/camel-api-component-maven-plugin/src/main/resources/api-document.vm
deleted file mode 100644
index 3615887..0000000
--- a/tooling/maven/camel-api-component-maven-plugin/src/main/resources/api-document.vm
+++ /dev/null
@@ -1,242 +0,0 @@
-#*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- *#
-## ------------------------------------------------------------------------
-## Licensed to the Apache Software Foundation (ASF) under one or more
-## contributor license agreements. See the NOTICE file distributed with
-## this work for additional information regarding copyright ownership.
-## The ASF licenses this file to You under the Apache License, Version 2.0
-## (the "License"); you may not use this file except in compliance with
-## the License. You may obtain a copy of the License at
-##
-## http://www.apache.org/licenses/LICENSE-2.0
-##
-## Unless required by applicable law or agreed to in writing, software
-## distributed under the License is distributed on an "AS IS" BASIS,
-## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-## See the License for the specific language governing permissions and
-## limitations under the License.
-## ------------------------------------------------------------------------
-## api-document.vm
-<!DOCTYPE html>
-<html>
-<head>
- <title>${componentName} Component</title>
-</head>
-<style>
- table,th,td
- {
- border:1px solid black;
- border-collapse:collapse;
- }
- th,td
- {
- padding:5px;
- }
- th
- {
- text-align:left;
- }
-</style>
-<body>
- <h2>${componentName} Component</h2>
- <hr/>
- <h3>Component Description</h3>
- <p>Maven users will need to add the following dependency to their pom.xml for this component:</p>
- <code>
- <pre>
- <dependency>
- <groupId>${groupId}</groupId>
- <artifactId>${artifactId}</artifactId>
- <version>${version}</version>
- </dependency>
- </pre>
- </code>
-
- <h3>URI Format</h3>
- <hr/>
- <p>The ${componentName} Component uses the following URI format:</p>
- <pre>
- ${uriFormat}
- </pre>
-#set( $hasApiPrefix = $uriFormat.contains("-prefix") )
-#if( $hasApiPrefix )
- <p>Endpoint prefix can be one of:</p>
- <ul>
-#foreach( $name in $apiNames )
- <li>$name</li>
-#end
-#end
- </ul>
- <h3>${componentName}Component</h3>
- <hr/>
- <p>
- The ${componentName} Component can be configured with the options below.
- These options can be provided using the component's bean property <code>configuration</code> of type <code>$componentConfig.Name</code>.
- </p>
- <table>
- <tr>
- <th>Option</th>
- <th>Type</th>
- </tr>
-#foreach( $field in $componentConfigFields.entrySet() )
- <tr>
- <td>$field.Key</td>
- <td>$field.Value</td>
- </tr>
-#end
- </table>
- <h3>Producer Endpoints</h3>
- <hr/>
-#if( !$hasApiPrefix )
- <p>
- Producer endpoints can use endpoint names and options listed next.
- A shorthand alias can be used for some endpoints.
- </p>
-#else
- <p>
- Producer endpoints can use endpoint prefixes followed by endpoint names and associated options described next.
- A shorthand alias can be used for some endpoints. The endpoint URI MUST contain a prefix.
- </p>
-#end
- <p>
- Endpoint options that are not mandatory are denoted by [].
- When there are no mandatory options for an endpoint, one of the set of [] options MUST be provided.
- Producer endpoints can also use a special option <b><code>inBody</code></b> that in turn should contain
- the name of the endpoint option whose value will be contained in the Camel Exchange In message.
- </p>
- <p>
- Any of the endpoint options can be provided in either the endpoint URI, or dynamically in a message header.
- The message header name must be of the format <code>Camel${componentName}.<option></code>.
- Note that the <code>inBody</code> option overrides message header,
- i.e. the endpoint option <code>inBody=option</code> would override a <code>Camel${componentName}.option</code> header.
- </p>
-## single API use case, only list methods and options
-#if( !$hasApiPrefix )
-#set( $endpointConfig = $apiConfigs.get("") )
-#set( $endpoints = $helper.getEndpoints($apiMethods.get(""), $apiHelpers.get(""), $endpointConfig) )
- <table>
- <tr>
- <th>Endpoint</th>
- <th>Shorthand Alias</th>
- <th>Options</th>
- <th>Result Body Type</th>
- </tr>
-#foreach( $endpoint in $endpoints )
- <tr>
- <td>$endpoint.endpoint</td>
- <td>$endpoint.aliases</td>
- <td>$endpoint.options</td>
- <td>$endpoint.resultTypes</td>
- </tr>
-#end
- </table>
- <h3>URI Options</h3>
- <hr/>
-#set ( $nullableArguments = $apiHelpers.get("").NullableArguments )
-#if( !$nullableArguments.isEmpty )
- <p>
- If a value is not provided for one of the option(s) ${nullableArguments.toString()}
- either in the endpoint URI or in a message header, it will be assumed to be <code>null</code>.
- Note that the <code>null</code> value(s) will only be used if other options do not satisfy matching endpoints.
- </p>
-#end
- <table>
- <tr>
- <th>Name</th>
- <th>Type</th>
- </tr>
-#foreach( $field in $endpointConfig.DeclaredFields )
- <tr>
- <td>$field.Name</td>
- <td>$helper.getCanonicalName($field.Type)</td>
- </tr>
-#end
- </table>
-#else
-## multiple API use case, list API names and their methods and options
-#foreach( $apiMethod in $apiMethods.entrySet() )
-#set( $apiName = $apiMethod.Key )
- <h3>${foreach.count}. Endpoint Prefix <em>$apiName</em></h3>
- <hr/>
- <p>The following endpoints can be invoked with the prefix <code>$apiName</code> as follows:</p>
- <pre>
- ${scheme}://${apiName}/endpoint?[options]
- </pre>
- <table>
- <tr>
- <th>Endpoint</th>
- <th>Shorthand Alias</th>
- <th>Options</th>
- <th>Result Body Type</th>
- </tr>
-#set( $endpointConfig = $apiConfigs.get($apiName) )
-#set( $anApiHelper = $apiHelpers.get($apiName) )
-#set( $endpoints = $helper.getEndpoints($apiMethod.Value, $anApiHelper, $endpointConfig) )
-#foreach( $endpoint in $endpoints )
- <tr>
- <td>$endpoint.Endpoint</td>
- <td>$endpoint.Aliases</td>
- <td>$endpoint.Options</td>
- <td>$endpoint.ResultTypes</td>
- </tr>
-#end
- </table>
- <h4>URI Options for <em>$apiName</em></h4>
- <hr/>
-#set ( $nullableArguments = $anApiHelper.NullableArguments )
-#if( !$nullableArguments.Empty )
- <p>
- If a value is not provided for one of the option(s) ${nullableArguments.toString()}
- either in the endpoint URI or in a message header, it will be assumed to be <code>null</code>.
- Note that the <code>null</code> value(s) will only be used if other options do not satisfy matching endpoints.
- </p>
-#end
- <table>
- <tr>
- <th>Name</th>
- <th>Type</th>
- </tr>
-#foreach( $field in $endpointConfig.DeclaredFields )
- <tr>
- <td>$field.Name</td>
- <td>$helper.getCanonicalName($field)</td>
- </tr>
-#end
- </table>
-#end
-#end
- <h3>Consumer Endpoints</h3>
- <hr/>
- <p>
- Any of the producer endpoints can be used as a consumer endpoint.
- Consumer endpoints can use <a href="http://camel.apache.org/polling-consumer.html#PollingConsumer-ScheduledPollConsumerOptions">Scheduled Poll Consumer Options</a> with a <code>consumer.</code> prefix to schedule endpoint invocation.
- Consumer endpoints that return an array or collection will generate one exchange per element, and their routes will be executed once for each exchange.
- </p>
- <h3>Message Headers</h3>
- <hr/>
- <p>
- Any URI option can be provided in a message header for producer endpoints with a <code>Camel${componentName}.</code> prefix.
- </p>
- <h3>Message Body</h3>
- <hr/>
- <p>
- All result message bodies utilize objects provided by the underlying APIs used by the ${componentName}Component. Producer endpoints can specify the option name for incoming message body in the <code>inBody</code> endpoint URI parameter.
- For endpoints that return an array or collection, a consumer endpoint will map every element to distinct messages.
- </p>
-</body>
-</html>
-
[camel] 01/03: CAMEL-15478: Include more details in docs
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch api
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 941d4440cd0e38dc70348f23fe397a44100cbdea
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Thu Sep 17 17:59:15 2020 +0200
CAMEL-15478: Include more details in docs
---
.../src/main/java/org/apache/camel/maven/packaging/MvelHelper.java | 4 ++++
.../src/main/resources/endpoint-options.mvel | 7 +++++++
2 files changed, 11 insertions(+)
diff --git a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java
index 7acddcb..72dbe9e 100644
--- a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java
+++ b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java
@@ -47,6 +47,10 @@ public final class MvelHelper {
return escapedUrls;
}
+ public static String componentName(String scheme) {
+ return Character.toUpperCase(scheme.charAt(0)) + scheme.substring(1);
+ }
+
public static String formatSignature(String signature) {
signature = signature.replace('$', '.');
return signature + ";";
diff --git a/tooling/maven/camel-package-maven-plugin/src/main/resources/endpoint-options.mvel b/tooling/maven/camel-package-maven-plugin/src/main/resources/endpoint-options.mvel
index fa4d5b4..d6ca847 100644
--- a/tooling/maven/camel-package-maven-plugin/src/main/resources/endpoint-options.mvel
+++ b/tooling/maven/camel-package-maven-plugin/src/main/resources/endpoint-options.mvel
@@ -84,6 +84,13 @@ The @{api.name} API method(s) has the following set of parameters listed in the
In addition to the parameters above, the @{api.name} API can also use from the @{endpointParameterOptions.size()} endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `Camel@{util.componentName(scheme)}.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `Camel@{util.componentName(scheme)}.myParameterNameHere` header.
+
@end{}
@end{}
[camel] 03/03: CAMEL-15478: Include more details in docs
Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch api
in repository https://gitbox.apache.org/repos/asf/camel.git
commit c9e2f4aa1f50c875e1ba18f468933e01f2af7efc
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Thu Sep 17 18:22:59 2020 +0200
CAMEL-15478: Include more details in docs
---
.../src/main/docs/as2-component.adoc | 14 +
.../src/main/docs/box-component.adoc | 70 ++++
.../src/main/docs/braintree-component.adoc | 98 ++++++
.../src/main/docs/fhir-component.adoc | 91 +++++
.../src/main/docs/google-calendar-component.adoc | 49 +++
.../docs/google-calendar-stream-component.adoc | 49 +++
.../src/main/docs/google-drive-component.adoc | 84 +++++
.../src/main/docs/google-mail-component.adoc | 49 +++
.../main/docs/google-mail-stream-component.adoc | 49 +++
.../src/main/docs/google-sheets-component.adoc | 14 +
.../main/docs/google-sheets-stream-component.adoc | 14 +
.../src/main/docs/olingo2-component.adoc | 7 +
.../src/main/docs/olingo4-component.adoc | 7 +
.../src/main/docs/twilio-component.adoc | 392 +++++++++++++++++++++
.../src/main/docs/zendesk-component.adoc | 7 +
.../java/org/apache/camel/util/StringHelper.java | 6 +
.../apache/camel/maven/packaging/MvelHelper.java | 4 +-
.../apache/camel/maven/packaging/SchemaHelper.java | 38 ++
18 files changed, 1041 insertions(+), 1 deletion(-)
diff --git a/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc b/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
index 1b845c5..2e49953 100644
--- a/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
+++ b/components/camel-as2/camel-as2-component/src/main/docs/as2-component.adoc
@@ -210,6 +210,13 @@ The client API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the client API can also use from the 49 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelAs2.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelAs2.myParameterNameHere` header.
+
==== server
@@ -249,6 +256,13 @@ The server API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the server API can also use from the 49 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelAs2.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelAs2.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-box/camel-box-component/src/main/docs/box-component.adoc b/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
index 9cdd134..67fa993 100644
--- a/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
+++ b/components/camel-box/camel-box-component/src/main/docs/box-component.adoc
@@ -329,6 +329,13 @@ The files API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the files API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== search
@@ -370,6 +377,13 @@ The search API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the search API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== comments
@@ -433,6 +447,13 @@ The comments API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the comments API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== event-logs
@@ -476,6 +497,13 @@ The event-logs API method(s) has the following set of parameters listed in the t
In addition to the parameters above, the event-logs API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== collaborations
@@ -541,6 +569,13 @@ The collaborations API method(s) has the following set of parameters listed in t
In addition to the parameters above, the collaborations API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== tasks
@@ -618,6 +653,13 @@ The tasks API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the tasks API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== events
@@ -658,6 +700,13 @@ The events API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the events API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== groups
@@ -739,6 +788,13 @@ The groups API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the groups API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== users
@@ -825,6 +881,13 @@ The users API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the users API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
+
==== folders
@@ -917,6 +980,13 @@ The folders API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the folders API can also use from the 38 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelBox.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBox.myParameterNameHere` header.
// endpoint options: END
== URI format
diff --git a/components/camel-braintree/src/main/docs/braintree-component.adoc b/components/camel-braintree/src/main/docs/braintree-component.adoc
index a2645d3..6c9a37a 100644
--- a/components/camel-braintree/src/main/docs/braintree-component.adoc
+++ b/components/camel-braintree/src/main/docs/braintree-component.adoc
@@ -184,6 +184,13 @@ The paymentMethodNonce API method(s) has the following set of parameters listed
In addition to the parameters above, the paymentMethodNonce API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== documentUpload
@@ -224,6 +231,13 @@ The documentUpload API method(s) has the following set of parameters listed in t
In addition to the parameters above, the documentUpload API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== subscription
@@ -298,6 +312,13 @@ The subscription API method(s) has the following set of parameters listed in the
In addition to the parameters above, the subscription API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== dispute
@@ -371,6 +392,13 @@ The dispute API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the dispute API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== settlementBatchSummary
@@ -414,6 +442,13 @@ The settlementBatchSummary API method(s) has the following set of parameters lis
In addition to the parameters above, the settlementBatchSummary API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== address
@@ -471,6 +506,13 @@ The address API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the address API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== webhookNotification
@@ -516,6 +558,13 @@ The webhookNotification API method(s) has the following set of parameters listed
In addition to the parameters above, the webhookNotification API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== creditCardVerification
@@ -564,6 +613,13 @@ The creditCardVerification API method(s) has the following set of parameters lis
In addition to the parameters above, the creditCardVerification API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== transaction
@@ -670,6 +726,13 @@ The transaction API method(s) has the following set of parameters listed in the
In addition to the parameters above, the transaction API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== report
@@ -710,6 +773,13 @@ The report API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the report API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== paymentMethod
@@ -777,6 +847,13 @@ The paymentMethod API method(s) has the following set of parameters listed in th
In addition to the parameters above, the paymentMethod API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== clientToken
@@ -819,6 +896,13 @@ The clientToken API method(s) has the following set of parameters listed in the
In addition to the parameters above, the clientToken API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== merchantAccount
@@ -876,6 +960,13 @@ The merchantAccount API method(s) has the following set of parameters listed in
In addition to the parameters above, the merchantAccount API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
+
==== customer
@@ -935,6 +1026,13 @@ The customer API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the customer API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelBraintree.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelBraintree.myParameterNameHere` header.
// endpoint options: END
== Producer Endpoints:
diff --git a/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc b/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc
index 90ccba4..b8e8435 100644
--- a/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc
+++ b/components/camel-fhir/camel-fhir-component/src/main/docs/fhir-component.adoc
@@ -241,6 +241,13 @@ The update API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the update API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== create
@@ -287,6 +294,13 @@ The create API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the create API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== validate
@@ -331,6 +345,13 @@ The validate API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the validate API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== operation
@@ -414,6 +435,13 @@ The operation API method(s) has the following set of parameters listed in the ta
In addition to the parameters above, the operation API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== search
@@ -455,6 +483,13 @@ The search API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the search API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== capabilities
@@ -496,6 +531,13 @@ The capabilities API method(s) has the following set of parameters listed in the
In addition to the parameters above, the capabilities API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== patch
@@ -549,6 +591,13 @@ The patch API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the patch API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== meta
@@ -614,6 +663,13 @@ The meta API method(s) has the following set of parameters listed in the table b
In addition to the parameters above, the meta API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== history
@@ -676,6 +732,13 @@ The history API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the history API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== load-page
@@ -728,6 +791,13 @@ The load-page API method(s) has the following set of parameters listed in the ta
In addition to the parameters above, the load-page API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== transaction
@@ -777,6 +847,13 @@ The transaction API method(s) has the following set of parameters listed in the
In addition to the parameters above, the transaction API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== read
@@ -855,6 +932,13 @@ The read API method(s) has the following set of parameters listed in the table b
In addition to the parameters above, the read API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
+
==== delete
@@ -909,6 +993,13 @@ The delete API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the delete API can also use from the 46 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelFhir.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelFhir.myParameterNameHere` header.
// endpoint options: END
include::camel-spring-boot::page$fhir-starter.adoc[]
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
index 5864b34..33f574c 100644
--- a/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-component.adoc
@@ -195,6 +195,13 @@ The settings API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the settings API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendar.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendar.myParameterNameHere` header.
+
==== freebusy
@@ -235,6 +242,13 @@ The freebusy API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the freebusy API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendar.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendar.myParameterNameHere` header.
+
==== events
@@ -328,6 +342,13 @@ The events API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the events API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendar.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendar.myParameterNameHere` header.
+
==== channels
@@ -368,6 +389,13 @@ The channels API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the channels API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendar.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendar.myParameterNameHere` header.
+
==== acl
@@ -440,6 +468,13 @@ The acl API method(s) has the following set of parameters listed in the table be
In addition to the parameters above, the acl API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendar.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendar.myParameterNameHere` header.
+
==== calendars
@@ -502,6 +537,13 @@ The calendars API method(s) has the following set of parameters listed in the ta
In addition to the parameters above, the calendars API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendar.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendar.myParameterNameHere` header.
+
==== list
@@ -563,6 +605,13 @@ The list API method(s) has the following set of parameters listed in the table b
In addition to the parameters above, the list API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelGoogleCalendar.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendar.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc b/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
index 008018c..bf7ef9d 100644
--- a/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
+++ b/components/camel-google-calendar/src/main/docs/google-calendar-stream-component.adoc
@@ -198,6 +198,13 @@ The settings API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the settings API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendarStream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendarStream.myParameterNameHere` header.
+
==== freebusy
@@ -238,6 +245,13 @@ The freebusy API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the freebusy API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendarStream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendarStream.myParameterNameHere` header.
+
==== events
@@ -331,6 +345,13 @@ The events API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the events API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendarStream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendarStream.myParameterNameHere` header.
+
==== channels
@@ -371,6 +392,13 @@ The channels API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the channels API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendarStream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendarStream.myParameterNameHere` header.
+
==== acl
@@ -443,6 +471,13 @@ The acl API method(s) has the following set of parameters listed in the table be
In addition to the parameters above, the acl API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendarStream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendarStream.myParameterNameHere` header.
+
==== calendars
@@ -505,6 +540,13 @@ The calendars API method(s) has the following set of parameters listed in the ta
In addition to the parameters above, the calendars API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogleCalendarStream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendarStream.myParameterNameHere` header.
+
==== list
@@ -566,6 +608,13 @@ The list API method(s) has the following set of parameters listed in the table b
In addition to the parameters above, the list API can also use from the 32 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelGoogleCalendarStream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogleCalendarStream.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-google-drive/src/main/docs/google-drive-component.adoc b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
index 3dd3a66..ea4a7ce 100644
--- a/components/camel-google-drive/src/main/docs/google-drive-component.adoc
+++ b/components/camel-google-drive/src/main/docs/google-drive-component.adoc
@@ -213,6 +213,13 @@ The drive-channels API method(s) has the following set of parameters listed in t
In addition to the parameters above, the drive-channels API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-revisions
@@ -275,6 +282,13 @@ The drive-revisions API method(s) has the following set of parameters listed in
In addition to the parameters above, the drive-revisions API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-replies
@@ -348,6 +362,13 @@ The drive-replies API method(s) has the following set of parameters listed in th
In addition to the parameters above, the drive-replies API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-permissions
@@ -419,6 +440,13 @@ The drive-permissions API method(s) has the following set of parameters listed i
In addition to the parameters above, the drive-permissions API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-parents
@@ -474,6 +502,13 @@ The drive-parents API method(s) has the following set of parameters listed in th
In addition to the parameters above, the drive-parents API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-apps
@@ -514,6 +549,13 @@ The drive-apps API method(s) has the following set of parameters listed in the t
In addition to the parameters above, the drive-apps API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-changes
@@ -558,6 +600,13 @@ The drive-changes API method(s) has the following set of parameters listed in th
In addition to the parameters above, the drive-changes API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-comments
@@ -625,6 +674,13 @@ The drive-comments API method(s) has the following set of parameters listed in t
In addition to the parameters above, the drive-comments API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-properties
@@ -692,6 +748,13 @@ The drive-properties API method(s) has the following set of parameters listed in
In addition to the parameters above, the drive-properties API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-realtime
@@ -739,6 +802,13 @@ The drive-realtime API method(s) has the following set of parameters listed in t
In addition to the parameters above, the drive-realtime API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-children
@@ -794,6 +864,13 @@ The drive-children API method(s) has the following set of parameters listed in t
In addition to the parameters above, the drive-children API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
+
==== drive-files
@@ -884,6 +961,13 @@ The drive-files API method(s) has the following set of parameters listed in the
In addition to the parameters above, the drive-files API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelGoogle-drive.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-drive.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-google-mail/src/main/docs/google-mail-component.adoc b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
index 04ed35b..710ed7e 100644
--- a/components/camel-google-mail/src/main/docs/google-mail-component.adoc
+++ b/components/camel-google-mail/src/main/docs/google-mail-component.adoc
@@ -210,6 +210,13 @@ The users API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the users API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail.myParameterNameHere` header.
+
==== threads
@@ -276,6 +283,13 @@ The threads API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the threads API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail.myParameterNameHere` header.
+
==== drafts
@@ -351,6 +365,13 @@ The drafts API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the drafts API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail.myParameterNameHere` header.
+
==== labels
@@ -418,6 +439,13 @@ The labels API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the labels API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail.myParameterNameHere` header.
+
==== history
@@ -458,6 +486,13 @@ The history API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the history API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail.myParameterNameHere` header.
+
==== attachments
@@ -500,6 +535,13 @@ The attachments API method(s) has the following set of parameters listed in the
In addition to the parameters above, the attachments API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail.myParameterNameHere` header.
+
==== messages
@@ -599,6 +641,13 @@ The messages API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the messages API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelGoogle-mail.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc b/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc
index 506d6fc..9772a95 100644
--- a/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc
+++ b/components/camel-google-mail/src/main/docs/google-mail-stream-component.adoc
@@ -197,6 +197,13 @@ The users API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the users API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail-stream.myParameterNameHere` header.
+
==== threads
@@ -263,6 +270,13 @@ The threads API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the threads API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail-stream.myParameterNameHere` header.
+
==== drafts
@@ -338,6 +352,13 @@ The drafts API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the drafts API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail-stream.myParameterNameHere` header.
+
==== labels
@@ -405,6 +426,13 @@ The labels API method(s) has the following set of parameters listed in the table
In addition to the parameters above, the labels API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail-stream.myParameterNameHere` header.
+
==== history
@@ -445,6 +473,13 @@ The history API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the history API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail-stream.myParameterNameHere` header.
+
==== attachments
@@ -487,6 +522,13 @@ The attachments API method(s) has the following set of parameters listed in the
In addition to the parameters above, the attachments API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-mail-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail-stream.myParameterNameHere` header.
+
==== messages
@@ -586,6 +628,13 @@ The messages API method(s) has the following set of parameters listed in the tab
In addition to the parameters above, the messages API can also use from the 30 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelGoogle-mail-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-mail-stream.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc b/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc
index 31837c7..487db2e 100644
--- a/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc
+++ b/components/camel-google-sheets/src/main/docs/google-sheets-component.adoc
@@ -211,6 +211,13 @@ The spreadsheets API method(s) has the following set of parameters listed in the
In addition to the parameters above, the spreadsheets API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-sheets.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-sheets.myParameterNameHere` header.
+
==== data
@@ -298,6 +305,13 @@ The data API method(s) has the following set of parameters listed in the table b
In addition to the parameters above, the data API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelGoogle-sheets.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-sheets.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc b/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc
index 8e18fc6..4d5129f 100644
--- a/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc
+++ b/components/camel-google-sheets/src/main/docs/google-sheets-stream-component.adoc
@@ -212,6 +212,13 @@ The spreadsheets API method(s) has the following set of parameters listed in the
In addition to the parameters above, the spreadsheets API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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 `CamelGoogle-sheets-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-sheets-stream.myParameterNameHere` header.
+
==== data
@@ -299,6 +306,13 @@ The data API method(s) has the following set of parameters listed in the table b
In addition to the parameters above, the data API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelGoogle-sheets-stream.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelGoogle-sheets-stream.myParameterNameHere` header.
// endpoint options: END
diff --git a/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc b/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
index 211c8a1..0a0ef80 100644
--- a/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
+++ b/components/camel-olingo2/camel-olingo2-component/src/main/docs/olingo2-component.adoc
@@ -258,6 +258,13 @@ The DEFAULT API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the DEFAULT API can also use from the 36 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelOlingo2.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelOlingo2.myParameterNameHere` header.
// endpoint options: END
== Producer Endpoints
diff --git a/components/camel-olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc b/components/camel-olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc
index 5a56fe9..078bade 100644
--- a/components/camel-olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc
+++ b/components/camel-olingo4/camel-olingo4-component/src/main/docs/olingo4-component.adoc
@@ -263,6 +263,13 @@ The DEFAULT API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the DEFAULT API can also use from the 34 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelOlingo4.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelOlingo4.myParameterNameHere` header.
// endpoint options: END
== Producer Endpoints
diff --git a/components/camel-twilio/src/main/docs/twilio-component.adoc b/components/camel-twilio/src/main/docs/twilio-component.adoc
index eeb3f0d..b4e5f7c 100644
--- a/components/camel-twilio/src/main/docs/twilio-component.adoc
+++ b/components/camel-twilio/src/main/docs/twilio-component.adoc
@@ -174,6 +174,13 @@ The recording-add-on-result-payload API method(s) has the following set of param
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.
+==== Message headers and body
+
+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.
+
==== usage-record-today
@@ -216,6 +223,13 @@ The usage-record-today API method(s) has the following set of parameters listed
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.
+==== Message headers and body
+
+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.
+
==== available-phone-number-country-local
@@ -259,6 +273,13 @@ The available-phone-number-country-local API method(s) has the following set of
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.
+==== Message headers and body
+
+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.
+
==== call-recording
@@ -334,6 +355,13 @@ The call-recording API method(s) has the following set of parameters listed in t
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.
+==== Message headers and body
+
+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.
+
==== queue-member
@@ -394,6 +422,13 @@ The queue-member API method(s) has the following set of parameters listed in the
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.
+==== Message headers and body
+
+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.
+
==== usage-trigger
@@ -466,6 +501,13 @@ The usage-trigger API method(s) has the following set of parameters listed in th
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.
+==== Message headers and body
+
+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.
+
==== usage-record-last-month
@@ -508,6 +550,13 @@ The usage-record-last-month API method(s) has the following set of parameters li
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.
+==== Message headers and body
+
+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.
+
==== usage-record-all-time
@@ -550,6 +599,13 @@ The usage-record-all-time API method(s) has the following set of parameters list
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.
+==== Message headers and body
+
+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.
+
==== recording-transcription
@@ -609,6 +665,13 @@ The recording-transcription API method(s) has the following set of parameters li
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.
+==== Message headers and body
+
+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.
+
==== message
@@ -696,6 +759,13 @@ The message API method(s) has the following set of parameters listed in the tabl
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.
+==== Message headers and body
+
+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.
+
==== call-feedback-summary
@@ -754,6 +824,13 @@ The call-feedback-summary API method(s) has the following set of parameters list
In addition to the parameters above, the call-feedback-summary API can also use from the 23 endpoint query option
which is listed in the _Query Parameters_ section.
+==== Message headers and body
+
+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.
+
==== sip-credential-list-credential
@@ -830,6 +907,13 @@ The sip-credential-list-credential API method(s) has the following set of parame
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.
+==== Message headers and body
+
+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.
+
==== new-key
@@ -872,6 +956,13 @@ The new-key API method(s) has the following set of parameters listed in the tabl
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.
+==== Message headers and body
+
+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.
+
==== incoming-phone-number
@@ -947,6 +1038,13 @@ The incoming-phone-number API method(s) has the following set of parameters list
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.
+==== Message headers and body
+
+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.
+
==== call-notification
@@ -998,6 +1096,13 @@ The call-notification API method(s) has the following set of parameters listed i
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.
+==== Message headers and body
+
+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.
+
==== validation-request
@@ -1041,6 +1146,13 @@ The validation-request API method(s) has the following set of parameters listed
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.
+==== Message headers and body
+
+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.
+
==== usage-record-yesterday
@@ -1083,6 +1195,13 @@ The usage-record-yesterday API method(s) has the following set of parameters lis
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.
+==== Message headers and body
+
+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.
+
==== usage-record-this-month
@@ -1125,6 +1244,13 @@ The usage-record-this-month API method(s) has the following set of parameters li
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.
+==== Message headers and body
+
+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.
+
==== new-signing-key
@@ -1167,6 +1293,13 @@ The new-signing-key API method(s) has the following set of parameters listed in
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.
+==== Message headers and body
+
+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.
+
==== conference
@@ -1223,6 +1356,13 @@ The conference API method(s) has the following set of parameters listed in the t
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.
+==== Message headers and body
+
+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.
+
==== usage-record-daily
@@ -1265,6 +1405,13 @@ The usage-record-daily API method(s) has the following set of parameters listed
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.
+==== Message headers and body
+
+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.
+
==== application
@@ -1334,6 +1481,13 @@ The application API method(s) has the following set of parameters listed in the
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.
+==== Message headers and body
+
+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.
+
==== usage-record
@@ -1376,6 +1530,13 @@ The usage-record API method(s) has the following set of parameters listed in the
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.
+==== Message headers and body
+
+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.
+
==== available-phone-number-country-mobile
@@ -1419,6 +1580,13 @@ The available-phone-number-country-mobile API method(s) has the following set of
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.
+==== Message headers and body
+
+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.
+
==== conference-participant
@@ -1495,6 +1663,13 @@ The conference-participant API method(s) has the following set of parameters lis
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.
+==== Message headers and body
+
+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.
+
==== recording-add-on-result
@@ -1554,6 +1729,13 @@ The recording-add-on-result API method(s) has the following set of parameters li
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.
+==== Message headers and body
+
+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.
+
==== notification
@@ -1603,6 +1785,13 @@ The notification API method(s) has the following set of parameters listed in the
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.
+==== Message headers and body
+
+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.
+
==== sip-domain-ip-access-control-list-mapping
@@ -1670,6 +1859,13 @@ The sip-domain-ip-access-control-list-mapping API method(s) has the following se
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.
+==== Message headers and body
+
+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.
+
==== sip-domain
@@ -1740,6 +1936,13 @@ The sip-domain API method(s) has the following set of parameters listed in the t
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.
+==== Message headers and body
+
+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.
+
==== address
@@ -1815,6 +2018,13 @@ The address API method(s) has the following set of parameters listed in the tabl
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.
+==== Message headers and body
+
+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.
+
==== message-media
@@ -1874,6 +2084,13 @@ The message-media API method(s) has the following set of parameters listed in th
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.
+==== Message headers and body
+
+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.
+
==== sip-ip-access-control-list-ip-address
@@ -1950,6 +2167,13 @@ The sip-ip-access-control-list-ip-address API method(s) has the following set of
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.
+==== Message headers and body
+
+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.
+
==== available-phone-number-country
@@ -1999,6 +2223,13 @@ The available-phone-number-country API method(s) has the following set of parame
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.
+==== Message headers and body
+
+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.
+
==== usage-record-yearly
@@ -2041,6 +2272,13 @@ The usage-record-yearly API method(s) has the following set of parameters listed
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.
+==== Message headers and body
+
+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.
+
==== queue
@@ -2111,6 +2349,13 @@ The queue API method(s) has the following set of parameters listed in the table
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.
+==== Message headers and body
+
+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.
+
==== transcription
@@ -2167,6 +2412,13 @@ The transcription API method(s) has the following set of parameters listed in th
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.
+==== Message headers and body
+
+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.
+
==== sip-domain-credential-list-mapping
@@ -2234,6 +2486,13 @@ The sip-domain-credential-list-mapping API method(s) has the following set of pa
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.
+==== Message headers and body
+
+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.
+
==== call-feedback
@@ -2293,6 +2552,13 @@ The call-feedback API method(s) has the following set of parameters listed in th
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.
+==== Message headers and body
+
+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.
+
==== key
@@ -2356,6 +2622,13 @@ The key API method(s) has the following set of parameters listed in the table be
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.
+==== Message headers and body
+
+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.
+
==== incoming-phone-number-toll-free
@@ -2405,6 +2678,13 @@ The incoming-phone-number-toll-free API method(s) has the following set of param
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.
+==== Message headers and body
+
+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.
+
==== token
@@ -2447,6 +2727,13 @@ The token API method(s) has the following set of parameters listed in the table
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.
+==== Message headers and body
+
+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.
+
==== short-code
@@ -2503,6 +2790,13 @@ The short-code API method(s) has the following set of parameters listed in the t
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.
+==== Message headers and body
+
+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.
+
==== available-phone-number-country-toll-free
@@ -2546,6 +2840,13 @@ The available-phone-number-country-toll-free API method(s) has the following set
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.
+==== Message headers and body
+
+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.
+
==== usage-record-monthly
@@ -2588,6 +2889,13 @@ The usage-record-monthly API method(s) has the following set of parameters liste
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.
+==== Message headers and body
+
+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.
+
==== sip-ip-access-control-list
@@ -2659,6 +2967,13 @@ The sip-ip-access-control-list API method(s) has the following set of parameters
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.
+==== Message headers and body
+
+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.
+
==== connect-app
@@ -2722,6 +3037,13 @@ The connect-app API method(s) has the following set of parameters listed in the
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.
+==== Message headers and body
+
+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.
+
==== address-dependent-phone-number
@@ -2765,6 +3087,13 @@ The address-dependent-phone-number API method(s) has the following set of parame
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.
+==== Message headers and body
+
+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.
+
==== signing-key
@@ -2828,6 +3157,13 @@ The signing-key API method(s) has the following set of parameters listed in the
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.
+==== Message headers and body
+
+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.
+
==== outgoing-caller-id
@@ -2891,6 +3227,13 @@ The outgoing-caller-id API method(s) has the following set of parameters listed
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.
+==== Message headers and body
+
+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.
+
==== call
@@ -2973,6 +3316,13 @@ The call API method(s) has the following set of parameters listed in the table b
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.
+==== Message headers and body
+
+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.
+
==== incoming-phone-number-local
@@ -3022,6 +3372,13 @@ The incoming-phone-number-local API method(s) has the following set of parameter
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.
+==== Message headers and body
+
+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.
+
==== message-feedback
@@ -3065,6 +3422,13 @@ The message-feedback API method(s) has the following set of parameters listed in
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.
+==== Message headers and body
+
+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.
+
==== recording
@@ -3121,6 +3485,13 @@ The recording API method(s) has the following set of parameters listed in the ta
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.
+==== Message headers and body
+
+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.
+
==== incoming-phone-number-mobile
@@ -3170,6 +3541,13 @@ The incoming-phone-number-mobile API method(s) has the following set of paramete
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.
+==== Message headers and body
+
+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.
+
==== account
@@ -3218,6 +3596,13 @@ The account API method(s) has the following set of parameters listed in the tabl
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.
+==== Message headers and body
+
+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.
+
==== sip-credential-list
@@ -3288,6 +3673,13 @@ The sip-credential-list API method(s) has the following set of parameters listed
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.
+
+==== Message headers and body
+
+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.
// endpoint options: END
== Producer Endpoints:
diff --git a/components/camel-zendesk/src/main/docs/zendesk-component.adoc b/components/camel-zendesk/src/main/docs/zendesk-component.adoc
index 57ebf1d..5b58633 100644
--- a/components/camel-zendesk/src/main/docs/zendesk-component.adoc
+++ b/components/camel-zendesk/src/main/docs/zendesk-component.adoc
@@ -1360,6 +1360,13 @@ The DEFAULT API method(s) has the following set of parameters listed in the tabl
In addition to the parameters above, the DEFAULT API can also use from the 28 endpoint query option
which is listed in the _Query Parameters_ section.
+
+==== Message headers and body
+
+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 `CamelZendesk.parameter`.
+The `inBody` parameter overrides message header, i.e. the endpoint parameter `inBody=myParameterNameHere`
+would override a `CamelZendesk.myParameterNameHere` header.
// endpoint options: END
diff --git a/core/camel-util/src/main/java/org/apache/camel/util/StringHelper.java b/core/camel-util/src/main/java/org/apache/camel/util/StringHelper.java
index 86210cc..19b274f 100644
--- a/core/camel-util/src/main/java/org/apache/camel/util/StringHelper.java
+++ b/core/camel-util/src/main/java/org/apache/camel/util/StringHelper.java
@@ -835,6 +835,12 @@ public final class StringHelper {
return m.matches();
}
+ /**
+ * Converts the string from camel case into dash format (helloGreatWorld -> hello-great-world)
+ *
+ * @param text the string
+ * @return the string camel cased
+ */
public static String camelCaseToDash(String text) {
if (text == null || text.isEmpty()) {
return text;
diff --git a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java
index 72dbe9e..b984551 100644
--- a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java
+++ b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/MvelHelper.java
@@ -48,7 +48,9 @@ public final class MvelHelper {
}
public static String componentName(String scheme) {
- return Character.toUpperCase(scheme.charAt(0)) + scheme.substring(1);
+ String text = SchemaHelper.dashToCamelCase(scheme);
+ // first char should be upper cased
+ return Character.toUpperCase(text.charAt(0)) + text.substring(1);
}
public static String formatSignature(String signature) {
diff --git a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaHelper.java b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaHelper.java
index f635654..d417d27 100644
--- a/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaHelper.java
+++ b/tooling/maven/camel-package-maven-plugin/src/main/java/org/apache/camel/maven/packaging/SchemaHelper.java
@@ -20,6 +20,44 @@ import java.util.Locale;
public final class SchemaHelper {
+ /**
+ * Converts the string from dash format into camel case (hello-great-world -> helloGreatWorld)
+ *
+ * @param text the string
+ * @return the string camel cased
+ */
+ public static String dashToCamelCase(String text) {
+ if (text == null) {
+ return null;
+ }
+ int length = text.length();
+ if (length == 0) {
+ return text;
+ }
+ if (text.indexOf('-') == -1) {
+ return text;
+ }
+
+ StringBuilder sb = new StringBuilder();
+
+ for (int i = 0; i < text.length(); i++) {
+ char c = text.charAt(i);
+ if (c == '-') {
+ i++;
+ sb.append(Character.toUpperCase(text.charAt(i)));
+ } else {
+ sb.append(c);
+ }
+ }
+ return sb.toString();
+ }
+
+ /**
+ * Converts the string from camel case into dash format (helloGreatWorld -> hello-great-world)
+ *
+ * @param text the string
+ * @return the string camel cased
+ */
public static String camelCaseToDash(String text) {
if (text == null || text.isEmpty()) {
return text;