Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 341. 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: 

<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>
Copy to Clipboard Toggle word wrap

341.1. URI format
Copier lien

xchange://exchange?options
Copy to Clipboard Toggle word wrap

341.2. Options
Copier lien

The XChange component has no options.

The XChange endpoint is configured using URI syntax: 

xchange:name
Copy to Clipboard Toggle word wrap

with the following path and query parameters:

341.2.1. Path Parameters (1 parameters):
Copier lien

Expand
NameDescriptionDefaultType

name

Required The exchange to connect to

 

String

341.2.2. Query Parameters (5 parameters):
Copier lien

Expand
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

341.3. Authentication
Copier lien

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************
Copy to Clipboard Toggle word wrap

341.4. Message Headers
Copier lien

<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")
Copy to Clipboard Toggle word wrap
</TODO>
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat