A domain search interface often starts with a fixed list of familiar endings. That list becomes misleading as soon as the connected registrar supports more extensions, changes its catalogue or cannot confirm one result. IaGenify SDK 0.3.3 adds a direct way to discover the extensions currently offered through the account's registrar integration.
Ask the API what is supported today
The new `api.domains.tlds()` method reads the available extension catalogue from the service. An application can use that response to render its own filter, directory or suggestion list, instead of shipping a hard-coded set that drifts from the provider's actual coverage.
const extensions = await api.domains.tlds();
const results = await api.domains.search("studio", {
tlds: ["com", "design", "studio"],
});Search one extension or compare several
The existing search resource accepts a name and an optional list of extensions. Developers can query a full domain when a person already knows the exact address, or search a short name across a chosen set and compare the results. The catalogue and the search operation can therefore power a compact input or a richer comparison table.
Availability is not a reservation
A search result is a point-in-time availability response. It does not reserve the name, complete registration or guarantee the same result later. The SDK keeps that boundary clear: it exposes discovery and search, while registration and payment remain an explicit flow in the IaGenify product.
That distinction matters for interfaces. Unknown availability should remain unknown rather than being presented as a green result, and a live search response should not be worded as a purchase confirmation. The application can show the provider result while leaving the actual order to a separately confirmed step.
Let the registrar's current catalogue inform the interface; let the order flow make the purchase.
With 0.3.3, domain-aware applications can build their extension choices from the same service they query. It is a small SDK method with a practical effect: fewer stale assumptions in the UI and a clearer separation between looking up a name and registering it.
Frequently asked questions
Does `api.domains.tlds()` return a list embedded in the SDK?
No. It reads the extension catalogue from the IaGenify API connected to the registrar.
Can I search just one full domain?
Yes. `api.domains.search()` accepts a complete domain name, or a base name with a list of extensions.
Does a positive result reserve the domain?
No. Search reports availability at that time; it does not reserve or register the name.
Does this method make a purchase?
No. The SDK feature covers catalogue discovery and search. Registration and payment require a separate explicit product flow.