Zebpay Build is a platform on the top of which users can create their own applications, similar to Zebpay or any other cryptocurrency trading applications. Developers can even create trading bots using Zebpay Build. Users can also build other types of applications(console/web/API) using our platform and can: Buy and sell digital currencies. Import transactions details on open and closed orders, past trade history. Integrate live price charts of bitcoin, ether and other altcoins. Fetch detailed information like volume, last trade, spread for each coin. Create crypto portfolio of digital assets. Build a customized watchlist. Set alerts basis change in percentage in custom interval. Sync wallet balance and create a wallet overview.

All Market and Trading related data/methods is available at this time through REST-ful API.

General Trading Overview and Zebpay Build details.

Overview and general information about the Zebpay Build API's.

All our API requests and responses are application/json content type and follow typical HTTP response status codes for success and failure. All API requests are called by the standard HTTPS. All POST calls need to specify the parameters of the format to x-www-form-urlencoded.

A successful response is indicated by HTTP status code 200 and may contain an optional body. If the response has a body it will be documented under each API.

Unless otherwise stated, errors to bad requests will respond with HTTP 4xx or status codes. The body will also contain a message parameter indicating the cause. Your language's http library should be configured to provide message bodies for non-2xx requests so that you can read the message field from the body.

Following table gives more details about error code and description.

When a rate limit is exceeded, a status of 429 Too Many Requests will be returned.

All our Datetime properties has value as "Unique Timestamp in milliseconds" (Unix time, also known as POSIX time[citation needed] or UNIX Epoch time[1]) is a system for describing a point in time, defined as an approximation of the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970.

Consumer can convert the same to any timezone. Please note that, in case your library supports only seconds, divide the value by 1000 before converting to date object.

We support pagination in the API's which return a list. User has to pass the value parameterized like "?limit=10&page=1". By default system will limit the record to 20, and fetch the latest data.

For example

Tradepair History (/market/{tradepair}/trades).

Get Order (/orders).

A public sandbox is available for testing API connectivity and web trading. The sandbox environment provides all of the functionality of the production exchange and allows you to play around with API.

Login sessions and API keys are separate from production. Use the sandbox web interface to create keys in the sandbox environment.

Zebpay Build production environment is available for API connectivity and web trading.

Login sessions and API keys are separate from production.

Client libraries can help you integrate with our API quickly.

Github Repository

We supports almost all major/leading Cryptocurrencies, and are adding a new virtual currency every week. Current supported coins are:

You'll need to register your app before getting started.Upon registration you will get following piece of information which need to be remember.

which will be used in the OAuth flow

User must restrict the scope of Application.This permission user can select at time of application registration.

All Request must contain the following headers.

The API signature header is generated by creating a sha256 HMAC using the base64-decoded secret key on the prehash string

                        
                        POST + Seprator(\n) + timestamp +seprator+targeturl+seprator+bodydata+seprator+client_Id:client_Id
                       
                      

The timestamp value is the same as the timestamp in header.

For all authenticated API's we also return a signature back ti the caller in response header with key "x-hmac". The value is hashed using the same API secret key, and response body as payload message. Calling application can use this hashed value to verify if the response is returned from the trusted Zebpay server.

Zebpay Build provide a page where developer can register the application as "web". At time of application registration developer need to keep following things in mind:

When creating .net MVC Core application, app.UseAuthentication() should be used for Authentication.

Code Sample for .net MVC Core application (developer should use Authorize attribute on Controller)

Zebpay provide a page where developer can register the application as "Console".

Zebpay provides a series of API's for login purpose.

The API's need to be called in a sequence : /login, /verifyotp, /verifypin, /logout. See User API for detail request/response.

After successfull authentication user will get access_token and user can use this access_token to access API.

Get the list of tickers. Get 24 hr stats for the product. volume is in base currency units. open, high, low are in quote currency units, for all trade pairs.

Get the ticker information for the current Trade Pair, with daily volume and current Price.

Get a list of open orders for a trade pair.

Get the trade History information for the current Trade Pair.

This endpoint can be used to read order data as well as create a new order. You can also cancel your previously placed order.

User can place limit order and it can be done only when there is sufficient amount of Quote currencies available in the account. On placing order, the amount of quote currency for the given pair will be on hold for the duration of the order.

List your current orders. You can view open as well as settled orders. We need to pass ORDER STATUS "Pending" to get all un-settled orders, "all" to get all orders.

Get a single order's detail/fills by order id.

Cancel a previously placed order.

"Pair-Trading" in cryptocurrency in simple language means "exchanging one virtual currency for another". Every cryptocurrency in today's world is associated a value, which is a multiple of value of domestic fiat currency. The same concept is applied while "Crypto-Crypto trading" where the base value of the relative alternative coins is decided to that of the Bitcoin.

Left Hand Side will be the currency we want to trade:

Description

pin is the encrypted value of user's pin encrypted using API secret (provided during creation of app on zebpay build). Algorithm used is AES encryption. Below is an example of how this can be done using Javascript.

import * as CryptoJS from 'crypto-js';

  aesEncrypt(text, key){
    let k = key.replace(/-/g, '').substring(0,16);
    k = CryptoJS.enc.Utf8.parse(k);
    const iv = CryptoJS.enc.Utf8.parse('0000000000000000');
    const encrypted = CryptoJS.AES.encrypt(text.trim(), k, {
      keySize: 16,
      iv: iv,
      mode: CryptoJS.mode.ECB,
      padding: CryptoJS.pad.Pkcs7
    });
    console.log(encrypted.toString());
    return encrypted.toString();
  }

The websocket feed provides real-time market data updates for following events:

• 1. Tickers
• 2. Orderbook
• 3. Trades or History
• 4. Instant Buy/Sell rates

To connect to Zebpay websocket feed you have include socket.io library depending on your client. For example to use it just as a cross-browser WebSocket include js lib (you can download or refer from cdn )- and run below code in javascript:

Once the connection is established between the client and server, you can subscribe to different events by simply emitting a 'subscribe' event with the respective event name. The Format for event names are as follows:

Once you have the event name(s), you need to emit the subscribe event with the respective event name and server will start sending real time data.

                        // To subscribe realtime ticker event for BTC-EUR

                    ws.emit('subscribe', 'ticker/BTC-INR');


                        // To subscribe realtime orderbook event for BTC-INR

                    ws.emit('subscribe', 'book/BTC-INR');

                        
                        // To subscribe realtime history event for BTC-INR
 
                    ws.emit('subscribe', 'history/BTC-INR');


                        // To subscribe realtime Instant Buy/Sell rate events for BTC-AUD

                    ws.emit('subscribe', 'traderates/BTC-AUD');

                    

To capture the data for any event, you have to simply add a socket listener for that event.

                    
                            ws.on('ticker/BTC-INR', (data) => {
                            console.log('in event ticker/BTC-INR', data);
                            });
                          
                        

Note - To capture data from any event make sure you have emitted a subscribe event for that event name.

For debugging purpose and catching socket server errors, you can directly listen for the ‘error’ event. No need to subscribe.

                    
                            ws.on(‘error’, (message) => {
                            console.error(‘Error from socket server’, message);
                            });