> ## Documentation Index
> Fetch the complete documentation index at: https://hedera-0c6e0218-mintlify-bc559771.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Create a topic
> Create a new Hedera Consensus Service topic with TopicCreateTransaction, configure admin and submit keys, then read the topic ID from the receipt.
A transaction that creates a new topic recognized by the Hedera network. The newly generated topic can be referenced by its `topicId`. The `topicId` is used to identify a unique topic to submit messages to. You can obtain the new topic ID by requesting the receipt of the transaction. All messages within a topic are sequenced with respect to one another and are provided a unique sequence number.
**Note**
With the Consensus Node Release [v0.60](/learn/release-notes/services#release-v0.60), you can set an auto renew account ID without the requirement of setting an admin key on the topic.
#### Private topic
You can also create a private topic where only authorized parties can submit messages to that topic. To create a private topic you would need to set the `submitKey` property of the transaction. The `submitKey` value is then shared with the authorized parties and is required to successfully submit messages to the private topic.
#### Topic Properties
| Field | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Admin Key** | Access control for updateTopic/deleteTopic. If no adminKey is specified, anyone can increase the topic's expirationTime with updateTopic, but they cannot use deleteTopic. However, if an adminKey is specified, both updateTopic and deleteTopic can be used. |
| **Submit Key** | Access control for submitMessage. No access control will be performed specified, allowing all message submissions. |
| **Topic Memo** | Store the new topic with a short publicly visible memo. (100 bytes) |
| **Auto Renew Account** | At the topic's expirationTime, the optional account can be used to extend the lifetime up to a maximum of the autoRenewPeriod or duration/amount that all funds on the account can extend (whichever is the smaller).
Currently, rent is not enforced for topics so no auto-renew payments will be made.
Note: If the developer does not explicitly set autoRenewAccount, the SDK will automatically default to using the transaction fee payer account ID for the auto renew account. This is beneficial in the event an admin key is not set.
|
| **Auto Renew Period** | The initial lifetime of the topic and the amount of time to attempt to extend the topic's lifetime by automatically at the topic's expirationTime. Currently, rent is not enforced for topics so auto-renew payments will not be made.
NOTE: The minimum period of time is approximately 30 days (2592000 seconds) and the maximum period of time is approximately 92 days (8000001 seconds). Any other value outside of this range will return the following error: AUTORENEW\_DURATION\_NOT\_IN\_RANGE.
|
| **Fee Schedule Key** | (Optional) A key that controls updates and deletions of topic fees. **Must be set at creation; cannot be added later via `updateTopic`**. |
| **Fee Exempt Keys** | (Optional) A list of keys that, if used to sign a message submission, allow the sender to bypass fees. **Can be updated later via `updateTopic`**. |
| **Custom Fees** | (Optional) A fee structure applied to message submissions for revenue generation. Can be updated later via updateTopic, but must be signed by the Fee Schedule Key.
Defines a fixed fee required for each message submission to the topic. This fee can be set in HBAR or HTS fungible tokens and applies when messages are submitted.
|
**Transaction Signing Requirements:**
* If an **Admin Key** is specified, the Admin Key must sign the transaction.
* If no **Admin Key** is specified, the topic is immutable.
* If an **Auto Renew Account** is specified, that account must also sign this transaction.
* If a **Fee Schedule Key** is specified, the Fee Schedule Key must sign the transaction.
* If a Fee Exempt Key List is specified, it contains a list of public keys that are exempt from paying fees when submitting messages to the topic. These keys do not need to sign the transaction.
**Transaction Fees**
* Each **transaction** incurs a **standard Hedera network fee** based on network resource usage.
* If a **custom fee** is set for a topic, users submitting messages must pay this fee in **HBAR or HTS tokens**.
* The **Fee Schedule Key** allows authorized users to update fee structures. If set, it must sign transactions modifying fees.
* Fee exemptions can be granted using the **Fee Exempt Key List**.
* Use the [Hedera Fee Estimator](https://hedera.com/fees) to estimate standard network fees.
#### Methods
| **Method** | **Type** | **Requirements** |
| --------------------------------------- | --------------------- | ---------------- |
| `setAdminKey()` | Key | Optional |
| `setSubmitKey()` | Key | Optional |
| `setTopicMemo()` | String | Optional |
| `setAutoRenewAccountId()` | AccountId | Optional |
| `setAutoRenewPeriod()` | Duration | Optional |
| `setFeeScheduleKey()` | Key | Optional |
| `setFeeExemptKeys()` | List\ | Optional |
| `setCustomFees()` | List\ | Optional |
| `addCustomFee()` | CustomFixedFee | Optional |
| `addFeeExemptKey()` | Key | Optional |
| `setHighVolume()` | boolean | Optional |
```java Java theme={null}
//Create the transaction
TopicCreateTransaction transaction = new TopicCreateTransaction()
.setFeeScheduleKey(feeScheduleKey)
.setFeeExemptKeys(feeExemptKeys)
.setCustomFees(customFees);
//Sign with the client operator private key and submit the transaction to a Hedera network
TransactionResponse txResponse = transaction.execute(client);
//Request the receipt of the transaction
TransactionReceipt receipt = txResponse.getReceipt(client);
//Get the topic ID
TopicId newTopicId = receipt.topicId;
System.out.println("The new topic ID is " + newTopicId);
//v2.0.0
```
```javascript JavaScript theme={null}
//Create the transaction
const transaction = new TopicCreateTransaction()
.setFeeScheduleKey(feeScheduleKey)
.setFeeExemptKeys(feeExemptKeys)
.setCustomFees(customFees);
//Sign with the client operator private key and submit the transaction to a Hedera network
const txResponse = await transaction.execute(client);
//Request the receipt of the transaction
const receipt = await txResponse.getReceipt(client);
//Get the topic ID
const newTopicId = receipt.topicId;
console.log("The new topic ID is " + newTopicId);
//v2.0.0
```
```go Go theme={null}
//Create the transaction
transaction := hedera.NewTopicCreateTransaction().
.setFeeScheduleKey(feeScheduleKey).
.setFeeExemptKeys(feeExemptKeys).
.setCustomFees(customFees)
//Sign with the client operator private key and submit the transaction to a Hedera network
txResponse, err := transaction.Execute(client)
if err != nil {
panic(err)
}
//Request the receipt of the transaction
transactionReceipt, err := txResponse.GetReceipt(client)
if err != nil {
panic(err)
}
//Get the topic ID
newTopicID := *transactionReceipt.TopicID
fmt.Printf("The new topic ID is %v\n", newTopicID)
//v2.0.0
```
```rust Rust theme={null}
// Create a new topic
let transaction = TopicCreateTransaction::new()
.topic_memo("My topic memo")
.admin_key(admin_key)
.submit_key(submit_key)
.auto_renew_period(Duration::hours(24 * 30)); // 30 days
// Sign with the client operator private key and submit to a Hedera network
let tx_response = transaction.execute(&client).await?;
// Request the receipt of the transaction
let receipt = tx_response.get_receipt(&client).await?;
// Get the topic ID
let topic_id = receipt.topic_id.unwrap();
println!("The new topic ID is {:?}", topic_id);
// v0.34.0
```
## Get transaction values
| **Method** | **Type** | **Requirements** |
| ------------------------- | --------- | ---------------- |
| `getAdminKey(adminKey)` | Key | Optional |
| `getSubmitKey(submitKey)` | Key | Optional |
| `getTopicMemo(memo)` | String | Optional |
| `getAutoRenewAccountId()` | AccountId | Required |
| `getAutoRenewPeriod()` | Duration | Required |
| `getFeeScheduleKey()` | Key | Optional |
| `getFeeExemptKeys()` | List | Optional |
| `getCustomFees()` | List | Optional |
```java Java theme={null}
//Create the transaction
TopicCreateTransaction transaction = new TopicCreateTransaction()
.setFeeScheduleKey(feeScheduleKey);
//Get the fee schedule key from the transaction
Key getFeeScheduleKey = transaction.getFeeScheduleKey();
//V2.0.0
```
```javascript JavaScript theme={null}
const transaction = new TopicCreateTransaction()
.setFeeScheduleKey(feeScheduleKey);
//Get the fee schedule key from the transaction
const feeScheduleKey = transaction.getFeeScheduleKey();
//V2.0.0
```
```java Go theme={null}
transaction := hedera.NewTopicCreateTransaction().
SetFeeScheduleKey(feeScheduleKey)
getFeeScheduleKey := transaction.GetFeeScheduleKey()
//V2.0.0
```
This transaction supports [high-volume entity creation](/learn/core-concepts/high-volume-entity-creation)
(HIP-1313). Setting `setHighVolume(true)` routes the transaction through dedicated
high-volume throttle capacity with variable-rate pricing. Always pair this with
`setMaxTransactionFee()` to cap your costs.