There are 3 routes that help to manage a given topic before sending consensus messages. The focus is that if you have a particular group of users or a particular app that you wish to have a separate topic to keep track of messages you can do so with different topics.
All routes required authentication through the x-api-key and a escaped JSON value can be injected into the memo to hold more information about the topic.
Get the topic information using a supplied topic_id.
Create a topic with 2 optional values, the memo or the enable_private_submit_key which stops any other account to successfully sent a consensus message to the topic.
Update the memo of a given topic by providing a memo property to the body.