-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP API #1
HTTP API #1
Conversation
Thanks Mike. Yes, it would be good to have at least one worked example in the doc. Something from the perspective of an application using the API, e.g. something that periodically queries available offers, takes an offer that meets a given criteria, etc, and what API calls it makes at each step in the process. The "simplest possible Bisq trading bot" would be a good start. Regarding naming, please rename this doc from Regarding style, please: Also, you mention that the project would be a "separate module", but it is probably better to call it out as being a "separate repository" (I think this is what you actually meant), as well as where that canonical repository would reside, e.g. https://github.com/bisq-network/http-api. |
Note that I've retitled the pull request from "first draft of api proposal" to "HTTP API", given that all pull requests to this repository are for proposals (so it need not be repeated), and because any given pull request may go through a number of drafts / revisions before being merged, so there's no need to mention "first draft" in the title. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes requested, see previous comments. Will probably be further review comments as well. Thanks again, @mrosseel for putting together the first proposal!
This proposal will be renamed to http-api, because it better describes the contents of the file, and because numbers will either not be used or at the very least are not known before a proposal is approved.
Perhaps you already noticed this, @mrosseel, but the email address you're using in your Git author metadata doesn't match the address you're using to sign your commits:
|
hi @cbeams yes this was a first test commit, will look into either adding the email to the gpg signature or changing the github email. |
This commit adds 2 examples of an API use case. These examples could be implemented by the API as currently proposed. Also added that the API will be hosted in a separate repo.
Note: I've just created the #http-api channel in Slack, where Mike and I are now discussing next steps with this proposal. |
I'm closing this proposal PR per my comments at bisq-network/bisq-docs#36 (comment). @mrosseel and I discussed this briefly earlier today as well. Thanks, Mike, for putting together an early cut at a proposal doc. Our use of this repository has evolved quite a bit and we'll see about keeping it issues-only from here out, as that seems to an effective approach. |
please comment on usage of asciidoc, style, content, ... .
It's fairly minimal, let me know what you feel is missing, maybe interaction examples for certain trades?