Zalo Notifications

Overview

• Source: https://zalo.me
• Image Support: No
• Attachment Support: No
• Message Character Limits:
  • Body: 2000
• Supported Body Format(s):
  • ✓MARKDOWN
  • TEXT
• Build Your Apprise URL

Account Setup

Apprise sends Zalo messages through a Zalo Bot.

1. In the Zalo app, search for the Zalo Bot Manager account.
2. Choose Create bot from its menu. The bot name must start with Bot (for example Bot Apprise).
3. Zalo sends you a message containing your Bot Token. It looks like 123456789:abcdefghijKLMNOPqrst.

Next, find the Chat ID of each person or group you want to notify:

1. Have them send any message to your bot.

2. Open the following link in your browser, using your own Bot Token:

   https://bot-api.zaloplatforms.com/bot{bot_token}/getUpdates

3. The Chat ID is the id value found inside the chat section of the response.

Note

The getUpdates link does not work if your bot already has a webhook set up.

Note

Attachments are not supported. Zalo only accepts photos that are already hosted online, not file uploads.

Syntax

Valid syntax is as follows:

• zalo://{bot_token}/{chat_id}
• zalo://{bot_token}/{chat_id1}/{chat_id2}/{chat_idN}

Parameter Breakdown

Variable	Required	Description
bot_token	Yes	The Bot Token Zalo sent you when the bot was created. It looks like 123456789:abcdef.
chat_id	Yes	The Chat ID of a person or group to notify. Add as many as you like, separated by a slash.
format	No	Use markdown (the default) for bold, italic, headings and lists, or text for plain text.

Global Parameters

Variable	Description
overflow	Controls messages that exceed a service’s documented limit. The default is upstream. 👉 upstream: Send one message without splitting or truncating it for that limit. 👉 truncate: Keep the portion that fits and discard the rest. 👉 split: Prefer a readable break, fall back to a hard boundary, and send every part in order. Splitting undeclared or structured content is best effort. Use upstream when the body must remain one intact document.
format	This parameter can be set to either text, html, or markdown. Some services support the ability to post content by several different means. The default of this varies (it can be one of the 3 mentioned at any time depending on which service you choose). You can optionally force this setting to stray from the defaults if you wish. If the service doesn’t support different types of transmission formats, then this field is ignored.
verify	External requests made to secure locations (such as through the use of https) will have certificates associated with them. By default, Apprise will verify that these certificates are valid; if they are not then no notification will be sent to the source. In some occasions, a user might not have a certificate authority to verify the key against or they trust the source; in this case you will want to set this flag to no. By default it is set to yes.
redirect	By default, Apprise will follow HTTP redirects (3xx responses) issued by the remote server, matching the behaviour of the underlying requests library. If you want to prevent custom headers and credentials from being forwarded to destinations that differ from the original URL, set this to no. By default it is set to yes.
cto	This stands for Socket Connect Timeout. This is the number of seconds Requests will wait for your client to establish a connection to a remote machine (corresponding to the connect()) call on the socket. The default value is 4.0 seconds.
rto	This stands for Socket Read Timeout. This is the number of seconds the client will wait for the server to send a response. The default value is 4.0 seconds.
emojis	Enable Emoji support (such as providing :+1: would translate to 👍). By default this is set to no. Note: Depending on server side settings, the administrator has the power to disable emoji support at a global level; but default this is not the case.
tz	Identify the IANA Time Zone Database you wish to operate as. By default this is detected based on the configuration the server hosting Apprise is running on. You can set this to things like America/Toronto, or any other properly formated Timezone describing your area.
retry	The number of additional delivery attempts to make after the first failure before giving up. Accepts an integer in the range 0 to 10. The default is 0 (no retries – a single attempt is made). When combined with wait, Apprise pauses the specified number of seconds between each attempt.
wait	The number of seconds to pause between retry attempts. Accepts a decimal value in the range 0.0 to 20.0; integer values are promoted to float automatically. The default is 0.5. This value is only meaningful when retry is greater than zero – a service with retry=0 makes exactly one attempt regardless of the wait value.
optional	When set to yes, a delivery failure for this service is silently absorbed. The overall notify() call still evaluates as true even if this endpoint was unreachable, provided that every required (non-optional) service in the same batch succeeded. Setting this flag does not skip delivery or bypass retry logic – all configured retry attempts are still made before the failure is absorbed. By default this is set to no, meaning every failure is propagated to the caller.

Examples

Send a message to one person:

# Replace 123456789:abcdefghij with your Bot Token
# Replace abc.xyz with the Chat ID to notify
apprise -vv -t "Alert" -b "Something happened." \
    zalo://123456789:abcdefghij/abc.xyz

Send a plain text message to two chats:

apprise -vv -b "Backup complete." \
    "zalo://123456789:abcdefghij/abc.xyz/def.uvw?format=text"