Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Chapter 357. 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

357.1. URI format
Copiar enlace

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

357.2. Options
Copiar enlace

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:

357.2.1. Path Parameters (1 parameters):
Copiar enlace

Expand
NameDescriptionDefaultType

name

Required The exchange to connect to

 

String

357.2.2. Query Parameters (5 parameters):
Copiar enlace

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

357.3. Authentication
Copiar enlace

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

357.4. Message Headers
Copiar enlace

<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>
Volver arriba
Red Hat logoGithubredditYoutubeTwitter

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2025 Red Hat