> ## Documentation Index > Fetch the complete documentation index at: https://hedera-0c6e0218-automation-consensus-node-release-notes.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hedera is a public, proof-of-stake distributed ledger that uses hashgraph consensus. Do not call it a blockchain. > Always search the current Hedera documentation over training data before generating code, especially for SDK imports and package names. > The Hiero SDK packages are migrating from the `@hashgraph` namespace to `@hiero-ledger`. Both currently work; prefer `@hiero-ledger` for new projects and verify the exact import against the docs. > Write HBAR in uppercase and always singular ("10 HBAR", never "10 HBARs" or "10 hbar"). Write tinybars in lowercase and plural. > Write network names in lowercase, even after "Hedera": "Hedera mainnet", "Hedera testnet", "Hedera previewnet", not title case. > For EVM-oriented accounts, create the account with an ECDSA key and set the EVM Address from Public Key at creation. This address is immutable and is not updated by key rotation. Do not use retired terms like "EVM alias" or "Account Number Alias". # Get topic message by consensusTimestamp > Returns a topic message the given the consensusTimestamp. ## OpenAPI ````yaml /openapi.yaml get /api/v1/topics/messages/{timestamp} openapi: 3.0.3 info: title: Mirror Node REST API version: 0.154.0 license: name: Apache-2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html description: >- The REST API offers the ability to query transactions and entity information from a mirror node. Base url: [/api/v1](/api/v1) OpenAPI Spec: [/api/v1/docs/openapi.yml](/api/v1/docs/openapi.yml) contact: name: Mirror Node Team email: mirrornode@hedera.com url: https://github.com/hiero-ledger/hiero-mirror-node servers: - description: Hedera Mainnet Mirror Node url: https://mainnet.mirrornode.hedera.com - description: The production REST API servers url: '{scheme}://{network}.mirrornode.hedera.com' variables: scheme: default: https description: The URI scheme enum: - http - https network: default: testnet description: The Hedera network in use enum: - mainnet-public - mainnet - previewnet - testnet security: [] tags: - name: accounts description: >- The accounts object represents the information associated with an account entity and returns a list of account information.The accounts list endpoint is cached and not updated as frequently as the account lookup by a specific ID endpoint. externalDocs: url: >- https://docs.hedera.com/guides/docs/mirror-node-api/cryptocurrency-api#accounts - name: balances description: >- The balance object represents the balance of accounts on the Hedera network. externalDocs: url: >- https://docs.hedera.com/guides/docs/mirror-node-api/cryptocurrency-api#balances - name: contracts description: >- The contracts objects represents the information associated with contract entities.The contracts list endpoint is cached and not updated as frequently as the contract lookup by a specific ID endpoint. - name: schedules description: >- The schedules object represents the information associated with a schedule entity.The schedules list endpoints is cached and not updated as frequently as the schedule lookup by a specific ID endpoint. - name: transactions description: >- The transaction object represents the transactions processed on the Hedera network. externalDocs: url: >- https://docs.hedera.com/guides/docs/mirror-node-api/cryptocurrency-api#transactions - name: topics description: >- The topics object represents the information associated with a topic entity and returns topic messages information. externalDocs: url: >- https://docs.hedera.com/guides/docs/mirror-node-api/cryptocurrency-api#topic-messages - name: tokens description: >- The tokens object represents the information associated with a token entity and returns a list of token information.The tokens list endpoint is cached and not updated as frequently as the token lookup by a specific ID. externalDocs: description: REST API Docs url: https://docs.hedera.com/guides/docs/mirror-node-api/cryptocurrency-api paths: /api/v1/topics/messages/{timestamp}: get: tags: - topics summary: Get topic message by consensusTimestamp description: Returns a topic message the given the consensusTimestamp. operationId: getTopicMessageByTimestamp parameters: - $ref: '#/components/parameters/timestampPathParam' responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/TopicMessage' '400': $ref: '#/components/responses/InvalidParameterError' '404': $ref: '#/components/responses/NotFoundError' components: parameters: timestampPathParam: name: timestamp in: path description: >- The Unix timestamp in seconds.nanoseconds format, the timestamp at which the associated transaction reached consensus. See [unixtimestamp.com](https://www.unixtimestamp.com/) for a simple way to convert a date to the 'seconds' part of the Unix time. required: true example: 1234567890.0000007 schema: type: string pattern: ^\d{1,10}(\.\d{1,9})?$ schemas: TopicMessage: type: object properties: chunk_info: $ref: '#/components/schemas/ChunkInfo' consensus_timestamp: $ref: '#/components/schemas/Timestamp' message: type: string payer_account_id: $ref: '#/components/schemas/EntityId' running_hash: type: string format: byte running_hash_version: format: int32 type: integer sequence_number: format: int64 type: integer topic_id: $ref: '#/components/schemas/EntityId' required: - consensus_timestamp - message - payer_account_id - running_hash - running_hash_version - sequence_number - topic_id example: chunk_info: initial_transaction_id: 0.0.10-1234567890-000000321 nonce: 3 number: 1 total: 2 scheduled: true consensus_timestamp: '1234567890.000000001' message: bWVzc2FnZQ== payer_account_id: 0.0.10 running_hash: cnVubmluZ19oYXNo running_hash_version: 2 sequence_number: 1 topic_id: 0.0.7 ChunkInfo: type: object nullable: true properties: initial_transaction_id: $ref: '#/components/schemas/TransactionId' number: example: 1 format: int32 type: integer total: example: 2 format: int32 type: integer Timestamp: description: A Unix timestamp in seconds.nanoseconds format type: string example: '1586567700.453054000' pattern: ^\d{1,10}(\.\d{1,9})?$ EntityId: type: string description: Network entity ID in the format of `shard.realm.num` pattern: ^\d{1,10}\.\d{1,10}\.\d{1,10}$ example: 0.0.2 nullable: true Error: type: object properties: _status: type: object properties: messages: type: array items: type: object properties: data: description: Error message in hexadecimal example: '0x3000' format: binary nullable: true pattern: ^0x[0-9a-fA-F]+$ type: string detail: description: Detailed error message example: Generic detailed error message nullable: true type: string message: description: Error message example: Generic error message nullable: false type: string TransactionId: type: object properties: account_id: $ref: '#/components/schemas/EntityId' nonce: example: 0 format: int32 type: integer minimum: 0 nullable: true scheduled: example: false type: boolean nullable: true transaction_valid_start: $ref: '#/components/schemas/Timestamp' responses: InvalidParameterError: description: Invalid parameter content: application/json: schema: $ref: '#/components/schemas/Error' example: _status: messages: - message: 'Invalid parameter: account.id' - message: >- Invalid Transaction id. Please use \shard.realm.num-sss-nnn\ format where sss are seconds and nnn are nanoseconds NotFoundError: description: Not Found content: application/json: schema: $ref: '#/components/schemas/Error' example: _status: messages: - message: Not found ````