Skip to main content

Request Format

All POST request bodies in the published OpenAPI use application/x-www-form-urlencoded. The published PHP pattern uses http_build_query($params).

Content Type​

  • Authentication headers: username and token
  • POST body: Content-Type: application/x-www-form-urlencoded
  • GET operations in the current specification use path parameters and no request body

Arrays​

Serialize arrays with PHP-style brackets:

nameservers[]=ns1.example.net
nameservers[]=ns2.example.net

The lookup schema uses the same pattern:

tldsToInclude[]=test.ly

Nested Objects​

Serialize nested registration/contact fields with bracket notation:

contacts[registrant][firstname]=John
contactdetails[Registrant][Contact_Name]=John Smith

Use an HTTP client that percent-encodes form values. Do not build the encoded body with string concatenation.

Unspecified Input Rules​

VALIDATION REQUIRED: The public contract does not define Unicode normalization beyond the examples, empty-value behavior, duplicate-key handling, field-name case sensitivity, hostname normalization, or whether omitted and empty optional fields are equivalent.