Sample Request /v1/bpi/currentprice/CNY.json Sample JSON Response Historical BPI data We offer historical data from our Bitcoin Price Index through the following endpoint: /v1/bpi/historical/close.json By default, this will return the previous 31 days' worth of data.This endpoint accepts the following optional parameters: ?index=[USD/CNY]The index to return data for.?currency=The currency to return the data in, specified in ISO 4217 format.?start=&end= Allows data to be returned for a specific date range.Must be listed as a pair of start and end parameters, with dates supplied in the YYYY-MM-DD format, e.g.2013-09-01 for September 1st, 2013.?for=yesterdaySpecifying this will return a single value for the previous day.Overrides the start/end parameter.Sample Request: /v1/bpi/historical/close.json?start=2013-09-01&end=2013-09-05 Sample JSON Response: Feedback If you have any feedback or suggestions with regards to this API, please send them to .

Request Limits: To bypass the request limiter, please request an API key.REQUEST API KEY Receive Payments View Documentation Blockchain Wallet Service View Documentation Blockchain Data API View Documentation Simple Query API View Documentation Websockets View Documentation Exchange Rates View Documentation Charts and Statistics View Documentationethereum competitorsDocuments About Information for exchanges Backlink Banners Markets API Markets API API Overview Bitcoincharts provides a simple API to most of its data.25 btc physical bitcoinYou can use this API to include markets data in your websites, mobile apps or desktop applets.bitcoin trading dubai

Please remember to add a link to Bitcoincharts!Bitcoincharts' API is accessable through HTTP Parameters are passed using GET-requests returned data is JSON encoded Don't query more often than once every 15 minutes!You can use this to price goods and services in Bitcoins.This will yield much lower fluctuations than using a single market's latest price.block bitcoin explorerWeighted prices are calculated for the last 24 hours, 7 days and 30 days.zero fee bitcoin poolIf there are no trades during an interval (like no trade within 24 hours) no value will be returned.bitcoin mining vga cardPrepare your code to handle this cases!bitcoin api jsonThe returned JSON is dictionary with elements for each currency.bitcoin exchange ipo

Each currency has up to three key-value pairs: 24h, 7d and 30d.This will return an array with elements for each market.Returned fields per market are: symbolshort name for market currencybase currency of the market (USD, EUR, RUB, JPY, ...)bidhighest bid price asklowest ask price latest_tradeunixtime of latest trade.Following fields relate to the day of this field (UTC)!bitcoin dice bettingn_tradesnumber of trades highhighest trade during day lowlowest trade during day closelatest trade previous_closeatest trade of previous day volumetotal trade volume of day in BTC currency_volumetotal trade volume of day in currency Historic Trade Data Trade data is available as CSV, delayed by approx.It will return the 2000 most recent trades.You can use the start parameter to specify an earlier unix timestamp in order to retrieve older data.This service is strictly for personal use.

Do not assume this data to be 100% accurate or write trading bots that rely on it.blockchain-wallet bitcoin bitcoinrpc api commits branch releases contributors Latest commit 27ecfae Jun 6, 2017 Blockchain Wallet API V2 Programmatically interface with your Blockchain.info wallet.Contents Getting Started Upgrading API Documentation RPC API Installation Troubleshooting Usage Development Deployment Getting Started To use this API, you will need to run small local service which be responsible for managing your Blockchain.info wallet.Your application interacts with this service locally via HTTP API calls.Start by completing the following steps: Follow the installation instructions Start the server: $ blockchain-wallet-service start --port 3000 Reference the documentation and start interacting with your wallet programmatically!Note that blockchain-wallet-service is designed to be run locally on the same machine as your application and therefore will only accept connections from localhost.

If you modify this service to accept external connections, be sure to add the appropriate firewall rules to prevent unauthorized use.An API code is required for wallet creation and higher request limits.For basic usage, no API code is required.Request an API code here.Upgrading If you already have an application that uses Blockchain.info's Wallet API, you will need to complete the steps in the Getting Started section above and then, in your application code, replace calls to blockchain.info/merchant/... with localhost:/merchant/.... API Documentation View the original documentation.All endpoints present in the API documentation above are supported in Blockchain Wallet API V2.The differences between two are: The "consolidate addresses" endpoint has been omitted All endpoints can be called with GET or POST, and can only be accessed from localhost.Creating a new Blockchain Wallet Endpoint: /api/v2/create Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (required) priv - private key to import into wallet as first address (optional) label - label to give to the first address generated in the wallet (optional) email - email to associate with the newly created wallet (optional) Sample Response: Make Payment Endpoint: /merchant/:guid/payment Query Parameters: to - bitcoin address to send to (required) amount - amount in satoshi to send (required) password - main wallet password (required) second_password - second wallet password (required, only if second password is enabled) api_code - blockchain.info wallet api code (optional) from - bitcoin address or account index to send from (optional) fee - specify transaction fee in satoshi (optional, otherwise fee is computed) Sample Response: Send to Many Endpoint: /merchant/:guid/sendmany Query Parameters: recipients - a URI encoded JSON object, with bitcoin addresses as keys and the satoshi amounts as values (required, see example below) password - main wallet password (required) second_password - second wallet password (required, only if second password is enabled) api_code - blockchain.info wallet api code (optional) from - bitcoin address or account index to send from (optional) fee - specify transaction fee in satoshi (optional, otherwise fee is computed) URI Encoding a JSON object in JavaScript: Sample Response: Fetch Wallet Balance Endpoint: /merchant/:guid/balance Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (required) Sample Response: Enable HD Functionality Endpoint: /merchant/:guid/enableHD Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) This will upgrade a wallet to an HD (Hierarchical Deterministic) Wallet, which allows the use of accounts.

See BIP32 for more information on HD wallets and accounts.List Active HD Accounts Endpoint: /merchant/:guid/accounts Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) List HD xPubs Endpoint: /merchant/:guid/accounts/xpubs Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Create New HD Account Endpoint: /merchant/:guid/accounts/create Query Parameters: label - label to assign to the newly created account (optional) password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Get Single HD Account Endpoint: /merchant/:guid/accounts/:xpub_or_index Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Get HD Account Receiving Address Endpoint: /merchant/:guid/accounts/:xpub_or_index/receiveAddress Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Check HD Account Balance Endpoint: /merchant/:guid/accounts/:xpub_or_index/balance Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Archive HD Account Endpoint: /merchant/:guid/accounts/:xpub_or_index/archive Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Unarchive HD Account Endpoint: /merchant/:guid/accounts/:xpub_or_index/unarchive Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) List Addresses (deprecated, use the HD API instead) Endpoint: /merchant/:guid/list Query Parameters: password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Sample Response: Fetch Address Balance (deprecated, use the HD API instead) Endpoint: /merchant/:guid/address_balance Query Parameters: address - address to fetch balance for (required) password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Note: unlike the hosted API, there is no option of a confirmations parameter for specifying minimum confirmations.

Sample Response: Generate Address (deprecated, use the HD API instead) Endpoint: /merchant/:guid/new_address Query Parameters: password - main wallet password (required) label - label to give to the address (optional) api_code - blockchain.info wallet api code (optional) Sample Response: Archive Address (deprecated, use the HD API instead) Endpoint: /merchant/:guid/archive_address Query Parameters: address - address to archive (required) password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Sample Response: Unarchive Address (deprecated, use the HD API instead) Endpoint: /merchant/:guid/unarchive_address Query Parameters: address - address to unarchive (required) password - main wallet password (required) api_code - blockchain.info wallet api code (optional) Sample Response: RPC Bitcoind compatible RPC API.Full documentation available here.

Starting the RPC server: $ blockchain-wallet-service start-rpc [options] View additional options and instructions under Usage.Differences from server API: Option -rpcssl is not supported Method listsinceblock is not supported Param minConfimations is not supported for methods listreceivedbyaccount and listreceivedbyaddress Param minimumConfirmations is not supported for method getbalance Param confirmations is not supported for method listaccounts Responses representing transactions have a different format Installation nodejs and npm are required to install and use this API service.Installation: For the best stability and performance, make sure you are always using the latest version.To check your version: To update to the latest version: Requires: node >= 6.0.0 npm >= 3.0.0 If you have issues with the installation process, see the troubleshooting section below.Troubleshooting Installation errors: If you are getting EACCESS or permissions-related errors, it might be necessary to run the install as root, using the sudo command.

If you are getting errors concerning node-gyp or python, install with npm install --no-optional Startup errors: If startup fails with /usr/bin/env: node: No such file or directory, it's possible node is not installed, or was installed with a different name (Ubuntu, for example, installs node as nodejs).If node was installed with a different name, create a symlink to your node binary: sudo ln -s /usr/bin/nodejs /usr/bin/node, or install node through Node Version Manager.Runtime errors: If you are seeing a TypeError claiming that an object has no method 'compare', it is because you are on a version of Node older than 0.12, before the compare method was added to Buffers.Try upgrading to at least Node version 0.12.If you are getting wallet decryption errors despite having correct credentials, then it's possible that you do not have Java installed, which is required by a dependency of the my-wallet-v3 module.Not having Java installed during the npm install process can result in the inability to decrypt wallets.

Download the JDK from here for Mac or by running apt-get install default-jdk on debian-based linux systems.Timeout Errors: If you are getting a timeout response, additional authorization from your blockchain wallet may be required.This can occur when using an unrecognized browser or IP address.An email authorizing the API access attempt will be sent to the registered user that will require action in order to authorize future requests.If this section did not help, please open a github issue or visit our support center.Usage After installing the service, the command blockchain-wallet-service will be available for use.Options -h, --help - output usage information -V, --version - output the version number -c, --cwd - use the current directory as the wallet service module (development only) Commands start Usage: blockchain-wallet-service start [options] This command will start the service, making Blockchain Wallet API V2 available on a specified port.

Command options: -h, --help - output usage information -p, --port - port number to run the server on (defaults to 3000) -b, --bind - bind to a specific ip (defaults to 127.0.0.1, note that binding to an ip other than this can lead to security vulnerabilities) --ssl-key - the path to your ssl key (optional) --ssl-cert - the path to your ssl certificate (optional) To open the service to all incoming connections, bind to 0.0.0.0. start-rpc Usage: blockchain-wallet-service start-rpc [options] This command will start the JSON RPC server.Options: -k, --key - api code to use for server requests (required option) -p, --rpcport - rpc server port (default: 8000) -b, --bind - bind to a specific ip (defaults to 127.0.0.1, note that binding to an ip other than this can lead to security vulnerabilities) Get an API code here.Examples To start the Wallet API service on port 3000: Development Clone this repo Run yarn --ignore-engines Run yarn start Dev server is now running on port 3000 If you are developing blockchain-wallet-client alongside this module, it is useful to create a symlink to my-wallet-v3: Testing Configuration Optional parameters can be configured in a .env file: PORT - port number for running dev server (default: 3000) BIND - ip address to bind the service to (default: 127.0.0.1) Deployment If you want to use blockchain-wallet-service in your UNIX production server, you just have to run: