1. 20 Nov, 2017 1 commit
    • Andras Fuchs's avatar
      Fixed a the name query parameter for API call wallet/general-info (#359) · b899324f
      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)
      b899324f
  2. 21 Jun, 2017 3 commits
  3. 18 May, 2017 1 commit
  4. 17 May, 2017 1 commit
  5. 15 May, 2017 1 commit
  6. 14 May, 2017 1 commit
  7. 12 May, 2017 1 commit
  8. 08 May, 2017 1 commit
  9. 07 May, 2017 1 commit
  10. 02 May, 2017 1 commit
  11. 25 Apr, 2017 1 commit
  12. 14 Apr, 2017 2 commits
  13. 13 Apr, 2017 1 commit
  14. 10 Apr, 2017 2 commits
    • Jeremy Bokobza's avatar
      Added API contribution guidelines · 59e00306
      Jeremy Bokobza authored
      59e00306
    • Jeremy Bokobza's avatar
      Update ApiSpecification.md · f3b4f480
      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?
      f3b4f480
  15. 29 Mar, 2017 7 commits
  16. 28 Mar, 2017 4 commits