> 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/messages/message.md).
# Message
This is **where you say what matters**—the actual content your users need to see. Whether it’s an alert, a reminder, or a funny status update, the `message` field is what grabs attention.
* **No strict length limit** (but practical limits apply for readability).
* **Supports line breaks** for better formatting.
* **Works with emojis** because everything is better with emojis. 😎
* **Plain text only**—no markdown, HTML, or rich formatting.
#### Use Cases
The `message` can be used in many ways, from simple alerts to detailed reports. Here are some good examples:
**Good Use Cases**
✅ **System Alerts:** `"Server CPU at 95%! Check logs now."`\
✅ **Reminders:** `"Water the plants today!"`\
✅ **Status Updates:** `"Your order #12345 has shipped!"`\
✅ **Error Notifications:** `"❌ Backup failed! Check /logs for details."`
**Bad Use Cases**
❌ **Sending entire log files.** (`"Error 404. Error 405. Error 406. Error..."` 😵)\
❌ **Writing an essay.** (Nobody reads 10 paragraphs in a push notification.)\
❌ **Adding unsupported formatting.** (`"Bold Text"` won’t work!)
#### Requirements
Attribute
Data Type
Validation Criteria
message
string
text
#### Example Request
{% code overflow="wrap" %}
```bash
curl -X "POST" "https://api.justpush.io/messages" \
-H 'Content-Type: text/plain; charset=utf-8' \
-d $'{
"user": "<< USER KEY >>",
"title": "A simple title"
}'
```
{% endcode %}
#### Mobile App
Below you see an example of how this is displayed as a push message and within the app.
**Push Message**
Push Message with Title and Message
**Within JustPush.io App.**
***
#### Frequently Asked Questions
How long can a message be?
There’s no strict limit, but **shorter is better**—users prefer quick, scannable content.
Can I use line breaks?
Yes! Line breaks work, so you can separate content for clarity.
Do emojis work?
Yup! All of them
Can I use HTML or markdown?
No, the message field only supports **plain text**.
***
## 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/messages/message.md?ask=
```
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.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.justpush.io/introduction/objects/messages/message.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.