GET/v1/domains/pending

Domains awaiting their dossier

Paid domains that could not be registered yet because the registrant details or dossier (eKYC, declaration) are incomplete, with what is left to do (actions) and ready while Tino registers them. Requires the domains:registrant scope: only personal API tokens with an IP restriction. Guide: Domain registrant dossier.

API v1 · Updated 2026-10-21View .md

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

This route takes no parameters.

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.