Search

Chapter 371. XChange Component

download PDF

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:

<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-xchange</artifactId>
    <version>x.x.x</version>
    <!-- use the same version as your Camel core version -->
</dependency>

371.1. URI format

xchange://exchange?options

371.2. Options

The XChange component has no options.

The XChange endpoint is configured using URI syntax:

xchange:name

with the following path and query parameters:

371.2.1. Path Parameters (1 parameters):

NameDescriptionDefaultType

name

Required The exchange to connect to

 

String

371.2.2. Query Parameters (5 parameters):

NameDescriptionDefaultType

currency (producer)

The currency

 

Currency

currencyPair (producer)

The currency pair

 

CurrencyPair

method (producer)

Required The method to execute

 

XChangeMethod

service (producer)

Required The service to call

 

XChangeService

synchronous (advanced)

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

false

boolean

371.3. Spring Boot Auto-Configuration

The component supports 2 options, which are listed below.

NameDescriptionDefaultType

camel.component.xchange.enabled

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

 

Boolean

camel.component.xchange.resolve-property-placeholders

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

true

Boolean

371.4. Authentication

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************

371.5. Message Headers

<TODO><title>Samples</title>

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

from("direct:ticker").to("xchange:binance?service=market&method=ticker&currencyPair=BTC/USDT")
</TODO>
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.