Hubz API v1 (beta) · Hubz v0.7.0 · 2026-11-06
Rate limits and error codes
Rate limits
About 300 requests a minute per key. This may change during the beta. Over the limit, the API returns 429 with a Retry-After header (seconds to wait).
Messages sent through the API go through the same queue and anti-spam limits of the Zalo account as messages staff send by hand, so a message may wait a few seconds before it reaches the customer. It is returned with status queued, then becomes sent or failed (message.updated event).
Error codes
| Code | Meaning |
|---|---|
400 | The request data is invalid; details says what is wrong. |
401 | The key is wrong or has been revoked. |
403 | The key or the staff member (X-Hubz-User) lacks permission. |
404 | Not found, or not visible to this key. |
429 | Rate limit exceeded: wait for Retry-After, then retry. |
A 400 error (the message is in Vietnamese):
{"error": "Dữ liệu không hợp lệ", "details": ["…"]}Other errors:
{"error": "…"}Hubz is not affiliated with Zalo or VNG; Hubz does not use Zalo’s official API. Hubz is not affiliated with Odoo S.A.; Odoo is a trademark of Odoo S.A.