XChange Component

Available as of Camel version 2.21

The xchange: component uses the XChange Java library to provide access to 60+ Bitcoin and Altcoin exchanges. It comes with a consistent interface for trading and accessing market data.

Camel can get crypto currency market data, query historical data, place market orders and much more.

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

    <!-- use the same version as your Camel core version -->

URI format



The XChange component has no options.

The XChange endpoint is configured using URI syntax:


with the following path and query parameters:

Path Parameters (1 parameters):

Name Description Default Type


Required The exchange to connect to


Query Parameters (5 parameters):

Name Description Default Type

currency (producer)

The currency


currencyPair (producer)

The currency pair


method (producer)

Required The method to execute


service (producer)

Required The service to call


synchronous (advanced)

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



Spring Boot Auto-Configuration

When using Spring Boot make sure to use the following Maven dependency to have support for auto configuration:

  <!-- use the same version as your Camel core version -->

The component supports 2 options, which are listed below.

Name Description Default Type


Whether to enable auto configuration of the xchange component. This is enabled by default.



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




This component communicates with supported crypto currency exchanges via REST API. Some API requests use simple unauthenticated GET request. For most of the interesting stuff however, you’d need an account with the exchange and have API access keys enabled.

These API access keys need to be guarded tightly, especially so when they also allow for the withdraw functionality. In which case, anyone who can get hold of your API keys can easily transfer funds from your account to some other address i.e. steal your money.

Your API access keys can be strored in an exchange specific properties file in your SSH directory. For Binance for example this would be: ~/.ssh/binance-secret.keys

# This file MUST NEVER be commited to source control.
# It is therefore added to .gitignore.
apiKey = GuRW0*********
secretKey = nKLki************

Message Headers


In this sample we find the current Bitcoin market price in USDT: