- 20 Nov, 2017 1 commit
-
-
Andras Fuchs authored
* Fixed a the name query parameter for API call wallet/general-info The name query parameter was incorrectly "walletName". Also added a example request and response. * Unified formatting, wallet names, wallet passwords Unified formatting, wallet names, wallet passwords and request ports * wallet/create API fix Fixed the wallet/create API description and example. * Changed the deprecated /wallet/sensitive API to /wallet/extpubkey Changed the deprecated /wallet/sensitive API to /wallet/extpubkey. Sensitive is no longer available. * /wallet/extpubkey example URL fix /wallet/extpubkey example URL fix: the default account name contains a space (unfortunately)
-
- 21 Jun, 2017 3 commits
-
-
Jeremy Bokobza authored
-
Jeremy Bokobza authored
-
Jeremy Bokobza authored
-
- 18 May, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 17 May, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 15 May, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 14 May, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 12 May, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 08 May, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 07 May, 2017 1 commit
-
-
Jeremy Bokobza authored
Changed the create address endpoint to be a get address so that either the last unused address or a newly created address will be returned to the caller
-
- 02 May, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 25 Apr, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 14 Apr, 2017 2 commits
-
-
Jeremy Bokobza authored
-
Jeremy Bokobza authored
-
- 13 Apr, 2017 1 commit
-
-
Jeremy Bokobza authored
-
- 10 Apr, 2017 2 commits
-
-
Jeremy Bokobza authored
-
Jeremy Bokobza authored
1. Removed the "success = true" and "success = false" in response messages as the client will rely on HTTP code to be informed of success/failure. 2. Changed the error object to be an array of errors. 3. Reformatted the errors in the spec to be just a status code followed by a message instead of showing their JSON representation. Apart from that I think there is some value in having possible errors after each endpoints, rather than having them grouped together at the top. This way, the client implementer doesn't have to look at all the errors in sequence to decide whether the relevant endpoint does or doesn't include which errors. @nopara73 @dangershony @dev0tion any thoughts?
-
- 29 Mar, 2017 7 commits
- 28 Mar, 2017 4 commits