GET /accounts/{account_id}/registrar/extensions

Returns metadata and JSON Schema documents describing the expected input structure for registration operations on each supported extension (TLD).

This endpoint uses cursor-based pagination. Results are ordered by extension name by default. To fetch the next page, pass the cursor value from the result_info object in the response as the cursor query parameter in your next request. An empty cursor string indicates there are no more pages.

Supports HTTP conditional GET via ETag. Include the ETag value from a previous response in an If-None-Match header to receive a 304 Not Modified when the data has not changed.

Servers

Path parameters

Name Type Required Description
account_id String Yes

Query parameters

Name Type Required Description
name String No

Filter extensions by exact name match. For example, name=com returns only the com extension.

direction String No

Sort direction for results. Defaults to ascending order.

Valid values:

  • "desc"
  • "asc"

Default value: "asc"

per_page Integer No

Number of items to return per page.

Default value: 20

cursor String No

Opaque token from a previous response's result_info.cursor. Pass this value to fetch the next page of results. Omit (or pass an empty string) for the first page.

sort_by String No

Column to sort results by. Defaults to name when omitted.

Valid values:

  • "name"
  • "created_at"
  • "updated_at"

Default value: "name"

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.