Reseller Hosting API OT&E Testing Guide

Creating a hosting account by hand after every order wastes time. And when plan selection, account creation, and order verification happen across separate screens, mistakes creep in. Domain Name API's Reseller Hosting REST API lets you pull hosting plans directly into your own sales system, create new hosting accounts programmatically, and verify that each account was actually created. You can test the whole flow in the OT&E sandbox before going live.

Who Is the Reseller Hosting API For?

• Hosting companies
• Domain resellers
• Web design and software agencies
• SaaS teams building customer dashboards
• IT consultants and MSPs
• Platforms managing hosting for multiple customer sites

If you're only hosting a single personal site, standard hosting is simpler. The Reseller Hosting API makes more sense for businesses selling hosting to multiple customers under their own brand.

What Does a Hosting API Integration Actually Get You?

Faster provisioning

Once payment clears, the hosting account can be created immediately — no manual ops step in between.

Fewer data-entry errors

Plan and order details move through a defined integration flow instead of manual re-entry, which cuts down on wrong-package selections and missing information.

One consistent customer experience

Domain and hosting services can live in the same sales or customer portal, so customers track order status from a single place instead of jumping between systems.

Controlled growth

The same integration flow scales as order volume grows — as long as you design it to respect API rate limits and retry safely.

Real integration testing

The OT&E sandbox lets you run through integration scenarios without touching production credentials or creating real customer orders.

Live API vs. OT&E Sandbox

Environment	Purpose	Swagger / Documentation
Live (Production)	Real, billable transactions	https://api.domainresellerapi.com/swagger/index.html
OT&E (Sandbox)	Integration and scenario testing	https://ote.domainresellerapi.com/swagger/index.html

For a broader overview of how live and OT&E access work together, see the Domain Name API Test Platform Guide.

Where Do You Get API Credentials?

The REST API doesn't use your portal login email and password. Credentials live in the Integration Information section of the reseller panel:

• Live environment: Reseller ID and API Key
• OT&E environment: OT&E Reseller ID and OT&E API Key

Reseller panel: https://dm.apiname.com/ Don't mix live and test credentials — a mismatch between environment and key returns an authorization error. If you rely on IP whitelisting, register the fixed outbound IP of the server making the calls in the panel.

Reseller Hosting API Endpoints

Method	Endpoint	Purpose
GET	/api/v1/hostings/plans	Lists available hosting plans.
POST	/api/v1/hostings/create	Creates a new hosting account under your reseller account.
GET	/api/v1/hostings	Lists hosting accounts tied to your reseller account.
GET	/api/v1/hostings/by-token	Looks up a single hosting account by token.

Required fields, data types, filters, pagination options, and response models can change; always confirm the current schema in Swagger rather than guessing field names or response shapes from the endpoint name.

The Hosting Order Lifecycle

1. Pull current hosting plans

Call GET /api/v1/hostings/plans to get available plans, and select the plan you'll use for the new account from that response. Confirm the exact names of plan fields — plan name, resource limits, pricing, and so on — in Swagger. Refresh plan data from the API periodically rather than hardcoding it permanently.

2. Verify the customer order

Before creating a hosting account, complete these checks:

• Has payment been confirmed?
• Has this order already been processed?
• Is the selected plan still available?
• Are the domain and customer details in the required format?
• Is there already an active hosting account tied to this order?

3. Create the hosting account

Call POST /api/v1/hostings/create with the required fields defined in Swagger. Store the account ID or token returned in a successful response and tie it to your own order record. Confirm in Swagger whether domain, plan, username, contact, or password fields are required, and their exact field names.

4. Verify the account with the token

Call GET /api/v1/hostings/by-token to look up the account individually. Only show the customer a 'Your hosting account is ready' message once both the creation response and the account status confirm success. A dropped network connection doesn't always mean the operation failed. Blindly retrying the same create request can produce a duplicate account.

5. List and sync accounts

Call GET /api/v1/hostings to pull the hosting accounts tied to your reseller account. Confirm whether filtering, pagination, and specific response fields are supported in Swagger. Use this call to refresh your ops dashboard, show status in a customer portal, run inventory checks, and reconcile your local records against the API's.

How a Real Customer Order Flows

1. The customer selects a hosting package.
2. The application matches that selection against the current /plans response.
3. A local order record is created once payment clears.
4. The /create request is tied to that local order reference.
5. The account ID or token from the API response is stored securely.
6. /by-token confirms the account was actually created.
7. The customer is notified only after that verification succeeds.
8. /hostings runs periodic synchronization.

Recommended OT&E Test Plan

1. Connect using your OT&E credentials.
2. Pull available test plans with /plans.
3. Send a /create request using a valid plan.
4. Store the returned account ID or token.
5. Verify the account with /by-token.
6. Confirm the account appears in the /hostings list.
7. Test invalid-plan and missing-field scenarios.
8. Test unauthorized access and IP-whitelist failures.
9. Confirm a timeout doesn't produce a second account.
10. Confirm the same order can't be processed twice.
11. Turn raw API errors into user-friendly messages.
12. Verify your logs contain no API keys, tokens, passwords, or personal data.

Once your OT&E tests pass, switch only the base URL and the matching environment credentials to move to production.

Building for Security and Scale

Don't hardcode plan data

Manage plan IDs, resource details, and pricing through the API's current structure. Sync regularly so your integration keeps working when the plan catalog changes.

Prevent duplicate accounts

Generate a unique local reference per order. If a create call times out, check the outcome of the previous attempt before opening a new account.

Protect sensitive data

API keys, customer information, hosting passwords, and tokens should only ever be handled server-side. Mask sensitive fields in your logs.

Show verified status, not just a 200 OK

Don't rely solely on a successful HTTP response. Confirm the account is actually in the expected state before sending the customer a clear status message.

Respect rate limits

Queue your API requests. Apply controlled backoff on 429 Too Many Requests, and check current API documentation for the exact limit.

Common API Issues

Issue	First Thing to Check
401 Unauthorized	Reseller ID, API Key, environment match, and IP whitelist
403 Forbidden	Account permissions, product access, and environment in use
400 Bad Request	Required fields and data formats per Swagger
404 Not Found	Endpoint, token, or the resource being queried
429 Too Many Requests	Request rate — add client-side queuing and backoff
Timeout or 5xx	Check whether the operation already succeeded before creating a new account

Related Guides

• Domain Name API Test Platform Guide
• SSL Reseller API & OT&E Sandbox Guide
• Reseller Hosting Program
• Reseller panel

Frequently Asked Questions

Does OT&E create a real hosting account?

No. OT&E is strictly for testing — never treat sandbox resources as production output. Live operations require the production base URL and production credentials.

Which endpoint should I call first?

Start with GET /api/v1/hostings/plans to see valid plans, then create the account using the selected plan.

Where can I see the request fields?

The current required fields, data types, and sample models are documented on the production or OT&E Swagger page.

Why should I query the account after create?

Confirming the account's actual status reduces the risk of a false success message and prevents duplicate accounts.

I'm using WHMCS or WiseCP — do I still need the REST API?

Check current module documentation to see whether the module you're using already supports reseller hosting operations. If it covers your needs, you may not need to build against the REST API directly.

Are live and OT&E keys the same?

No. Each environment requires its own Reseller ID and API Key, both shown in the panel.

The Bottom Line

A solid reseller hosting integration is never just a single create call. Selecting the current plan, verifying the result with the token, protecting sensitive data, and avoiding duplicate operations on ambiguous network errors are all part of the same flow. Complete those checks in OT&E first, and you'll go live with meaningfully less operational risk.