This list is generated from the same definitions the server registers, so it matches what tools/list returns.
estimate_message_costZBS template message cost (Zalo)- Estimate what Zalo charges for ZBS template messages (formerly ZNS): base price by template type (otp, voucher, payment_request, bus_ticket, custom = "other types", rating, quick_response, carousel, journey "from" price) for phone or UID sending, plus buttons by category (the first button to the OA page/Mini App/OA article and the first to an e-invoice page are free, others paid from the first), image module and quick reply. Returns the price per message with a line breakdown, the total if all messages are delivered, the estimate for delivery_rate (only delivered messages are charged), totals with VAT if you pass vat_rate (Zalo names no rate), the OA plan needed to send through the API, and days needed at the daily quota (default 20000, a new OA). OTP, quick response, journey and carousel by UID are rejected. Prices exclude VAT. Reference only, no messages are sent. Examples: {"template_type":"custom","buttons":["business_website"],"count":10000}; {"template_type":"custom","delivery":"uid","buttons":["oa_profile_page"],"count":5000,"delivery_rate":0.9,"vat_rate":0.1}; {"template_type":"otp","count":20000}.
oa_plan_compareZalo OA plan comparison- Compare the Zalo Official Account plans in force from 1 June 2026 (Cơ bản, Tiêu chuẩn, Tăng trưởng, Toàn diện) with prices including 10% VAT, staff accounts, Open API and its requests-per-minute limit, consultation messages outside the 48-hour window and features, and pick the smallest plan that meets your needs (needs_api, api_requests_per_minute, replies_outside_48h_per_month, staff, features, term_months 6 or 12), with the reason and the paid-reply overage. The Cơ bản price is not published by Zalo. Reference only. Examples: {}; {"needs_api":true,"staff":8}; {"replies_outside_48h_per_month":3000,"features":["chatbot"],"term_months":6}.
validate_templateCheck a ZBS template draft (formal rules)- Check a ZBS template draft against the formal technical rules Zalo publishes: template name, title and text block lengths and parameter counts, table rows and cell lengths, number of buttons (2 vs 3 conflict reported as a warning), button text and URL length, parameters only in the URL path, one OA page button, logo PNG 400x96, image module 1-3 images 16:9 up to 500 KB, parameter types and sample lengths, and formal content hints (links or phone numbers in the text, icons, "anh/chị", superlatives in Tag 3). Types: custom, otp, rating, quick_response. Returns errors and warnings with the rule and the official page. Content is reviewed by Zalo, not here; the text is not stored. Example: {"template_type":"custom","tag":1,"title":"Order <order_code> confirmed","paragraphs":["Hello <customer_name>, your order <order_code> is on its way."],"buttons":[{"category":"business_website","text":"Track order","url":"https://shop.example.vn/track/<order_code>"}],"logo":{"format":"PNG","width":400,"height":96}}.
check_sending_rulesCheck ZBS sending window, quota and promotion limits- Check whether a ZBS template send is allowed: the sending window by tag in Vietnam time (Tag 1 round the clock, Tag 2 and 3 07:00-22:00; for Tag 1 at night a warning notes the -133 wording; the conflicting announcement dates are named), the OA daily quota (levels 1000, 5000, 20000, 50000, unlimited; default 20000), Tag 3 limits per user (1 per day, 30 per month), and the quota upgrade conditions (Good quality over 7 days and 2 x the daily quota sent in 7 days). Reference only, nothing is sent. Examples: {"tag":3,"send_time":"21:30","daily_volume":15000}; {"tag":2,"send_time":"06:30"}; {"tag":3,"promo_sent_to_user_today":1}; {"tag":1,"quota_level":20000,"sent_last_7_days":45000}.
choose_channelChoose a Zalo channel for a task- Suggest which Zalo channel fits a business task, by simple published rules: ZBS template message (with the template type, tag, price and window), a free consultation reply within 48 hours of the user's last interaction (paid outside 48 hours, not allowed after 7 days), an OA broadcast to followers, or a Mini App. Tasks: otp, order_status, delivery_tracking, payment_request, appointment_reminder, customer_reply, service_rating, promotion, voucher, birthday_greeting, news_to_followers, catalog_checkout. Optional: last_interaction_hours, is_follower. Reference only. Examples: {"task":"order_status"}; {"task":"customer_reply","last_interaction_hours":30}; {"task":"promotion","is_follower":true}.
error_lookupZalo error code lookup- Explain a Zalo error code in plain words: which table it comes from (ZBS Template Message, the archived ZNS table, or the Official Account API; the same code can mean different things in different tables) and what to check. A positive number is also tried as negative. Examples: {"code":-133}; {"code":-100,"table":"oa_api"}; {"code":249}.
data_infoZalo reference data: sources and gaps- Return the data version and retrieval date, the official Zalo pages used, what Zalo does not publish (Cơ bản plan price, broadcast price above the free allowance, Mini App fees, the VAT rate for template messages, and others), where Zalo's own pages disagree (maximum buttons, night window, OTP by UID, old fallback prices) and how this tool resolves it, the change log and the worked example. Use when the user asks how current or reliable the figures are. Takes no arguments: {}.