• MCP server @hatang/mcp 0.1.0. npx -y @hatang/mcp gives an agent search_docs and read_doc (no key needed) and, with an API key, tools to send email, check domains, create and simulate VietQR payments, read e-invoices, work the inbox and add knowledge for the AI assistant. --read-only keeps it to lookups. See MCP server.
• Docs for machines. /docs/llms.txt lists every page, /docs/llms-full.txt holds the whole hub, every page has a Markdown copy at its URL plus .md, and the OpenAPI spec is at /docs/openapi.json. The same in Vietnamese under /vi/docs.
• Rules for your project. One AGENTS.md section, a Cursor rule and a Claude Code skill that tell an agent which SDK to use, where the key lives and how to verify payments and webhooks. See Use Ha Tang with AI coding agents.
• Recipes. Email from Node.js, VietQR payments, Zalo ZNS from code, live chat on a website and e-invoices through the API.

• Each README ends with an About Ha Tang section and links to its guide, the API reference, this changelog and support.
• The iOS and Android SDKs ship a LICENSE file (MIT).
• The Python package no longer links source and changelog pages that were not public.

Upgrading is optional. See all SDKs and supported versions.

• Each member gets their own copy from the group address, shown as "Sender via Group name", with Reply-To the original sender.
• Spam, automated mail, mail that already went through a group and more than 30 messages per sender per hour are not forwarded. The original always stays in Receiving.
• Each copy counts toward the daily send quota and appears in Emails with source forward.

For API consumers:

• New endpoints POST/GET /email-groups and GET/PATCH/DELETE /email-groups/{id} (email:write to change, email:read to list). @hatang/sdk gains hatang.emailGroups.
• source on emails has a new value, forward. If your code switches on it, add a default branch.

See the Email groups guide.

• The mailbox page says so and the channel shows Active right away. support+billing@ style addresses work too; the part after + becomes a tag.
• Only the support address itself moves to the Inbox. Other addresses on the domain, email groups included, stay under Email → Received and keep firing email.received.
• Connecting a support address you had disconnected now reconnects it, keeping its conversations, instead of saying it is already connected.

See Connect a support email address.

• Sending (POST /emails, POST /emails/batch, the SMTP relay) and changing a scheduled send (PATCH /emails/{id}, POST /emails/{id}/cancel) need email:send.
• Reading emails (GET /emails, GET /emails/{id}, GET /emails/{id}/events) needs email:read; email:send and email:write include it.

Before, any valid key could call these endpoints. A key without the scope now gets 401 restricted_api_key (550 5.7.1 over SMTP). Keys with full access (*), email:* or email:send are not affected. If a key that sends email has only other scopes, such as email:write or chat:*, add email:send to it under API Keys in the dashboard.

The developer hub keeps what you need to build with Ha Tang: the API and SDK guides, the references, webhooks and the realtime protocol. Guides that were only dashboard steps moved to the help center, and their old addresses redirect there:

• every channel guide (Zalo OA, Zalo personal, TikTok, TikTok Shop, Messenger and Instagram, WhatsApp, Telegram, LINE, X, email), now under Channels;
• Team and roles, now Employees and roles;
• Businesses and modules, now Turn modules on and off.

The Support overview still lists every channel with its channel value for the API.

New calls:

• Templates: templates.create/get/list/update/remove/publish/duplicate, and emails.send({ to, template: { id, variables } }).
• Global contacts: contacts.* without audience_id, by id or email, with properties, segments and topics; new segments, topics and contactProperties namespaces. audience_id still uses the older audience routes.
• Automations: events.*, automations.* and automations.runs.*.
• Insights: emails.metrics(), logs.list/get and usage.get.

The blog namespace is removed. See the Node.js guide.

• WhatsApp: a WhatsApp Business number through Embedded Signup. The number keeps working in the WhatsApp Business app (coexistence), and messages sent from the phone show in the conversation. After the 24-hour window, agents reply with an approved template.
• Telegram: your Telegram bot. With Telegram Premium you can also link it through Telegram Business, so chats sent to your own account reach the Inbox too. It uses the Bot API only.
• X: direct messages, plus auto-replies to @mentions and to replies to your posts. Each business connects its own X developer app, because X bills API usage per call.
• LINE: a LINE Official Account through the Messaging API, with one-to-one chats only.

For API and webhook consumers:

• channel on conversations, customers and webhook payloads has four new values: whatsapp, telegram, x and line. The same values work in the channel filter of GET /chat/customers. If your code switches on channel, add a default branch, because more channels will follow.
• In @hatang/sdk 0.4.0 and later, the ChatChannel type includes the new values.
• A WhatsApp template reply is an agent message with metadata.whatsapp_template set to { name, language, params }.

• New guides: authentication, rate limits, errors, pagination, idempotency, sending email, domains, SMTP relay, broadcasts, deliverability, every support channel and more.
• The REST API reference is now part of the hub, with one page per endpoint, code samples in seven languages and a "Try it" console.
• Every webhook event has its own page with the payload schema.

• Operations are filed under one tag per resource (Conversations, Customers, Orders, Tickets…), and every tag belongs to a group.
• 429 responses state the real limit of each API: 10 requests per second for Email, 50 for Support and 20 for Payments.
• The API answers CORS preflights from https://hatang.dev, so the reference's "Try it" console can call it with your key.

• Header: the subtitle under the site name, and the business logo (or the site name's first letter) instead of agent photos when the profile is set to the business.
• Greeting: hidden when it is turned off or off on phones; signed with the first online agent's name when the sender is "online agent".
• Contact buttons: Zalo, Messenger, phone and email pills under the header.

New strings for the contact buttons (callUs/call and emailUs) must be passed when you build the strings object by hand. Older gateways omit the settings and the screens look as before. React Native 0.3.1 fixes the package's repository metadata.