initial draft of ledger API #90
Conversation
|
|
||
| ##### Request | ||
| ```http | ||
| GET /transfers/<ID> HTTP/1.1 |
There was a problem hiding this comment.
The format for <ID> should be specified. Recommend a lowercase UUID.
|
Each RFC number should be only one document, and we should never redefine/reassign. (Better to have a hole/deprecated RFC than a number that meant different things at different times.) IL-RFC 0004 is the JavaScript ledger plugin interface. So we should assign a new RFC number for this imo. |
remove connectors endpoint ID types authorization placeholder
added image
| ## Requirements | ||
|
|
||
| In order for ledgers to connect seamlessly with any of the ILP plugins `ilp-plugin-<ledgerID>`, the ledger needs to provide: | ||
| - a RESTful HTTP API with endpoints to `transfer` (or `transaction`, `asset`) objects |
There was a problem hiding this comment.
a RESTful HTTP API with endpoints to initiate transfers and submit fulfillments.
assigned it to RFC-0012 |
| ilpFulfillment | ||
| ``` | ||
|
|
||
| ## PUSH notifications (websockets) |
There was a problem hiding this comment.
We will need to define what these messages would look like? Just JSON objects?
|
Shall we close this in favor of #125? |
I started and initial draft for guidelineing the API as discussed in last call.
@adrianhopebailie: Is this the kind of format you were looking for?
cc @justmoon @emschwartz