/v1/domains/@id/registrantSave a waiting domain's registrant
JSON body {"registrant": {…}, "owner": {…} | null} or {"from_domain_id": N} (the registrant of running domain N, from GET /v1/registrants). After saving, Tino tries to register right away and returns the new dossier. Requires the domains:registrant scope: only personal API tokens with an IP restriction. Required fields: Domain registrant dossier.
Only a personal API token with the domains:registrant scope and an IP allow-list can call this route; OAuth apps never get this scope.
Authentication
Send the token in the header Authorization:
Authorization: Bearer <token>
Tokens that can call it: personal API tokens (tinopat_) with an IP allow-list.
Scopes
domains:registrant
Parameters
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | int | Required | Domain ID |
Response
No live sample: the route changes real data or the test account has no data for it. The answer is a JSON object; errors follow the common shape in Calling the Tino API.
Error codes
| Error code | Description |
|---|---|
401 · invalid_token | The token is wrong, expired or revoked. |
403 · insufficient_scope | The token lacks the domains:registrant 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.