Skip to content

Commit

Permalink
Updates example doc for candles
Browse files Browse the repository at this point in the history
  • Loading branch information
ksysoev committed Oct 1, 2023
1 parent 2d1c5cf commit 31e2c8c
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions examples/candles/README.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
# Deriv Ticks History
# Deriv Candles

This Go script demonstrates how to use the Deriv API to retrieve the ticks history for a specified symbol. The script uses the `deriv-api` and `deriv-api/schema packages` to interact with the Deriv API and send requests to subscribe to the ticks history stream.
This Go script demonstrates how to use the Deriv API to retrieve the ticks history for a specified symbol in candles representation. The script uses the `deriv-api` and `deriv-api/schema packages` to interact with the Deriv API and send requests to subscribe to the tick history stream with canles style.

The script first creates a new `DerivAPI` instance and authorizes the connection using the provided API token. It then creates a new ticks history subscription request with a specified symbol, start time, end time, style, and count.

The script then sends the subscription request to the Deriv API and waits for a response. Once a response is received, the script logs the historical prices for the specified symbol.

The script then subscribes to the ticks history stream and waits for new ticks to be received. Once a new tick is received, the script logs the symbol and quote for the tick.
The script then subscribes to the ticks history stream and waits for new ticks to be received. Once a new tick is received, the script logs OHLC values.

Note that this script is provided as an example and may require modifications to work with your specific environment and use case. It is important to thoroughly test any code that interacts with the Deriv API before using it with real funds.

0 comments on commit 31e2c8c

Please sign in to comment.