Tino Developers
POST/v1/domain/@id/reg

Manage private nameservers

Register, modify or delete private nameservers (glue records) of the domain; choose the operation with action:

  • registerNameServer: register a new glue record (needs nameserver, ip)
  • modifyNameServer: change the IP of a glue record (needs nameserver, oldip, newip)
  • deleteNameServer: delete a glue record (needs nameserver)
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

NameTypeRequiredDescription
idstringRequiredDomain ID

Body (JSON)

NameTypeRequiredDescription
actionstringOptionalOperation: registerNameServer, modifyNameServer, deleteNameServer
nameserverstringOptionalFull nameserver hostname
ipstringOptionalIP address for the nameserver – required for registerNameServer
oldipstringOptionalCurrent IP address – required for modifyNameServer
newipstringOptionalNew IP address – required for modifyNameServer

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 codeDescription
401 · invalid_tokenThe token is wrong, expired or revoked.
403 · insufficient_scopeThe token lacks the domains:write scope.
403 · ip_not_allowedA 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.