List scheduled transactions for an account
Returns a paginated list of scheduled transactions associated with the given account address, ordered descending by scheduled time (newest first). Results can be filtered by status, priority, time range, and transaction handler properties.
Path parameters
The 8-byte address of an account.
The account address (hex-encoded without 0x prefix).
Query parameters
Opaque pagination cursor from a previous response's next_cursor field.
Opaque pagination cursor from a previous response's next_cursor field.
The maximum number of results to return.
A comma-separated list of scheduled transaction statuses to filter by.
The execution priority of a scheduled transaction.
Filter by scheduled transaction priority.
Filter to include only scheduled transactions with a scheduled time at or after this value (inclusive, RFC 3339).
Filter to include only scheduled transactions with a scheduled time at or before this value (inclusive, RFC 3339).
The 8-byte address of an account.
Filter by the address of the account that owns the transaction handler.
Filter by the Cadence type identifier of the transaction handler (e.g. A.1654653399040a61.MyScheduler.Handler).
Filter by the UUID of the transaction handler resource.
A comma-separated list indicating which properties of the content to expand.
A comma-separated list indicating which properties of the content to return.
Response
A page of scheduled transactions.
Changes
Changed in 6 of the 24 revisions of this API.418
- ○
added the optional property
//to the response with the statusresponse-optional-property-added
- ○
added the required property
//to the response with the statusresponse-required-property-added
- ○
- ▲
the response property
///became optional for the statusresponse-property-became-optional
- ○
added the optional property
////to the response with the statusresponse-optional-property-added
- ▲
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
//to the response with the statusresponse-optional-property-added
- ○
- ▲
removed the required property
///from the response with the statusresponse-required-property-removed
- ▲
removed the required property
///from the response with the statusresponse-required-property-removed
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the required property
///to the response with the statusresponse-required-property-added
- ○
added the required property
///to the response with the statusresponse-required-property-added
- ○
added the required property
///to the response with the statusresponse-required-property-added
- ○
added the required property
///to the response with the statusresponse-required-property-added
- ○
added the required property
///to the response with the statusresponse-required-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
endpoint added
endpoint-added
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 13 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲