PUT
/v1/domain/@id/emforwardingUpdate email forwarding
Set the domain's email forwarding rules.
API v1 · Updated 2026-10-21View .md
Call it through the gateway https://api.tino.vn/v1 with a token that has the domains:write scope; see Calling the Tino API.
Authentication
Send the token in the header Authorization:
Authorization: Bearer <token>
Tokens that can call it: app tokens (tinoat_, Sign in with Tino) or personal API tokens (tinopat_).
Scopes
domains:writeDomain management
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string | Required | Domain ID |
Body (JSON)
| Name | Type | Required | Description |
|---|---|---|---|
from | string | Optional | Email address that you want to forward |
to | string | Optional | Email address that will receive forwarded emails |
records | array | Optional | Multiple forwarding rules [{"from":"info","to":"dest@example.com"},{"from":"support","to":"help@example.com"}] |
Response
The route's JSON answer, in the same shape as UserAPI returns it (Personal data). Live sample from a test account with personal data masked; long arrays and strings are trimmed (… N more item(s), … N more line(s)).
Error codes
| Error code | Description |
|---|---|
401 · invalid_token | The token is wrong, expired or revoked. |
403 · insufficient_scope | The token lacks the domains:write scope. |
403 · ip_not_allowed | A personal API token called from an IP outside its allow-list. |
Business errors of a route usually come as HTTP 200 with {"error": ["<code>"]}; see common error codes.