The Transaction Scheduler acts as an entrypoint for transactions, and initiates the transaction workflow to other Orchestrate workers. It allows users to send transactions through an HTTP REST API, and tracks the transaction data and status.
The Transaction Scheduler provides a
\transactions endpoint that allows users to send different transaction types; for example, contract transactions, raw transactions, contract deployments, or private transactions.
Additional low-level APIs provides finer-grained control over the transaction flow by exposing the following endpoints:
\jobs: Represents the transaction execution workflow, and stores metadata tied to the transaction such as execution logs or transaction type.
\schedules: Represents multiple transaction jobs that be run in parallel or sequentially.