POST /v2/domains/requirements
{
  "domain": "example.com",
  "operation": "register"
}

This route requires domains:read and an Idempotency-Key. The optional provider selector is used where needed; follow the current contract rather than inventing a registrar name.

1. Resolve the full domain and intended operation before requesting fields.
2. Read the returned requirements, allowed values and consent information.
3. Render only the relevant inputs and explain why restricted information is required.
4. Collect the customer's actual answers and explicit consents.
5. Submit those values in additional_fields with the registration or transfer request.

Standard contacts identify the registrant and other permitted roles. Registry-specific fields can establish eligibility, local presence or an IDN language. A complete address does not replace a required accreditation or registry declaration.

Do not preselect a consent merely to make validation pass. If the customer cannot satisfy a restricted TLD's requirements, offer a suitable alternative or the documented review process.

A REGISTRY_FIELDS_INVALID response indicates that the current rule set was not satisfied. Read the field errors and ask for the specific missing or incorrect information. Reusing a generic form from another extension may omit required fields even when it worked for a previous order.

Requirements can vary by operation. A transfer form should request the transfer contract rather than blindly copying registration fields. Obtain a fresh contract when the domain or operation changes.

Collect only information requested by the actual workflow and use the approved account or support channel for documents. Keep identity documents and authorisation codes out of public logs, URLs and analytics events.

Store enough evidence to connect the customer's answers to the operation, while applying your retention and access policy. API validation does not guarantee final registry approval; monitor the resulting operation and any additional review request before telling the customer the domain is registered.

• Register a domain using the current Domain Nexus v2 workflow
• Submit an inbound domain transfer with the Domain Nexus v2 API
• Register a .edu.ng domain with us: requirements and letter template
• Register a .gov.ng domain with us: approval steps and letter template
• Use the live Domain Nexus OpenAPI contract for your integration