Before you start you need three things from us: the module package BBReseller-client.zip, your reseller username, and your API key. The key is shown once when issued — if it is lost we issue a new one and the old key stops working immediately.

1. Install the module

Unpack the archive into your WHMCS root. It contains a single directory, modules/servers/BBReseller, and touches nothing else. There is nothing to activate: WHMCS discovers provisioning modules from the filesystem.

2. Add the server

Go to System Settings → Products/Services → Servers and choose Add New Server:

• Name — anything, for example BIGBANG
• Hostname — the full endpoint URL, not just a domain: https://portal.its.ae/modules/addons/BBReseller/api/index.php
• Type — BIGBANG Reseller
• Username — your reseller username
• Access Hash — your API key

Leave Secure, port, nameservers and the status-address fields alone. They do not apply. Most WHMCS server modules want a bare hostname; this one wants the whole URL, because it speaks HTTP to a single script rather than to a control panel on a port.

3. Test the connection

Press Test Connection. A pass means three separate things lined up: the endpoint is reachable, your key is valid, and your server clock agrees with ours.

The reply also carries a readiness block. All four of its values must be positive or true. If any is not, the connection is still valid but orders will be refused — that is on our side, so send us the reply.

4. Map a product

Create or edit a product, open the Module Settings tab and set the module to BIGBANG Reseller, the server group to the server you just added, and:

• BIGBANG plan code — the code from your catalogue. See Plan codes, pricing and billing.
• Order on cycle — which cycle we bill you on. Independent of what you bill your customer.

5. Place a test order

Order the product for a test client and let it provision. On success the module records our service id against your local service, and every later operation uses it. You can see it on the module tab of the service, on the BIGBANG service line, together with the live status read from our side.

Then exercise the rest: suspend, unsuspend, change package, terminate. All four should complete with no manual step at either end.

Do not import services by hand. A service created outside the module has no BIGBANG service id recorded, and suspend, upgrade and terminate will refuse to run on it rather than risk acting on the wrong account. Contact us and we will map it for you.