4 posts tagged with "api"

An email group turns an address on a receiving domain, such as [email protected], into a shared address: every message sent to it is forwarded to each member, like a Google Workspace group. Create groups under Email → Email groups.

The Email API now checks the scopes of the key, as the dashboard has always described them:

• 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.

Four new channels feed the Inbox, alongside the website widget, Zalo, Messenger, Instagram, TikTok and email. The AI assistant, flows, distribution rules and reports work on them as on every other channel. Connect them under Support → Channels → Add channel.

https://api.hatang.dev/openapi.json now describes every public webhook event in the OpenAPI 3.1 webhooks section, with the payload each one carries, instead of a bare list of names. The chat gateway's spec is published at https://chat.hatang.dev/openapi.json with stable operationIds.

• 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.