Skip to main content
ScheduleInfoQuery is a consensus node query that returns information about the current state of a schedule transaction on a Hedera network. Schedule Info Response
FieldDescription
Schedule IDThe ID of the schedule transaction.
Creator Account IDThe Hedera account that created the schedule transaction in x.y.z format.
Payer Account IDThe Hedera account paying for the execution of the scheduled transaction in x.y.z format.
Scheduled Transaction BodyThe transaction body of the transaction that is being scheduled by the schedule transaction.
SignatoriesThe public keys that have signed the transaction.
Admin KeyThe key that can delete the schedule transaction, if set
Expiration TimeThe date and time the schedule transaction will expire
Executed TimeThe time the schedule transaction was executed. If the schedule transaction has not executed this field will be left null.
Deletion TimeThe consensus time the schedule transaction was deleted. If the schedule transaction was not deleted, this field will be left null.
MemoPublicly visible information about the Schedule entity, up to 100 bytes. No guarantee of uniqueness.

​
Recommend Using Mirror Node REST API

For obtaining schedule information and historical data, consider using the Mirror Node REST API endpoint Get Schedule by ID which offers several advantages:
  • Cost-effective and scalable: Mirror node providers offer paid plans with a large number of queries included. The Hedera-hosted mirror node offers free queries with specific throttles for testing. While some SDK queries are currently free, these are subject to change in the future.
  • Performance: Mirror nodes don’t burden consensus nodes, allowing them to focus on processing transactions and providing efficient access to historical data without impacting network performance.
  • Historical data: Mirror nodes store complete transaction history, records, and events - ideal for analytics, auditing, and monitoring past activity.
Query Signing Requirements
  • The transaction fee payer account key is required to sign

​
Methods

MethodTypeRequirement
setScheduleId(<scheduleId>)ScheduleIdRequired
<ScheduleInfo>.scheduleIdScheduleIdOptional
<ScheduleInfo>.scheduledTransactionIdTransactionIdOptional
<ScheduleInfo>.creatorAccountIdAccountIdOptional
<ScheduleInfo>.payerAccountIdAccountIdOptional
<ScheduleInfo>.adminKeyKeyOptional
<ScheduleInfo>.signatoriesKeyOptional
<ScheduleInfo>.deletedAtInstantOptional
<ScheduleInfo>.expirationAtInstantOptional
<ScheduleInfo>.memoStringOptional
<ScheduleInfo>.waitForExpirybooleanOptional
//Create the query
ScheduleInfoQuery query = new ScheduleInfoQuery()
     .setScheduleId(scheduleId);

//Sign with the client operator private key and submit the query request to a node in a Hedera network
ScheduleInfo info = query.execute(client);