From: Jeff Garzik <jgarzik@bitpay.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] HTTP REST API for bitcoind
Date: Mon, 22 Jul 2013 15:42:45 -0400 [thread overview]
Message-ID: <CAJHLa0Ou1xF=LeLVu_wH1-XgJ1PavDV7_NHoDevo3R9+4z-ZfQ@mail.gmail.com> (raw)
URL: https://github.com/bitcoin/bitcoin/pull/2844
Adding an HTTP REST API for bitcoind has been occasionally tossed
about as a useful thing. Such an API would essentially provide a
decentralized block explorer capability, enabling easy external access
to transaction/address/block indices that we maintain.
The first two implemented API calls are simple, returning a block or
TX given a simple query string based on block hash, e.g.
GET /rest/tx/TX-HASH
or
GET /rest/block/BLOCK-HASH
This can be easily accessed via command line cURL/wget utilities.
Output formats -- binary, hex or json -- may be selected via a
"bitcoin-format" header.
The general goal of the HTTP REST interface is to access
unauthenticated, public blockchain information. There is no plan to
add wallet interfacing/manipulation via this API.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
next reply other threads:[~2013-07-22 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 19:42 Jeff Garzik [this message]
2013-07-22 22:06 ` [Bitcoin-development] HTTP REST API for bitcoind Michael Hendricks
2013-07-23 8:27 ` Andreas Schildbach
2013-07-23 8:45 ` Michael Gronager
2013-07-23 9:37 ` Pieter Wuille
2013-07-23 9:53 ` Michael Gronager
2013-07-23 10:17 ` Andreas Schildbach
2013-07-23 10:27 ` Pieter Wuille
2013-07-23 9:30 ` Andy Parkins
2013-07-23 9:42 ` Pieter Wuille
2013-07-23 9:52 ` Andy Parkins
2013-07-23 9:56 ` Pieter Wuille
2013-07-23 10:02 ` Andy Parkins
2013-07-23 10:06 ` Pieter Wuille
2013-07-23 9:47 ` Peter Todd
2013-07-23 10:00 ` Andy Parkins
2013-07-23 10:17 ` Peter Todd
2013-07-23 11:45 ` Andy Parkins
2013-07-23 10:19 ` Pieter Wuille
2013-07-23 10:29 ` Andreas Schildbach
2013-07-23 10:36 ` Pieter Wuille
2013-07-23 15:48 ` Michael Hendricks
2013-07-23 19:36 ` Mark Friedenbach
2013-08-10 20:30 ` Rune Kjær Svendsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJHLa0Ou1xF=LeLVu_wH1-XgJ1PavDV7_NHoDevo3R9+4z-ZfQ@mail.gmail.com' \
--to=jgarzik@bitpay.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox