List schedules entities
Changed onLists schedules on the network that govern the execution logic of scheduled transactions. This includes executed and non executed schedules.
Request
- Base URL(relative, and the document was published on a file host, not at the API’s origin)
- URL/api/v1/schedules
- Authnone declared
Query parameters
The ID of the account to return information for
The maximum number of items to return
The order in which items are listed
The ID of the schedule to return information for
Response
OK
Example response
{
"schedules": [
{
"admin_key": {
"_type": "ProtobufEncoded",
"key": "15706b229b3ba33d4a5a41ff54ce1cfe0a3d308672a33ff382f81583e02bd743"
},
"consensus_timestamp": "1586567700.453054000",
"creator_account_id": "0.0.2",
"executed_timestamp": "1586567700.453054000",
"expiration_time": "1586567700.453054000",
"memo": "created on 02/10/2021",
"payer_account_id": "0.0.2",
"schedule_id": "0.0.2",
"signatures": [
{
"consensus_timestamp": "1586567700.453054000",
"public_key_prefix": "AAEBAwuqAwzB",
"signature": "3q2+7wABAQMLqgMMwQ==",
"type": "ED25519"
}
],
"transaction_body": "Kd6tvu8="
}
]
}Changes
- breaking
the response property
///became nullable for the status - breaking
the response property
///became nullable for the status - breaking
the response property
/became nullable for the status - breaking
the response property
//became nullable for the status - breaking
the response property
//became nullable for the status - breaking
the response property
//became nullable for the status - breaking
the response property
//became nullable for the status - breaking
the response property
//became nullable for the status - breaking
the response property
//became nullable for the status
- breaking