create_transactions
Create new transaction/s, which will be submitted to the Mempool nodes for inclusion into a new block. This call assumes a full transaction as part of the request body, which might make raw calls difficult to manage. For convenience, it may be best to use an AIBlock library or SDK that abstracts this call for you.
Header Parameters
Possible values: Value must match regular expression ^[a-z0-9]{32}$
An idempotent key for retrieving cached responses from the node
Request Body required
Create a new transaction
- Array [
- ]
- Array [
- ]
inputs txinput[]
The inputs to the transaction
previous_out object
Previous output tx hash
Transaction hash
The index of the output in the input transaction
script_signature object
Pay2PkH object
Data to sign for verification. This is a SHA3 hash of the all the transaction outputs and this input's previous output, for example "{output1}{output2}{previousOut}"
Signature of the signable data
Public key used to sign the signable data
outputs txinput[]
The outputs to the transaction
value object
Token amount
The transaction's schema version
druid_info object
expectations object
- 200
- 400
Successful operation
Schema
The ID of the call, which corresponds to the x-cache-id used in the header
The status of the call, which will be one of either "Success", "Error", or "Pending"
The reason for the status of the call. Most useful to debug errors
The endpoint route that was called
content object
This section is unfinished, refer to postman collection for more details
{
"id": "a1d46199e5c89b00509e118f5af83172",
"status": "Success",
"reason": "Transaction/s successfully created",
"route": "create_transactions",
"content": {
"transaction": "This section is unfinished, refer to postman collection for more details"
}
}
Invalid input
Schema
{
"id": null,
"status": "Error",
"reason": "Bad Request",
"route": null,
"content": null
}