Skip to content

Which Integration Method Should I Choose?

There is no single “right” way to connect to CentralNic Reseller — there is the right way for your business. A web host automating a few hundred domains, a registrar running EPP across several registries, and a developer building a custom platform all have different needs, and we give each of them a path that fits. This page helps you pick yours before you write any code.

The good news: you are not locked in. Many partners start in the Control Panel, add WHMCS or an API integration as they grow, and mix methods over time. Choose what gets you live soonest today; you can always deepen the integration later.

Find the description that sounds most like you and follow the recommendation. More than one may fit — that is fine, and the comparison table below will help you decide between them.

”I Want To Be Live as Fast as Possible”

Section titled “”I Want To Be Live as Fast as Possible””

Start in the Control Panel. It is your white-label, web-based command centre — no code, no servers, nothing to install. You can register, transfer, renew and manage domains, contacts and DNS by hand from day one, and it is the fastest way to make your first real registration.

Every partner should know the Control Panel even if they later automate, because it is where you configure defaults, check pricing and verify that automation did what you expected. See Your First Day for the full walkthrough.

Choose the WHMCS module. If you already bill and provision hosting through WHMCS, our module plugs domain registration straight into the platform your customers and staff already use — no separate system to build or maintain. It is the shortest path to selling domains alongside hosting under your own brand.

You will find the module and its documentation on the WHMCS page, and the everyday flows in WHMCS integration.

”I Already Use WHMCS for Something Else”

Section titled “”I Already Use WHMCS for Something Else””

Same recommendation: the WHMCS module. There is no reason to build a custom integration when the platform you run can talk to us directly. Install the module, add your credentials, and your existing WHMCS instance becomes your domain storefront. Start at the WHMCS page.

”I’m a Developer Building a Custom Platform”

Section titled “”I’m a Developer Building a Custom Platform””

You want the API — and, if we publish one for your language, an SDK on top of it. Our HTTPS API is a straightforward request/response interface: you send a command with parameters and get a structured response back, over HTTPS, XML-RPC, SOAP or the high-performance MREG gateway. It gives you full control to build exactly the product you want.

If you would rather not hand-roll HTTP calls, our SDKs wrap the same API idiomatically. See SDK Quick Starts for the available languages, and Connecting for the five gateway options and how authentication works.

For most developers today, the HTTPS API (optionally via an SDK) is the proven, fully documented path. See the REST API Integration Guide for where REST fits once it is generally available.

”I’m a Registrar, or I Already Run EPP Elsewhere”

Section titled “”I’m a Registrar, or I Already Run EPP Elsewhere””

Choose EPP. If your team already speaks the Extensible Provisioning Protocol — the registry-industry standard — you can reuse that expertise and tooling to connect to CentralNic Reseller with minimal relearning. EPP is the natural fit for established registrars and anyone standardising on one protocol across multiple providers.

Our EPP server supports the full domain, contact, host, transfer and poll command set. See the EPP Command Reference for the complete list and the EPP Integration Guide to get connected.

Use this table to weigh the trade-offs. “Time-to-first-registration” assumes your account is already funded and secured.

MethodSetup effortTechnical prerequisitesControl & flexibilityTypical use caseTime-to-first-registration
Control PanelNone — log in and goA web browserManual operations; no automationGetting started, testing, occasional manual tasksMinutes
WHMCS moduleLowA running WHMCS installationHigh for billing/provisioning; bounded by WHMCSWeb hosts and anyone already on WHMCSSame day
SDKLow–mediumCoding in a supported languageFull API access, idiomatic wrapperDevelopers who want the API without hand-rolling HTTPDays
API (HTTPS / XML-RPC / SOAP / MREG)MediumAbility to send authenticated HTTP requestsFull control over every commandCustom platforms and bespoke automationDays
EPPMedium–highEPP client and protocol experienceFull registry-standard controlRegistrars and teams already running EPPDays

You have picked a direction — now let’s build. Open the guide that matches your choice: