Skip to content

Latest commit

 

History

History
92 lines (65 loc) · 2.89 KB

xchange-component.adoc

File metadata and controls

92 lines (65 loc) · 2.89 KB

XChange

Since Camel 2.21

Only producer is supported

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>

Usage

Authentication

This component communicates with supported cryptocurrency 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 stored 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************

Examples

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

from("direct:ticker").to("xchange:binance?service=marketdata&method=ticker&currencyPair=BTC/USDT")

spring-boot:partial$starter.adoc