> For the complete documentation index, see [llms.txt](https://docs.justpush.io/introduction/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.justpush.io/introduction/objects/topics/title.md).

# Title

The `title` is the display name of your topic. It doesn’t affect how messages are sent, but it *does* make your topic easier to recognize—especially when users are subscribing or managing multiple topics. Without a title, the topic will just show its unique ID (which, let’s be honest, looks like a Wi-Fi password).

A clear title helps give your topic purpose—whether it’s `"Build Notifications"`, `"Marketing Alerts"`, or `"🚨 Emergency Updates"`. Use it to make your push ecosystem a little more human.

#### **Use Cases**

**Good Ideas**

Use topics to send messages to specific streams or audiences, without spamming everything and everyone.

✅ **DevOps:** `"Staging Alerts"`, `"Production Errors"`, `"Deploy Logs"`\
✅ **Projects:** `"Team Alpha Updates"` vs. `"Marketing Launches"`\
✅ **Fun Stuff:** `"Dad Jokes of the Day"` or `"Cat Cam Alerts"`

**Bad Ideas**

❌ **Leaving the title blank.** Nobody’s excited to subscribe to `"topic-8f23a6b..."`.

❌ **Using vague titles.** `"Stuff"`, `"Misc"`, or `"Things"` doesn’t help anyone.

❌ **Overusing emojis.** `"🚨🔥💥😱🧯💣⚠️"` is fun once. Then it’s chaos.

❌ **Naming every topic the same.** `"Alerts"` for *everything* defeats the purpose of using topics at all.

#### Requirements

| Attribute | Data Type | Validation Criteria |
| --------- | --------- | ------------------- |
| `title`   | `string`  | `max 100`           |

#### Example Request

```bash
curl -X "POST" "https://api.justpush.io/topics" \
     -H 'Content-Type: application/json; charset=utf-8' \
     -d $'{
  "title": "A simple title",
  "user": "<< USER KEY>>",
}'
```

***

#### Frequently Asked Questions

<details>

<summary><strong>Is the topic title required?</strong></summary>

Yup it is!

</details>

<details>

<summary><strong>Can I change the title after creating the topic?</strong></summary>

Yes! Use a `PUT` request to update the title anytime.

</details>

<details>

<summary><strong>Does the title affect message delivery?</strong></summary>

Not at all. It’s just for display—messages are still sent using the topic’s unique ID.

</details>

<details>

<summary><strong>Can two topics have the same title?</strong></summary>

Yes, titles aren’t unique. Just make sure you don’t confuse yourself (or your users).

</details>

<details>

<summary><strong>Can I use emojis in the title?</strong></summary>

Absolutely! Just don’t go full emoji salad. 🌽🍅🥕

</details>

***

## Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.justpush.io/introduction/objects/topics/title.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.