Skip to content
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

[api] Get broadcast many-inputs #20

Open
olemis opened this issue Feb 24, 2019 · 0 comments
Open

[api] Get broadcast many-inputs #20

olemis opened this issue Feb 24, 2019 · 0 comments
Assignees

Comments

@olemis
Copy link
Contributor

olemis commented Feb 24, 2019

[GET] /api/transactions/broadcast/many-inputs/{operationId}

Should return broadcasted transaction by the opreationId. All transactions with many inputs, that were broadcasted by the should be available here.

Response:

{
// Operation ID.
“operationId”: “guid”,
// State of the transaction
// enum values:
//
// -  inProgress : transaction is being in-progress
// -  completed : transaction is completed for sure. When
// transaction is switched to the completed state,
// amount of this transaction should be already subtracted
// from the balance returned by the  [GET] /api/balances ,
// for outgoing transactions
// -  failed : transaction is failed, if applicable for the particular blockchain
//
“state”: “enum”,

 // Transaction moment as ISO 8601 in UTC
“timestamp”: “datetime”,
 // Sources.
// Should be non null if the  state is  Completed.
“inputs”: [
{
        “amount”: “string”
    }
// From address
“fromAddress”: “string”,
// Actual amount, that is transferred from the
//  fromAddress . Integer as string, aligned
// to the asset accuracy. Actual value can be
// calculated as
// x = amount / (10 ^ asset.Accuracy)
],
// Destination address
    “toAddress”: “string”,
//  Fee should always be zero if the  state is  Completed
“fee”: “string”,
   // Transaction hash as base64 string.
   // Can be empty
// Should be non empty if the  state is  Completed
    “hash”: “string”,
// Error description
// Can be empty
// Should be non empty if the  state is  Error
“error”: “string”,
// Error code.
// Can be empty.
// Should be non empty if the state is Failed.
// enum values:
// -  unknown : any error that does not fit another codes.
// -  amountIsTooSmall : amount is too small to execute
// transaction
// -  notEnoughBalance : transaction can’t be executed due
// to balance insufficiency on the source address.
“errorCode”: “enum”,
// Incremental ID of the moment, when the transaction
// state changing is detected. It should be the same
// sequence as for block in the  [GET] /api/balances
// response. In other words block number/height.
    “block”: integer64
}

Errors:

* `204 No content`  - specified transaction not found
cbermudez97 pushed a commit to uhsimelo/skyxcommons that referenced this issue Feb 26, 2019
…dpoint

/api/transactions/broadcast/many-inputs/{operationId}
cbermudez97 pushed a commit to uhsimelo/skyxcommons that referenced this issue Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants