Red Hat Training

A Red Hat training course is available for Red Hat Fuse

Chapter 345. Zendesk Component

Available as of Camel version 2.19

The Zendesk component provides access to all of the APIs accessible using zendesk-java-client. It allows producing messages to manage Zendesk ticket, user, organization, etc.

Maven users will need to add the following dependency to their pom.xml for this component:


345.1. Zendesk Options

The Zendesk component supports 3 options which are listed below.


configuration (common)

To use the shared configuration



zendesk (advanced)

To use a shared Zendesk instance.



resolveProperty Placeholders (advanced)

Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders.



The Zendesk endpoint is configured using URI syntax:


with the following path and query parameters:

345.1.1. Path Parameters (1 parameters):



Required What operation to use



345.1.2. Query Parameters (10 parameters):


inBody (common)

Sets the name of a parameter to be passed in the exchange In Body



serverUrl (common)

The server URL to connect.



bridgeErrorHandler (consumer)

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.



exceptionHandler (consumer)

To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.



exchangePattern (consumer)

Sets the exchange pattern when the consumer creates an exchange.



synchronous (advanced)

Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).



oauthToken (security)

The OAuth token.



password (security)

The password.



token (security)

The security token.



username (security)

The user name.



345.2. URI format


345.3. Producer Endpoints:

Producer endpoints can use endpoint names and associated options described next.

345.4. Consumer Endpoints:

Any of the producer endpoints can be used as a consumer endpoint. Consumer endpoints can use Scheduled Poll Consumer Options with a consumer. 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.

345.5. Message header

Any of the options can be provided in a message header for producer endpoints with CamelZendesk. prefix. In principal, parameter names are same as the arugument name of each API methods on the original org.zendesk.client.v2.Zendesk class. However some of them are renamed to the other name to avoid confliction in the camel API component framework. To see actual parameter name, please check org.apache.camel.component.zendesk.internal.ZendeskApiMethod.

345.6. Message body

All result message bodies utilize objects provided by the Zendesk Java Client. Producer endpoints can specify the option name for incoming message body in the inBody endpoint parameter.