31 Aug 10 .NET API Kit and Integration Guide

Follow the instructions below to begin integration with the API using .NET.

Make sure you have read the General API Integration Instructions first. If you have already integrated the .NET API Kit at your end, read the Change Log first to know what has changed since.

Reference:

General API Integration Instructions >>
Change Log >>

Step 1. Download the API Kit
Click the link below to download the relevant API kits (updated on 6th March, 2008).

Option 1 – Setup Application

NET_Core_Setup_v3_10.zip
NET_Domains_Setup_v3_10.zip
NET_Hosting_Setup_v3_10.zip
NET_OtherProducts_Setup_v3_10.zip

Option 2 – Compressed ZIP File

NET_CoreExamples_v3_10.zip
NET_DomainsExamples_v3_10.zip
NET_HostingExamples_v3_10.zip
NET_OtherProductsExamples_v3_10.zip

Step 2. Download the API Documentation
The complete documentation of all classes and methods available in the API can be found in the Docs below. The Docs below are javadocs, but the function names and explanations remain the same for all the platforms and the documentation is self explanatory. We recommend you download the docs and read through them completely once before you integrate your application (updated on 6th March, 2008).

Core_Docs_v3_10.zip
Domains_Docs_v3_10.zip (updated on 1st April, 2008)
Hosting_Docs_v3_10.zip
OtherProducts_Docs_v3_10.zip

Step 3. Install the API Kit
There are two ways by which you may install the API Kit on your computer:

Option 1 – Setup Application
We recommend that you download, unzip and run the setup file. First, however, please be sure that you have administrator privileges to install applications on the computer. If you’re hosting your website with a third-party provider and do not have the rights to install applications, then you will not be able to use the setup application to install the kit. Therefore, you may manually install and use the required API files from our compressed ZIP file option (Refer to Option 2 below).

The setup application will perform the following tasks:

A .NET dll containing the kit, and the relevant documentation, will be placed inside your “Program Files” folder; by default, the path would be “C:Program Files”. Therefore, you should be able to find the DLL and the documentation corresponding to your kit. Please ensure that you have the .NET runtime installed before you attempt to use the API kit.

Relevant shortcuts will be placed in your start menu.

If you have Microsoft Internet Information Server version 5.0 or greater (IIS) installed, the setup file will create a virtual directory named as OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples in your “Default Web Site”. The setup file allows you to give the virtual directory any name of your choice. This virtual directory contains a Visual Studio .NET project called OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples, which illustrates every function provided in the OrderBox API. You may run the examples by either by:

Opening it in Visual Studio.Net and pressing the F5 key, or
Visiting the url http://localhost/examples/ in your browser.

Option 2 – Compressed ZIP File
Download the zip file and extract the files to any temporary folder. The temporary folder will now contain the following subfolders:

OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples – The folder contains the example files to illustrate every method in the kit.

bin – This folder contains the actual kit DLL file. This is a .NET DLL, and requires the .NET runtime to be pre-installed, for use.

Installing the examples on your own computer:

Create the Examples folder (OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples) inside the root of any website configured in IIS, on your computer. IIS contains a default website called “Default Web Site”, having it’s root folder set to “c:Inetpubwwwroot”. If you have a default installation of IIS, you would create a subfolder called “examples” inside that root folder. Please note that you may name the examples directory as you please, you are not restricted to the name OrderBoxCoreExamples , OrderBoxDomainsExamples, OrderBoxHostingExamples, OrderBoxOtherProductsExamples.

Open the IIS management console by navigating to “Start > Programs > Administrative Tools > Internet Information Services”

Now, we need to create an “Application Root” for the examples folder. This can be accomplished by opening the properties window for that directory and clicking on the “Create” button.

If you successfully completed the above steps, you may open your browser and point it to http://localhost/examples (if you gave your examples folder some other name, replace the last word of the URL with that name).

Step 4. Run the examples
Please note first that the ASP.NET examples are provided solely to help illustrate usage of the ASP.NET Kit. You may use the example files directly, or simply use them as a reference project while developing your application to interface with the OrderBox API.

IMPORTANT

IIS 5.0 and the .NET runtime MUST be installed on your machine, BEFORE you run the kit setup file.

After you’ve installed the ASP.NET examples, open your browser, and point it to “http://localhost/your-examples-folder” (you may use the name given to the examples folder to replace “examples” in the preceding url). This shall open the ASP.NET examples webpage, which is divided into three frames:

The frame on the top allows you to mention the Service URL, your Reseller Username, your Password, ParentID, Language Preference, Role, Debug Mode to make API calls independent of the credentials provided in the APIConstants.vb file. This frame also provides you a checkbox to enable/disable the credentials of this frame. That is, if the checkbox is not selected the APIConstants.vb file credentials will be used to make the API call.
The lower left frame contains a list of links to pages that illustrate the use of each method in the API. When you click a link, it’s corresponding page is displayed in the right hand side frame. You may test the functions by putting in the call parameters in the page.

Step 5. Understanding Errors
Make sure you have read the General API Integration Instructions to obtain links to the error format and possible error documents. Reference: General API Integration Instructions >>

Step 6. Writing your own code
The API classes exist within the namespace OrderBoxCoreLib , OrderBoxDomainsLib, OrderBoxHostingLib, OrderBoxOtherProductsLib. The class named “Properties”, contains static variables useful for debugging, and changing the SOAP End Point.

The following are valid end points for the OrderBox Demo Server:

HTTP DEMO SERVICE URL: “http://api.onlyfordemo.net/anacreon/servlet/APIv3-XML”
HTTPS DEMO SERVICE URL: “https://api.onlyfordemo.net/anacreon/servlet/APIv3-XML”

The following are valid end points for the OrderBox Live Server:

HTTP LIVE SERVICE URL: “http://www.myorderbox.com/anacreon/servlet/APIv3-XML”
HTTPS LIVE SERVICE URL: “https://www.myorderbox.com/anacreon/servlet/APIv3-XML”

Example: To test the examples, you must first create an account on the Demo server. To use the Customer webservices of the OrderBox API, instantiate the customer object as demonstrated below. If at any time the SOAP end point must be changed to some other url, you may simply put the new SOAP end point into this variable.

Properties.Url = “http://soap-end-point”;

The following code instantiates the Customer object. You may now use it’s methods to call various OrderBox API functions. These are SOAP calls, that will be made to the SOAP End Point specified by the Propeties.Url variable.

Customer oCustomer = new Customer ();

To illustrate the use of this object, we shall take the example of a method called getCustomerId. Examine the code snippet below. It uses an object of the Customer class to request the id of a specified username.

int result = 0;

// First we make sure that our SOAP End Point is pointing to the correct resource.
Properties.Url = “http://api.onlyfordemo.net/anacreon/servlet/APIv3-XML“;

// The examples use a class called Constants, containing static properties that hold your credentials. You may set these properties once, and later in the file simply pass them to the method calls as required. The values set below are simply examples, and must be replaced with your own credentials.
Constants.Username = “username@domain.com”; // Your username goes here.
Constants.Password = “your-password”; // Your password goes here.
Constants.Role = “reseller”; // Your role goes here.
Constants.LangPref = “en”; // Your language preference goes here.
Constants.ParentID = 1; // Your parent id goes here.

// Since we wish to view the soap request and response …
Properties.Debug = true;

// Next we instantiate an object of the Customer class.
Customer oCustomer = new Customer ();

// We then use this customer object to request the id for a specified username.
result = oCustomer.getCustomerId (ApiConstants.SERVICE_USERNAME,
ApiConstants.SERVICE_PASSWORD,
ApiConstants.SERVICE_ROLE,
ApiConstants.SERVICE_LANGPREF,
ApiConstants.SERVICE_PARENTID,
“username”);

// Now we display the soap request.
Console.WriteLine (Properties.getLastRequest); Console.WriteLine ();

// Then we display the soap response.
Console.WriteLine (Properties.getLastResponse); Console.WriteLine ();

// Lastly we display the result.
Console.WriteLine (result);

The above code accepts authentication details and a username, and returns an integer value, which is the id corresponding to the username passed. The last parameter of the getCustomerId method is the username for which we requested an id. This id was returned into the integer variable result.

Please note the first five parameters of this method call. They consist of the username, password, role, language preference, and parent id respectively, of the individual calling the method. For the examples, you may make a demo account on the demo server, and pass the username, password, role, language preference and parent id from your demo account to this method call. These are the first five parameters that are passed to every API call that is undertaken. Please make sure that you pass accurate details for these parameters. If you do not, your method call will be unsuccessful.

IMPORTANT

In registering/managing any domain name on the demo server always use ns1.onlyfordemo.net and ns2.onlyfordemo.net as your nameservers. ANY OTHER Nameserver will result in an INVALID NAMESERVER error.

Step 7. Change the information to Live information when you are ready
When you have got the examples working correctly, you may set the value of Properties.Url to one of the live URL’s, and pass your own authentication details when making API calls.

Tags: 10 Zip, administrator, Administrator Privileges, Api, Api Documentation, Api Guide, Api Kit, ASP.NET, Computer Option, Demo Server, Docs, Explanations, http, installation of IIS, Integration Guide, Internet Information, Internet Information Services, Javadocs, Names, Net Hosting, Option 1, Party Provider, Platforms, Properties, Reference, Setup Application, Step 1, Step 2, Third Party, Two Ways, Visual Studio.Net, www.myorderbox.com/anacreon/servlet/APIv3-XML, Xml, Zip File, Zip Net

Filed in .NET API Kit with 0 Comments

30 Aug 10 Data Validation of Parameters passed in an API Method Call

This document describes the Validation routines which you need to build in for the various parameters which you send to the API call. Failure to validate these fields on your side may result in an undecipherable error from the Server.

General Guidelines
Any fields which are optional will require either NULL or “” to be passed to them if they are of type String, or “0″ passed to them if they are of type Numeric. The type of a parameter can be checked in the documentation supplied alongwith the kit. So for instance if you choose NOT to pass a FAX Number you will have to pass “NULL” or “” for that parameter.

Specific Parameters and their Validation

username:

The Username MUST NOT be null
The Username MUST be an E-Mail address of the type something@somevalidhostname
Valid Characters Before the @ sign: ‘a’ To ‘z’, ‘A’ To ‘Z’, ’0′ To ’9′, ‘-’, ‘_’, ‘.’
Valid Characters After the @ sign: ‘a’ To ‘z’, ‘A’ To ‘Z’, ’0′ To ’9′, ‘-’, ‘.’
The first and last character after the @ sign cannot be “-” or “.”
Maximum length of Username: 64 characters.

role:

Role must always be reseller

name:

Name MUST NOT be null
Maximum length: 64 characters

company:

Company MUST NOT be null
Maximum length: 255 characters
Company Name can not start with a dot “.”

IMPORTANT

While creating a Contact, each Name and Company Name combination should be unique.

address:

Address is divided into 3 fields
address1 MUST NOT be null
address2 and address3 MAY be NULL
Maximum length of address1, address2 and address3 each: 64 characters

langPref:

langPref MUST NOT be null
It MUST be a two-letter ISO Code representing a language e.g. “en” for English.
Allowed Codes are
- “en” for English
- “ar” for Arabic
- “by” for Belarussian
- “bg” for Bulgarian
- “nl” for Dutch
- “ru” for Russian
- “tr” for Turkish
- “es” for Spanish
- “fi” for Finnish
- “de” for German
- “iw” for Hebrew
- “pt” for Portuguese

password:

password MUST NOT be null
Minimum length: 6 characters

city:

city MUST NOT be null

country:

country MUST NOT be null
country MUST be the 2 letter ISO Code of that particular Country e.g. “US” for United States of America

zip:

zip MUST NOT be null
Maximum Length of Zip: 10 characters

Allowed Characters:
- First Character can be ’0′ To ’9′, ‘A’ To ‘Z’, ‘a’ To ‘z’
- Rest Characters can be ’0′ To ’9′, ‘A’ To ‘Z’, ‘a’ To ‘z’ and ‘-’

telnocc:

telnocc MUST NOT be null
valid characters: 0-9 (all numerals)
Minimum Length: 1 character
Maximum length: 3 characters

telno:

telno MUST NOT be null
valid characters: 0-9 (all numerals)
Minimum Length: 4 character
Maximum length: 12 characters

alttelnocc (optional):

alttelnocc MAY be null
If present, is validated exactly as telnocc

alttelno (optional):

alttelno MAY be null
If present, is validated exactly as telno

faxnocc (optional):

faxnocc MAY be null
If present, is validated exactly as telnocc

faxtelno (optional):

faxtelno MAY be null
If present, is validated exactly as telno

Tags: Api, Arabic, Bg, C Ompany, Cou, Data Validation, E Mail Address, English Ar, Failure, Fax Number, Fi, Hebrew, Iw, Letter Iso Code, Maximum Length, Parameters, Portuguese, Reseller Name, Ru, Type String, United States Of America, Validation Routines

Filed in Reseller API Guide with 0 Comments

29 Aug 10 Emulating API Calls

IMPORTANT

Ensure that you have read the following documents before Emulating any API call:

You may emulate any API call without actually installing any of the API Kits, on our server itself by following the below mentioned process:

1. Login into your Reseller Control Panel from http://manage.gossimer.biz/reseller

2. Click on the relevant Kit mentioned within Settings -> API -> Emulate API Calls

3. Fill in the relevant details in the top-frame by referring to the below mentioned link -

Read This FIRST – General API Integration Instructions

Note – If you wish to view the XML Sent and Received at the client-side, choose to print the XML Sent/Received. This will enable you to view the simulation of the XML sent by your server to our server and our server’s response thereof.

4. Select the API Method that you chose to Debug previously in the left frame and enter the relevant details in the right frame and emulate the API Call.

5. If you chose to print the XML Sent/Received previously, you will be able to view it in the right frame (after you make an API call). You may wish to save this for debugging later on.

Tags: Api, Api Examples, Data Validation, Description Data, Format Description, Integration, Left Frame, Parameters, Relevant Details, Reseller Control Panel, Server Error, Simulation, Top Frame, Xml

Filed in Emulate and Debug your API Calls with 0 Comments

29 Aug 10 General Finance Setting

The Reseller Admin Control Panel allows you to customize various finance parameters as follows:

1. Login into your Reseller Admin CP at http://manage.gossimer.biz/reseller

2. Click on Settings -> Finance & Billing -> General Settings.

3. Modify all the information in the form to suit your needs. The various fields in the form are explained below.

Selling Currency – This field represents the currency in which you wish to sell your Products to your Customers and Sub-Resellers.
Accounting Currency - This field is important for you if you use the Online Invoicing and Billing system we provide. If your Selling currency above is different from the currency in which you maintain your books of accounts, you may change your accounting currency.
Note that, if you choose a different Accounting Currency, all Invoices, Receipts, Debit Notes and Credit Notes will contain two currency columns, containing both the Selling currency and the Accounting Currency. This field represents the local currency of your country. So in India, this would be the Indian Rupee, if you are from Europe choose the Euro. If you made the wrong Currency choice at setup time then it is VERY IMPORTANT that you immediately contact us, before you start selling any Products. A wrong Currency could have several implications to your billing section.
Currency Conversion Rate – This represents the Conversion rate between your Selling Currency and your Accounting Currency. If you have chosen a different Accounting currency from your Selling Currency, the system will also automatically calculate your Forex Gain/Loss per transaction for you. Alternatively, you can keep modifying this value on a regular basis to represent the accurate conversion rate between your Selling and Accounting currencies. This needs to be selected by clicking on the check box, listed above the Currency Conversion Rate.
Funds Threshold Level – Set this to a comfortable amount such that the the System notifies you when your Funds in your Reseller Advance A/c drop below this level. For instance, if you set this to 100 in your Selling Currency, then each time your funds drop below 100, you will get an e-mail to replenish your funds.
Minimum Transaction Amount – This is a very useful feature which allows you to specify a minimum amount below which your Customers and Sub-Resellers will not be able to pay/add funds using any online payment option. This is useful when you do not wish to allow your Customers and Sub-Resellers to transact small amounts by online methods.Minimum Transaction Amount for making Payments – By setting a value greater than zero in this field, you can restrict your Customers from paying for Invoices/Debit Notes of lesser amounts.
Minimum Transaction Amount for Adding Funds – By setting a value greater than zero in this field, you can restrict your Customers and Sub-Resellers from adding funds into the system of lesser amounts.
Turn on the generation of Risk Assessment Reports – By default this feature is turned on, as measure to mitigate fraud when receiving funds from your Sub-Resellers and Customers via any of the following Payment Gateways -
- Authorize.Net Credit Card Gateway
- VeriSign Payflow Pro Credit Card Gateway
- Planet Payment Credit Card Gateway
- Electronic Clearing House Credit Card Gateway
- PayPal Direct Payment API Gateway

- Apart from various online payment gateways that you can setup to receive funds, you may also choose to receive payment via offline methods. Should you choose to do so, you would need display various methods by which your Customers and Sub-resellers can make offline payments, such as your Postal Address, instructions for mailing a Cheque or Wire Transfer information. All such information can be submitted here.
You would find 2 text-boxes where you can submit the Payment Page content (in HTML) for your Customers and and Sub-resellers. Use the preview buttons to see what your submitted content would appear like when your Customers/Sub-resellers view it before paying or adding funds.

IMPORTANT

The SuperSite contains information about the various Payment options you offer to your Customers and also presents these options at the time of purchasing Products and Services. This data is downloaded to your SuperSite from your Control Panel and cached (stored) on the SuperSite Server. Hence, you would need to refresh the cache of your SuperSite once you have completed the above process. You can accomplish this from within your Control Panel itself by clicking on Tools -> Reload SuperSite & PartnerSite Cache -> SuperSite Payment Preferences. Click here to know what is SuperSite >>

Tags: Accounting, Accurate Conversion, Admin Control Panel, Amp, Api, Authorize.Net, Billing Section, Billing System, Currencies, Currency Conversion Rate, Currency Note, Europe, Finance, finance parameters, General Finance, HTML, India, Indian Rupee, Invoices, Online Billing, Online Invoicing, online methods, online payment gateways, online payment option, Parameters, Receipts, Resellers, Setup Time, Threshold Level

Filed in Read this First: Understanding the Billing System with 0 Comments

25 Aug 10 About Authorize.Net

Authorize.Net (http://www.authorize.net), a service of Lightbridge, is the preferred global payment-processing service for e-commerce, enabling merchants to process secure transactions in real time, 24 hours a day. Authorize.Net Payment Solutions process credit cards and electronic checks.

Gossimer has integrated with Authorize.Net API via Advanced Integration Method (AIM), that uses secure sockets layer (SSL) digital certificate technology to connect securely and directly to the Payment Gateway-achieving the highest security for the Internet connection between a merchant and the gateway.

Some of the useful links are listed below -

Find a Authorize.Net Reseller: http://www.authorizenet.com/reseller/directory.php.

Signup for Authorize.Net Merchant Account: http://www.authorizenet.com/solutions/gettingstarted.php

Support Center: http://www.authorizenet.com/support/

Tags: Aim, Api, Authorize.Net, Credit Cards, Credit Checks, Digital Certificate Technology, e - commerce, Electronic Checks, Global Payment, Integration Method, Internet Connection, Lightbridge, Merchant Account, Merchants, Payment Gateway, Payment Processing, Payment Solutions, Php, Php Login, preferred global payment-processing service, Processing Service, Real Time, Reseller Directory, Secure Sockets Layer, Secure Transactions, SSL, Support Center

Filed in Integration with Authorize.Net's Credit Card Gateway with 0 Comments

24 Aug 10 Change Log

Changes in version 3.10

Java Docs updated

Changes related to classes and methods:

New Classes and Methods

Domains Kit
New Class Name	New Method
ThirdLevelDotUk	String invoiceOption
ThirdLevelDotUk	String existingEndTime

New Parameters introduced in Existing Methods

Other Products Kit
Class Name	Method Name	New Parameters
EngageOrder	renew	String invoiceOption
EngageOrder	renew	String existingEndTime

Deprecated Parameters in Methods

Domains Kit
Class Name	Method Name	Deprecated Parameters
ZoneOrder	add	“No Of Records” in DomainHash

Deprecated Methods

Domains Kit
Class Name	Deprecated Method	Suggested Class	Suggested Method
DomContact	addDefaultContact	DomContact	addDefaultContacts
DomContact	add	DomContact	addContact
DomContact	list	DomContact	listByType
DomContactExt	isValidRegistrantContact	DomContactExt	isValidContact
DomOrder	transferDomain	DomOrder	addTransferDomain
DomOrder	add	DomOrder	registerDomain
ZoneOrder	mod	ZoneOrder	Functionality not required anymore
DotEu	tradeDomain	DotEu	trade
DotEu	transferDomain	DotEu	transfer
DotEu	add	DomOrder	registerDomain
Core Kit
Class Name	Deprecated Method	Suggested Class	Suggested Method
Customer	addCustomer	Customer	signUp
Customer	modDetails	Customer	mod
Reseller	addReseller	Reseller	signUp
Reseller	modDetails	Reseller	mod
Reseller	addResellerWithStateId	Reseller	Functionality not required anymore
OrderSetup	getResellerSlabPercentageForProducts	OrderSetup	Functionality not required anymore
OrderSetup	getCustomerSlabPercentage	OrderSetup	Functionality not required anymore

Changes in version 3.9

Java Docs updated
Changes related to classes and methods:

The following method in the Domains Kit is deprecated and its use should be discontinued -

Deprecated method Class New method to be used

isValidRegistrantContact DomContactExt isValidContact

Changes in version 3.8

Java Docs updated
Changes related to classes and methods:
1. The following changes have been introduced under the DotEu class within the Domains Kit -
  - New methods
    - trade
    - transfer
  - Deprecated methods
    - tradeDomain
    - transferDomain
2. The following new methods have been introduced under DigitalCertificateOrder class within the Other Products Kit -
  - enrollForThawteCertificate
  - reissue
  - renew
  - checkDigitalCertificateStatus
  - del
  - cancelDigicertOrder
  - changeDigicertPassword
  - addAdditionalLicenses
  - getDetails
  - getDetailsByDomain
  - getOrderIdByDomain

Changes in version 3.7

Java Docs updated

Changes related to classes and methods:

Some old parameters have been removed and new parameters introduced in their place under the following methods -

LinuxHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

WindowsHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

MailHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*
mod	Hashtable orderHash	String packagekey^, int additionalMailBoxes^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*
getModPricing	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*

SiteBuilder Class
Method	Old Parameter	New Parameters
mod	Hashtable orderParams	String packageKey^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*

NOTE:

^* packageKey will be the Identifier Key of the Plan (plan1, plan2, plan3, plan4) for which the Order needs to be added/modified.

^# ssl will be true or false depending whether the user wants Dedicated IP / SSL for the Order placed.

^## excessBandwidth is the Bandwidth which the user wants over and above the Bandwidth of the Order’s current plan.

^** additionalMailBoxes is the number of additional mail boxes over and above the existing ones in blocks of 100 accounts.

The following classes and their methods are removed:
- LinuxHostingPlanOnlyOrder
- WindowsHostingPlanOnlyOrder
- MailHostingPlanOnlyOrder
The SiteBuilderLite class has been renamed to SiteBuilder.
Two new methods, mod and signUp, have been introduced under the Reseller and Customer classes.
The return type of the ListByType method of DomContact class in the Domains Kit has been changed to Hashtable from Vector.

Changes in version 3.6

Java Docs updated

Changes related to classes and methods:

New methods have been added in the Core Kit under the following class:
getProductMetadata – Product class
New methods have been added in the Domains Kit under the following classes:
getDefaultContactId – DomContactExt class
listByType – DomContact class
addTransferDomain – DomOrder class
changePrivacyProtectionStatus – DomOrder class
registerDomain – DomOrder class
Changes to the DomOrder class in Domains Kit:

The following methods in the Domains Kit are deprecated and their use should be discontinued:

Deprecated method	Class	New method to be used

add	DomContact	addContact
addDefaultContact	DomContact	addDefaultContacts
list	DomContact	listByType
add	DomOrder	registerDomain
transferDomain	DomOrder	addTransferDomain
transferDomainWithoutValidation	DomOrder	addTransferDomain
addTransferDomainWithoutvalidation	DomOrder	addTransferDomain
add	DotEu	registerDomain in DomOrder class

IMPORTANT

While these methods are currently available, they are no longer supported and may be discontinued in the near future.

New methods have been added in the Hosting Kit under the following class:
getHostingMetaData – WebHostingOrderData class
Changes to classes in the Hosting Kit:
The invoiceOption parameter has been added to the add method of MailHostingPlanOnlyOrder, WindowsHostingPlanOnlyOrder and LinuxHostingPlanOnlyOrder classes

Changes in version 3.5

Java Docs updated
Changes related to classes and functions:
- New functions have been added in the Core Kit under the following classes:
  getList – Country class
  getStateListForCountry – Country class
  getDetails – Order class
  addResellerWithStateId – Reseller class
- An extra option called Supersite is added in the getDetails function of the Reseller class in the Core Kit.
- A new class LegalAgreement is added with the following methods under the Core Kit:
  getRegistrantAgreement
  getProductCategory
  getAgreement
  getAllAgreements
- A new function has been added in the Domains Kit under the following class:
  addCoopContact – DotCoopContact class
- The following functions in the DomOrder class in the Domains Kit are changed to show the Invoice options also:
  validateDomainRegistrationParams
  validateDomainTransferParams
  addWithoutValidation

Changes in version 3.4

COM visible interfaces have been added for those who use ASP or VB, so that they are also able to use our DLLs.
Java Docs Updated
New Classes introduced in all Kits:

Core Kit

TaxService
getApplicableTaxes
getHashedTaxRules
Domains Kit

DotEu
    getEUCountryList
    tradeDomain
    transferDomain
    add
    isEUCountry

DotEuContact
    mod
    add
    addEuDefaultContact

DomOrder
    validateDomainRegistrationParams
    validateDomainTransferParams
    addTransferDomainWithoutvalidation
    addWithoutValidation
Hosting Kit

WindowsHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

LinuxHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

MailHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount
    list

MailHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

WindowsHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

LinuxHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap
Other Products Kit

DigitalCertificateOrder
    add
    getCertPrice

SiteBuilderSetup
    getPricingKeyPricingParamMap

EngageSetup
    getPricingKeyPricingParamMap

Changes in version 3.3

All the DLLs have been modified to allow partially trusted callers to use it.
3 new functions have been added in the Core Kit under the following classes:

authenticateCustomerId – Customer class
login – Customer class
getOrderIdByDomainAndProductCategory – Order class
Bug Fix – A minor Java Script problem was causing the frame links in the examples to not work in some browsers like Mozilla and Opera.

Changes in version 3.2

New methods added viz. Order.removeCustomerLock, Order.getLockList
The testing form provided now has a third frame which accepts the standard parameters passed in every call. If you set these parameters from the form, you can make test calls independent of the settings in the properties/constants file.
We’ve added ‘Strong Names’ to the kit.

Version 3.0 Released

Extensive changes made. Please download the kit and read the appropriate Javadocs for details.

Changes in version 2.6

Added the method Customer.delete() which allows you to delete a Customer
Added the method DomOrder.cancelTransferRequest() which allows you to cancel the transfer-in request for a domain name
Added the method Order.sendRfa() which allows you to re/send the email asking for transfer-in approval for domain names.

Changes in version 2.5.3

Bug fix: DomainContact.delete() used to throw an “Invalid Cast from string”” exception due to an incorrectly coded return type. This has been fixed.

Changes in version 2.5.2

Bug fix: It is now possible to view the XML sent and received.

Changes in version 2.5.1

Bug fix: The Setup.ini file was missing

Changes in version 2.5

Bug fix in Modify Customer Details and Modify Contact Details forms
More details in the Javadocs for DomOrder.getDetails()
Link to new Demo Server added.
Move Service functionality added in API
Add Funds functionality for both Sub-Resellers and Customers also added.
Domain Forwarding, Mail Forwarding, Managed DNS Products now available through the API.

Changes in version 1.5

Timeouts in the .NET API Kit when making some method calls are fixed.
The .NET API Kit is now strongly named.

Changes in version 1.4

Hashtable being passed by the Examples kit, to the domainHash parameter of the renewDomain method, in the Domain class, is now in the correct format.

Changes in version 1.2

Modified the default soap end point. It now points to the demo server.
Fixed Api Kit dll linkages in the Examples solution.

Tags: Api, ASP, Core Kit, Customer Signup, Demo Server, Deprecated Methods, DNS, Java, Java Docs, Kit Class, Parameters, Registerdomain, SSL, Xml

Filed in .NET API Kit with 0 Comments

23 Aug 10 Sample Domain Names API Flow and some Notes

Buying Process for a single Domain Name

Checking Domain Availability: First call the DomOrder.checkAvailabilityMultiple() method to discover if the domain in question is available for registration.
Customer Selection/Addition: If the domain is available, you will have to retrieve the customer id of the customer who wishes to buy the domain. If the customer already exists, you can use Customer.getCustomerId() to get it or use Customer.addCustomer() to create a new one. The customer id will be in the return value in both cases.
Get Registration Info: You’ll need the Name Servers and the Contact Ids to register a domain at the registry. Get the list of existing contacts using DomContact.list().
Validate the parameters: Now pass all the information required to DomOrder.validateDomainRegistrationsParams() to validate them and ensure correctness.
Register the Domain: Call DomOrder.addWithoutValidation() with all the parameters you’ve just validated and you’re basically done.

IMPORTANT

Using DomOrder.add(): The use of DomOrder.add() to register a domain is now deprecated. This method is single-threaded and inefficient and so is much slower than using steps 4 and 5 in the Buying process flow. Use the DomOrder.validateDomainRegistrationsParams(), DomOrder.addWithoutValidation() method pair instead.

Adding contacts for .US and .COOP domains: The contacts for .US and .COOP need to have addition information to be correctly added. .US requires a Nexus Category while .COOP requires 2 Sponsors. When attempting to register these domains, DomOrder.validateDomainRegistrationsParams() will return “InsufficientContactDataException in DomValidation while adding order” in the status has under the error key. When you see this error, you should use DomContactExt.setContactDetails() to set the relevant additional information and try again. If you attempt to call DomOrder.addWithoutValidation() with these incomplete contacts for .US or .COOP, you will get “Error during adding contact” in the status hash under the error key.

Modifying Domain Name Details

Reference: Domain Name Registration & Management >>

There is no single DomOrder.mod() method. Rather, you must call the relevant method to modify the appropriate property of a domain name. For example, to modify the Domain Secret, call DomOrder.modifyDomainSecret() and so on.

Modifying Domain Contact Details

Reference: Modifying the Whois / Contact Details of a Domain Name >>

There is a bit of a niggle when modifying the contacts to be used by a domain name. One can first get the contact ids for a particular domain by calling DomOrder.getDetails() with the orderid and ContactIds in the options Vector. We can then DomContact.listNames() to get a list of all contacts belonging to a particular Customer and show this in a list on the screen. We can then use DomOrder.modifyContact() to modify the contacts being used.

If the Customer chooses to modify the Registrant contact, then we should check if it is fit to be used in such a manner by calling DomContactExt.isValidRegistrantContact(). Some registries like .US and .COOP require additional information and this can be supplied to the contact with a call to DomContactExt.setContactDetails() if DomContactExt.isValidRegistrantContact() returns false.

If an attempt is made to use an incorrect contact id (one which would fail the DomContactExt.isValidRegistrantContact() test), then a InsufficientContactDataException is thrown. You can catch it and then set the details using DomContactExt.setContactDetails().

IMPORTANT

The system allows you to create an infinite number of Resellers and Sub-Resellers, each with customers under them. Orders can be placed only on behalf of the Customers and cannot be owned by Resellers or their Sub-Resellers directly. You can create as many Customers as you wish.

Reference: Videos describing the relationship between Customers and Sub-Resellers >>

Tags: Api, Buy Domain, Contact, Contacts, Coop, Correctness, Customer Id, Customer Selection, Discover, Domain Availability, Domain Name, Domain Names, Domain Registry, DomOrder.checkAvailabilityMultiple, First call, Ids, Name Servers, Nexus, Parameters, Register Domain, Register Domains, Registration Info, The

Filed in Sample API Flow with 0 Comments

22 Aug 10 Transferring your .EU Domain Name

Before proceeding with the Transfer you are advised to first go check if your Domain Name can be Transferred. Click here to check if your domain name can be transferred >>

IMPORTANT

In case of a .EU Domain Name Transfer, the Expiry date is updated to 1 year from the date of Transfer and not to 1 year from the date the domain name was set to expire prior to Transfer.

For example, if a Domain Name has the Expiry date as 24 Oct, 2007 and it gets Transferred to another Registrar on 2 Sep, 2007. The new Expiry date will be 2 Sep, 2008 and not 24 Oct, 2008.

If you wish to Transfer a .EU Domain Name to Gossimer, then you need to follow the steps mentioned below:

Transfer Process for Customers

1. Login to your Control Panel from http://manage.gossimer.biz/customer.

2. In the Control Panel go to Domains -> Domain Registration -> Transfer. There, enter the Domain Name you wish to Transfer.

3. Select the Registrant Contact for this Domain Name. You may select from the available list of contacts or Add a New Contact.

It is compulsory for you to agree to the associated Product Agreement(s) by selecting the Check Box.

4. In order to avoid any downtime for the website/emails associated with your .EU domain name during the Transfer, it is necessary to mention the Name Servers already in use by your .EU domain name. You may also provide any new Name Servers that you would like to associate your .EU domain name with. Here, it is obvious that all the necessary DNS records are already created on the new Name Servers for the website/emails to be functional.

5. You need to mention any existing Child Name Servers for your .EU domain name alongwith their respective IP Addresses. This is necessary to avoid any downtime for the website/emails associated with any domain name using these Child Name Servers as their Name Servers. If you wish to Register any new Child Name Servers, you may also mention the same alongwith the respective IP Addresses. These new Child Name Servers will be Registered once the domain name is Transferred successfully.

Child Name Servers can also be Registered separately. Click here to know how >>

6. Finally, proceed with the Payment of the Invoice. Click here to read more details on Payment >>.

Now that you have placed the Transfer Order, the Registrant Contact for the Domain Name will receive an e-mail from the Registry for the Transfer Authorization process, which needs to be approved within 7 days. The Registry provides an additional grace period of 7 days for approval, in case the Transfer was not approved within the initial 7 day period. The authorization can also be provided through a fax to the Registry from the Registrant Contact. Template of the confirmation fax is provided below:

Transfer confirmation fax >>

The request is processed once the Registry receives approval from the Registrant.

Transfer Process for Resellers

1. Login to your Control Panel from http://manage.gossimer.biz/reseller.

2. In the Control Panel go to Products -> Domain Registration -> Transfer. There you would have to enter the Domain Name you wish to Transfer.

IMPORTANT

Transfer request for .EU Domain Names cannot be placed from the Storefront/within the Control Panel. Hence, it is advised that you re-direct all purchase related links from within your, your company user’s and your Customer’s Control Panel to your SuperSite URL or your Custom URL (if you have integrated with our platform using our API).

Reference:
Click here to know what is SuperSite >>
Click here to read about API Integration >>
Click here to read how to integrate your Website and Shopping Cart with your Customer Control Panel >>

3. Enter the Username (Email Address) of the Customer, on whose behalf you wish to buy this Service. If the Customer is new, you can Add the Customer, by filling the form given there.

4. Select the Registrant Contact for this Domain Name. You may select from the available list of contacts or Add a New Contact.

It is compulsory for you to agree to the associated Product Agreement(s) by selecting the Check Box.

5. In order to avoid any downtime for the website/emails associated with your .EU domain name during the Transfer, it is necessary to mention the Name Servers already in use by your .EU domain name. You may also provide any new Name Servers that you would like to associate your .EU domain name with. Here, it is obvious that all the necessary DNS records are already created on the new Name Servers for the website/emails to be functional.

6. You need to mention any existing Child Name Servers for your .EU domain name alongwith their respective IP Addresses. This is necessary to avoid any downtime for the website/emails associated with any domain name using these Child Name Servers as their Name Servers. If you wish to Register any new Child Name Servers, you may also mention the same alongwith the respective IP Addresses. These new Child Name Servers will be Registered once the domain name is Transferred successfully.

Child Name Servers can also be Registered separately. Click here to know how >>

7. Finally, proceed with the Payment of the Invoice. Click here to read more details on Payment >>.

Transfer confirmation fax >>

The request is processed once the Registry receives approval from the Registrant.

Tags: Api, Contact, Control Panel, DNS, Dns Records, Domain Registration, Domain Transfer, Domains, Downtime, Emails, Eu Domain Name, European Union, Expiry Date, Ip Addresses, Name Domain, Name Servers, Product Agreement, Registrant, Registrar, Servers, Transfer Domain

Filed in Transferring your Domain Name from Another Registrar to Gossimer with 0 Comments

22 Aug 10 Add / Modify a PayPal Direct Payment API Gateway

Gossimer has directly integrated the PayPal API within our system, such that by mentioning a few details in your interface and your Business PayPal Account, you can safely and securely collect money from your Sub-Resellers and Customers.

When your Customer/Sub-Reseller decides to pay you through this Payment Gateway, we send all the variables via an API Call to the PayPal Server, to get the transaction authenticated. All this while your Customer/Sub-Reseller continues to remain within their OrderBox Control Panel itself.

Before you Start
You will need to verify/perform the following before you start -

Verify that you have a Business PayPal account only. You cannot integrate a Personal PayPal account with our System.
Apply for Website Payment Pro (for US Business PayPal accounts only)
You need to apply for Website Payment Pro before you can make successful API calls to services such as DirectPayment. If you have already been approved for Pro, you also need to accept the Billing Agreement. This is sometimes overlooked by merchants who think they have already accepted this by applying for Pro, but it is indeed a separate step that must be completed after approval.

To apply for Website Payment Pro, follow these steps:

a) Login to your PayPal account [must be a Business account] from https://www.paypal.com

b) Click the Merchant Tools tab

c) From the Dropdown select

Website Payment Pro

d) On the bottom of the right column, under Getting Started, click on

Submit Application

e) Complete the 2 page form

f) Click

Go To My Account

At this point, your account will undergo an approval process by PayPal that generally takes 2-3 days. Once you have been approved for Website Payments Pro, login back into your PayPal account and complete these steps:

i) Click the Merchant Tools tab
ii) In the top right corner, click Accept Billing Agreement
iii) Click Agree
Allow Gossimer’s PayPal API Name to make API calls on your account

a) Login to your PayPal account from https://www.paypal.com

b) Click on

Profile -> API Access -> API Access Authorization / Authorize API Access / API Authorizations

c) Click on

Add

d) Mention the API Account Name as

paypal_api1.myorderbox.com

e) Enable API Access for the following calls and click on the Save button

i) RefundTransaction
ii) GetTransactionDetails
iii) TransactionSearch
iv) DoCapture
v) DoVoid
vi) DoDirectPayment
vii) DoAuthorization
Using PayPal Direct Payment API Gateway, you would be able to accept funds from only 55 countries. The complete list of these countries is available at http://www.paypal.com/cgi-bin/webscr?cmd=_display-approved-signup-countries-outside.

Adding the PayPal Direct Payment API Gateway into your account consists of the following simple steps -

1. Login into your Reseller Control Panel from http://manage.gossimer.biz/reseller

2. Click on the Settings -> Finance & Billing -> Payment Gateway -> List / Add

3. Click on the Add Payment Gateway button and then on the Add a PayPal Direct Payment API Gateway link.

4. Enter the following details and Save your changes by clicking on the Submit button

Gateway Name – This Gateway Name would be shown to your Customers/Sub-Resellers, when they are about to make Payment. You can use something like “Credit Card Payment” or “Visa/Master Card” etc.

PayPal Account Username – The Username [e-mail address] you use to login into your PayPal Business account.

Currency – PayPal allows you to charge your Customers/Sub-Resellers in 6 different currencies. However, to use the PayPal Direct Payment API Gateway, you can only select USD Currency.

Currency Exchange Rate – If your Selling Currency differs from USD, we will have to convert the Order Value to the PayPal Currency, BEFORE we send your Customer/Sub-Reseller to PayPal. For this purpose the system needs a exchange rate between the two.

You may choose to maintain this exchange rate yourselves or let us maintain it for you. We download FOREX rates on a daily basis from a recognised source and update exchange rates for you. If however you wish to update the rates yourselves then you may do so by selecting the I would like to Maintain the currency exchange rate myself checkbox AND entering your own conversion rates.

Select the types of CREDIT CARDS that your merchant account supports - You need to select the types of Credit Card that are supported by your PayPal Account. The credit card types available are – Visa, MasterCard, American Express, Discover. You can also decide the sequence in which you want your Customers / Sub-Resellers to view these Card types on the payment page.

Payment Gateway Access Level for Customers and Sub-Resellers – Click here to know more about the Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>

Deciding whether a Sub-Reseller and Customer is Credited with the Gross Amount or Net – PayPal deducts a fee per transaction. There are two types of Transactions that can pass through your PayPal integration – Invoice/Debit Note Payment, and Add Funds. Click here to know more about the Payment Gateway Transaction types and Access Levels for your Customers and Sub-Resellers >>

In case of an Add Funds Transaction, you have the option of crediting your Customers/Sub-Resellers with the NET Amount that PayPal credits you with, or choose to credit them with the gross funds and bear the charges yourselves.

IMPORTANT

If you have selected to credit a Customer/Sub-Reseller with the Net Amount in an Add Funds transaction, then you must submit either a Fixed Transaction fee (greater than 0) or a Variable Transaction fee (greater than 0).

Send me a Reminder if a transaction is pending for more than x days – In case you have not yet accepted a payment sent to you via the PayPal Payment Gateway, you can get e-mail reminders sent across to you from our system, after every x number of days, until you either Approve or Decline these payments. Click here to know how to Approve / Decline Payment Gateway transactions >>

Display Position – If you plan on adding Multiple Gateways you can select the position in which you wish to display this Gateway on your Payment Page.

IMPORTANT

1. The SuperSite contains information about the various Payment options you offer to your Customers and also presents these options at the time of purchasing Products and Services. This data is downloaded to your SuperSite from your Control Panel and cached (stored) on the SuperSite Server. Hence, you would need to refresh the cache of your SuperSite once you have completed the above process. You can accomplish this from within your Control Panel itself by clicking on Tools -> Reload SuperSite & PartnerSite Cache -> SuperSite Payment Preferences. Click here to know what is SuperSite >>

2. After you have setup the above, you must setup a PayPal Standard Checkout Gateway as well, as per the Legal guidelines mentioned by PayPal. Click here to know how >>

Tags: American Express, Api, Api Calls, Business Account, Control Panel, Gossimer, Interface, Merchant Tools, Merchants, Money, OrderBox Control Panel, Payment Gateway, Paypal, Paypal Account, Paypal Payment, Personal Account, Resellers, Tab C, Variables, Website Payments Pro, Www Paypal, www.paypal.com

Filed in Integration with PayPal Gateway with 0 Comments

22 Aug 10 Read this FIRST: Reseller Account Startup Guide

As a Reseller, you need to make the following settings within your Reseller Control Panel to begin selling Products and Services to your Customers and Sub-Resellers.

1. Select your Selling and Accounting Currency

At the time of sign-up, you MUST select your desired Selling and Accounting Currency.

Click here to see a video on setting your Selling and Accounting Currency >>
Click here to read an article on setting your Selling and Accounting Currency >>

2. Add Funds in your Reseller Account

To let your Customers and Sub-Resellers buy Products and Services through you, you need to add sufficient Funds in your Reseller Account with . How? >>

3. Understand the relationship between Resellers, Customers, Sub-Resellers and Orders

Click here to see a video on an Introduction to Customers, Sub-Resellers and Orders >>

4. Decide which Products and Services to sign-up for, and configure them

Gossimer offers a wide-array of Products and Services that you can choose to sell. Select the services that you wish to sell, and sign-up for them from your Control Panel. How? >>

Once you have signed up for these Products and Services, you need to configure various settings before you get started

Click here to see a video on setting up your Domain Registration Business >>
Click here to read the Domain Registration Reseller Setup Guide >>

Click here to read the Domain/Mail Forwarding and Managed DNS Reseller Setup Guide >>

Click here to read the Web Hosting Reseller Setup Guide >>

Click here to read the Email Hosting Reseller Setup Guide >>

Click here to read the Website Builder Reseller Setup Guide >>

Click here to read the Live Chat Reseller Setup Guide >>

Click here to read the Digital Certificate Reseller Setup Guide >>

5. Configure your website

Gossimer offers you various methods of setting up your own Website to sell various Products and Services integrating your Sales process with our system. You could either

Use our ready-made private labeled SuperSite for all your retail business

Click here to read the SuperSite Guide >>

You MUST do the following if you are using the SuperSite -

Change the URL for your SuperSite. How? >>
Customize the header/footer of Supersite. How? >>
Specify the Additional Payment Options for your Customers/Resellers in the SuperSite. How? >>
Customize the content of the Static bar on your SuperSite. How? >>
Customize the content of the Contact Us page on your SuperSite. How? >>

AND/OR

Use our ready-made private labeled PartnerSite for all your wholesale business

Click here to read the PartnerSite Guide >>

You MUST do the following if you are using the PartnerSite -

Change the URL for your PartnerSite. How? >>
Customize the header/footer of PartnerSite. How? >>
Customize the content of the Static bar on your PartnerSite. How? >>
Customize the content of the Contact Us page on your PartnerSite. How? >>

OR

Create your own website using our API

Along with your Reseller account you get a comprehensive API with FREE client kits in PHP, Java, Perl and .NET. All Resellers have API access to the system. Every functionality of the system is available as an API CALL.

Click here to learn more about the API >>

NOTE: The API Integration method is recommended only if you have a proficient development team.

6. Configure Control Panels for your Customers and Sub-Resellers

provides you with comprehensive private-labeled control panels for your Customers and Sub-resellers in order to manage the products and services they purchase from you. You can either -

Use our ready-made private labeled Control Panels

The Control Panels allow your Customers and Sub-Resellers to place, manage, upgrade, downgrade, use, renew, delete, suspend/unsuspend, lock their Orders for various Products and Services from a single management window.

You MUST do the following if you are using the Control Panels -

Set your company logo on top of your Customer/Sub-Reseller Control Panels. How? >>
Customize the Footer of your Customer/Sub-Reseller Control Panels. How? >>

Build your own Control Panels using our API

If you are already selling several other products and services to your existing customer-base through another interface/control panel and do not want to add the burden of introducing the new Control Panels to them, you could use the OrderBox API to integrate provisioning and management of all OrderBox Products and Services in your existing interfaces and Control Panels.

Gossimer provides you comprehensive API kits in Java, PHP, Perl and .Net. You can use any of these to integrate with the system. More on API >>

The API Integration method is recommended only if you have a large Customer base and employ the services of a proficient development team.

7. Integrate your Website and Shopping Cart with your Customer Control Panel

Once you have configured your website and Control Panels for your Customers in steps 5 and 6 above, you should configure the integration between your Customer Control Panels and your website, so that your Customers can jump from their Control Panels to your website to make any purchases. Click here to learn how you can do this >>

8. Update your Contact Information

Personal Details: Personal Information such as your Personal details, your Brand Name, your Website URL, your personal Language preferences, can be easily reviewed and modified from your Reseller Control Panel. How? >>

Company Contact Information: The system automatically sends emails to your Customers and Sub-Resellers from the e-mail addresses and From Names specified in your Contact Information section.

You should update the contact details of various departments in your company, to ensure that all communication with your Customers and Sub-resellers is carried out using your branded email addresses and email signatures. How? >>

9. Configure your Payment Collection options

Setup your Online Credit Card Payment Gateway: The system allows you to integrate any Payment Gateway of your choice to collect money online from your Customers and Sub-Resellers.

Click here to read the Payment Gateway Integration Guide for more details >>
Click here to learn ho you can define the Minimum Transaction Amount for a Payment Gateway Transaction >>

Specify offline Payment Collection Methods for the SuperSite: Apart from collecting funds via a payment gateway, you should also describe other offline means of receiving funds from your Customers, during their shopping process, within the SuperSite. How? >>

Specify offline Payment Collection Methods for the Control Panel: You may also present other offline means of receiving funds to Customers/Sub-Resellers who wish to pay you from within the Control Panels e.g. your Bank details for receiving Bank/Wire Transfers, your Company Details to receive Check/Draft payments. How? >>

Configuring Payment Collection Parameters: You can let OrderBox assist you in collecting payments from your Customers by specifying appropriate Payment Collection Parameters for every Product and Service, that you are selling through OrderBox. How? >>

10. Configure Other Miscellaneous Options

Set your Funds Threshold Level: You should ensure that you always have a healthy balance in your Advance Account with to allow execution of your Customers and Sub-Resellers orders, by defining your Funds Threshold Level from inside your Control Panel, so that OrderBox can remind you via e-mail when your balance falls below this level. How? >>

Company Users: Create special logins for your (sales, support etc.) company users to enable them manage your business efficiently. Control all access for these accounts; and restrict specific menus from being viewed through them. More >>

Sub-Reseller Sign-up options: OrderBox lets you control Sub-Reseller sign-ups under you. More >>

Tags: Accounting, Api, Array, Bank/Wire Transfers, Control Panels, Currency, Digital Certificate, DNS, Domain Mail, Domain Registration Business, Email, Email Hosting, Email Setup, Gossimer, Gt 2, Gt 4, Gt 5, Java, Live Chat, Mail Forwarding, Online Credit Card Payment, Perl, Php, Read Email, Read Mail, ready-made private, Relationship, Reseller Account, Reseller Control Panel, Resellers, retail, Setting Up Your Own Website, Startup Guide, Static Bar, Web Hosting, Web Hosting Reseller Setup Guide, Website Builder

Filed in Reseller Guides with 0 Comments

22 Aug 10 IMPORTANT: API Abuse

If any Reseller exceeds the limit for number of calls defined in our OrderBox API Acceptable Usage Policy (AUP), their IP address will be temporarily blocked from accessing our servers, for a period of 24 hrs. During this time, they will be unable to make any calls to our Servers using the API. This block will be automatically cleared after 24 hrs and a notification to that effect will be sent to them. However repeated abuse will result in permanent blocking of the account.
Moreover, if the number of simultaneous connections from a single IP Address, increases beyond a certain number, OrderBox would automatically drop these excessive connections of that Reseller.

Tags: Acceptable Usage Policy, Api, Ip Address, Orderbox, Servers, Simultaneous Connections

Filed in Reseller API Guide with 0 Comments

21 Aug 10 Managing Managed DNS, Web Hosting, Email Hosting, Live Chat, Website Builder Orders through your API integration

The Managed DNS, Web Hosting, Email Hosting, Live Chat and Website Builder Orders reside on separate servers from the ones you connect to, via the API Kits. Due to this, your Customers need to login into their (individual) Control Panels, for managing such Orders.

Gossimer now provides you with another method of directly allowing access to your Customer, to manage their Managed DNS, Web Hosting, Email Hosting, Live Chat and Website Builder Orders from your interfaces itself.

To accomplish this, you need to use either of these 2 methods and pass the following parameters to the mentioned URL, via an HTTP POST method:

Method 1 (recommended)

URL – http://<Your_Control Panel_Branded_URL>/servlet/ManageServiceServletForAPI

orderid – the Managed DNS/Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id that your Customer wants to manage

loginid – you need to generate a Login ID, that you need to pass as the value of this parameter for allowing the Customer to manage his Order. This can be accomplished by calling the API method generateLoginID in the Customer class. In order to call generateLoginID, you will have to pass ipAddress as a parameter. This Login ID generated will be valid for a very short period of time and you should use it immediately upon generating it.

viewdns – the value of this parameter can be either true or false. If you do not pass any value for this parameter, then it is interpreted as false.Pass true – if the Order is Web Hosting or Mail Hosting and you want to allow your Customer to manage the DNS Records of that particular Order.

Pass false – if the Order is Web Hosting or Mail Hosting and you want your Customer to manage only the Web or Mail Hosting Order.

This method is the most secure method of allowing your Customers to manage their Managed DNS, Web Hosting, Email Hosting, Live Chat and Website Builder Orders, since it does not expose the Customer’s Username and Password in your interface.

If you choose to use this method, then you would need to create an intermediate interface to which you can provide the required parameters, and which in-turn generates a valid URL and redirects your Customer.

You need to provide orderid and any authentication details (optional) to this interface. This interface would then call the API method generateLoginID of the Customer class and build a URL with loginid, viewdns and orderid as parameters, and then redirect the Customer to this URL.

Example

Let us call this interface a servlet named ManageOrderBoxControlPanel (assuming that you are using our JAVA API Kit).

This interface would accept Managed DNS/Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id as a parameter. So, in order to manage a Service, you will call this interface with http://<Your-Server-URL>/ManageOrderBoxControlPanel?orderid=<orderid>.

Now this servlet would need to call the API method generateLoginID of the Customer class like -String loginid = API call to “generateLoginID(username,password,resellerid,langpref,role,ipAddress) ;

where,

username – the Username of the Customer, to whom the Order belongs
password – the Password of the Customer, to whom the Order belongs
resellerid – the Reseller Id associated with your Reseller account. This is obtainable from Settings -> Personal Information -> Primary Profile in your Reseller Control Panel.
role – customer

The final URL to which you would then redirect your Customer to, would look like - http://<Your_Branded_URL>/servlet/ManageServiceServletForAPI?loginid=<loginid>&orderid=<orderid>&viewdns=<true/false>

The pseudo code for accomplishing the above is as follows:

public class ManageOrderBoxControlPanel extends HttpServlet
{

authentication params = Get Authentication parameters;
orderid = Get OrderBox orderid;
classname = Customer class;
viewdns = false;

set ipaddress with authentication parameters to call “generateLoginID”;

try

Unknown macro: { loginid = API method call “generateLoginID” of Customer class. }
catch()
Unknown macro: { handle exceptional condition. }

url = “http://<Your_Branded_URL>/servlet/ManageServiceServletForAPI?loginid=” + loginid + “&orderid=” orderid + “&viewdns=” + viewdns ;

response.sendRedirect(url);
}

Method 2

URL – http://<Your_Control Panel_Branded_URL>/servlet/ManageServiceServletForAPI

orderid – the Managed DNS/Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id that your Customer wants to manage

username – the Username of the Customer, to whom the Order belongs

password – the Password of the Customer, to whom the Order belongs

resellerid – the Reseller Id associated with your Reseller account. This is obtainable from Settings -> Personal Information -> Primary Profile in your Reseller Control Panel.

Pass false – if the Order is Web Hosting or Mail Hosting and you want your Customer to manage only the Web or Mail Hosting Order.

The disadvantage of using this method is that it is a bit less secure as the Customer Username and Password along with your Reseller Id can be viewed in the source of the page, from where you post to the ManageServiceServletForAPI servlet.

IMPORTANT

Do not send the above mentioned as parameters as part of a URL, or else this information will be displayed in your Customer’s Browser Address Bar.

Tags: Api, Browser Address Bar, Control Panel, Customer Class, DNS, Dns Hosting, Dns Records, Email Hosting, Hosting Website, http, Individual Control, Java, Live Chat, Login, Lt, Mail Hosting, Mail Order, Managed Hosting, Parameters, Period Of Time, Servers, Short Period, Url, Web Email, Web Hosting, Web Hosting/Email Hosting/Live, Web Hosting/Email Hosting/Live Chat/Website Builder Service Order Id, Web Mail

Filed in Reseller API Guide with 0 Comments

21 Aug 10 Read This FIRST – General API Integration Instructions

The API is exposed using SOAP, a common web services protocol. SOAP is extremely simple to use and debug since it is an XML based protocol. While SOAP is a standardized protocol, we are using certain complex data types which are not completely compatible across all platforms. However we have written our own wrappers to handle this and we offer direct integration kits in various platforms which you can directly download and use.

IMPORTANT

When our System receives a request, it tries to complete the action immediately. If the System is unable to complete the action for some reason, it will return an error response and try to complete the action again after sometime. This ensures a high level of fault tolerance.

Due to this, it is imperative that when you encounter an error response (especially for commands that have financial implications like Registering or Renewing orders), you MUST check whether the command eventually failed or succeeded. To do this, you will have to issue additional API commands (depending on the command for which you received an error response) to check the final status of the original command.

It is recommended that you implement this querying process to check the status of API commands as a scheduled task/cron/batch process. Alternately, you can also check the status of the command by logging into your Reseller Control Panel.

Currently integration kits are available in PHP, Java, Perl and .NET. Our Server exposes all relevant methods using SOAP. SOAP is a simple XML-HTTP based protocol whose client implementations are available in EVERY language. Follow the steps below to begin making calls to the API -

Step 1. Sign up for a Demo Reseller Account
You will initially test your API scripts on our demo Server. Click here to read how to sign up for a demo Reseller account >> .

You will need the following items before you proceed to the next step

Your Signup Username
Your Signup Password
Your Parent ID

The first two items would have been entered by you during the signup. For the last item simply login to your Demo Account and click on Settings -> Personal Information -> Primary Profile.

IMPORTANT

You can use these accounts to try out various aspects of the system. However, the demo accounts are reset every day. As such, any additional orders placed herein, or any modification done to these accounts, shall cease to exist after 24 hours.

Step 2. Proceed to the corresponding API kit for your platform
Click on the links below to refer to further instructions for the platform you are developing on -

Java API Kit >>
PHP API Kit >>
.NET API Kit >>
Perl API Kit >>

Step 3. Download the API Documentation
The complete documentation of all classes and methods available in the API can be found in the Docs below. The Docs below are javadocs, but the function names and explanations remain the same for all the platforms and the documentation is self explanatory. We recommend you download the docs and read through them completely once before you integrate your application:

Core Docs v3_10
Domains Docs v3_10
Hosting Docs v3_10
Other Products Docs v3_10

Step 4. Refer to the Parameter Validation details of different parameters passed in any API Calls
We have a detailed document on the Validation routines which you need to build in for the various parameters which you send to the API call. Failure to validate these fields on your side may result in an undecipherable error from the Server. Click here to read about Data Validation of Parameters passed in an API Method Call >>

Step 5. Refer to the Error format document and the common errors
The first time you run any example you are likely to encounter errors if you have not followed the steps perfectly. It is important to understand the format of an error. Click here to understand the format of an error that you will receive >>

IMPORTANT

Sometimes, you may receive a 302 HTTP Redirect response from our System. Your API implementation should be capable of following such a redirect.

Step 6. Run the examples
All the above kits contain examples which you can run and test the API functionality. Try these examples out to verify everything is working fine. You should first run these examples on the Demo Server. Use the demo sign up information gathered above and the Demo Server URL below to run the examples on the demo server.

Demo Server URLs for API Kits ver 3.x and above

Java and PHP API Kits

http://api.onlyfordemo.net/anacreon/servlet/APIv3
https://www.foundationapi.com/anacreon/servlet/APIv3

Perl and .NET API Kit

http://api.onlyfordemo.net/anacreon/servlet/APIv3-XML
https://api.onlyfordemo.net/anacreon/servlet/APIv3-XML

Demo Server URLs for older API Kits

Java and PHP API Kits

http://demo.myorderbox.com/anacreon/servlet/rpcrouter
https://demo.myorderbox.com/anacreon/servlet/rpcrouter

.NET and Perl API Kits

http://demo.myorderbox.com/anacreon/servlet/XMLrpcrouter
https://demo.myorderbox.com/anacreon/servlet/XMLrpcrouter

Step 7. Refer to common errors
In this documentation we have some answers covering common errors you can expect while integrating with the API. Click here to know details about common API errors >>

Step 8. Change the information to Live information when you are ready
Once you have followed the steps above and got the test programs to work successfully, you can duplicate the same code in your live application and replace the Demo Server and Reseller account information with your live username and password. You will also need to change the server URL to the live server URL.

LIVE Server URLs for API Kits ver 3.x and above

Java and PHP API Kits

http://www.myorderbox.com/anacreon/servlet/APIv3
https://www.myorderbox.com/anacreon/servlet/APIv3

Perl and .NET API Kit

http://www.myorderbox.com/anacreon/servlet/APIv3-XML
https://www.myorderbox.com/anacreon/servlet/APIv3-XML

LIVE Server URLs for older API Kits

Java and PHP API Kits

http://www.myorderbox.com/anacreon/servlet/rpcrouter
https://www.myorderbox.com/anacreon/servlet/rpcrouter

.NET and Perl API Kits

http://www.myorderbox.com/anacreon/servlet/XMLrpcrouter
https://www.myorderbox.com/anacreon/servlet/XMLrpcrouter

Refer to the corresponding kit and integration guide of the platform that you choose for further instructions.

IMPORTANT

As you duplicate your code on the live application environment, remember to change your Parent ID to the one associated with your Live Reseller account. You can find this from Settings -> Personal Information -> Primary Profile in your Reseller Control Panel.
You need to display the Registrar Registrant Agreement for Domain Names Legal document within the domain name registration buy process on your website.

It is compulsory to display this document AS IS to your Customers and get them to agree to the terms mentioned therein, before buying domain names through you. You can view this agreement from within your Reseller Admin Control Panel at Help >> Legal Agreements.

Tags: Api, Api Commands, Data Types, Demo Server, Exposed, Fault Tolerance, Financial Implications, http, Integration, Java, Java Perl, Net Server, Parent, Parent Id, Perl, Php, Platforms, Protocol, Registrar, Relevant Methods, Reseller Account, Reseller Control Panel, Soap Soap, standardized protocol, Test Scripts, web services protocol, www.foundationapi.com/anacreon/servlet/APIv3, www.myorderbox.com/anacreon/servlet/APIv3, www.myorderbox.com/anacreon/servlet/APIv3-XML, www.myorderbox.com/anacreon/servlet/rpcrouter, www.myorderbox.com/anacreon/servlet/XMLrpcrouter, Xml

Filed in Reseller API Guide with 0 Comments

19 Aug 10 PHP API Kit and Integration Guide

Follow the instructions below to begin integration with the API using PHP -

Make sure you have read the General API Integration Instructions first. If you have already integrated the PHP API Kit at your end, read the Change Log first to know what has changed since.

Reference:

General API Integration Instructions >>
Change Log >>

IMPORTANT

The PHP API Kit is not compatible with version PHP5. You need to use version PHP4 in order to integrate the API Kit at your end.

Step 1. Download the API Kit
Click the link below to download the relevant API kits (updated on 6th March, 2008).

PHP_CoreKIT_v3_10.zip
PHP_DomainsKIT_v3_10.zip
PHP_HostingKIT_v3_10.zip
PHP_OtherProductsKIT_v3_10.zip

Core_Docs_v3_10.zip
Domains_Docs_v3_10.zip (updated on 1st April, 2008)
Hosting_Docs_v3_10.zip
OtherProducts_Docs_v3_10.zip

IMPORTANT

Since “list” is a keyword in the PHP language, the “list()” methods in the various classes (in the PHP Kit) has been renamed to “listOrder().” However, the documentation still mentions the method name as “list” since the documentation is JAVA specific.

Instructions to pass parameters to functions using the PHP Kit

Since PHP uses typeless variables you will have to ignore the datatypes presented in the docs. But for assigning values to variable of types other than strings and integers special care will have to be taken. Below is the list of datatypes presented in the API Doc and their usage in PHP.

Java Data	Types Assigning values in PHP
String	“firstname@secondname.com”
int	123
HashMap (Datatype for storing name-value pair)	array(“domain.com”=>”1″)
Array and Vector (Datatype for storing more than one value)	array(“ns1.domain.com”,”ns2.domain.com”)
boolean (Datatype for storing true or false)	true / false

Example:

For Calling a Function which takes a String datatype and an integer datatype as its paramters

public int function1(java.lang.String userName, int parentid)
$result = $obj->function1(“firstname@secondname.com”,1);
For Calling a Function which takes a HashMap, a String Array and an integer Array as its parameters

public java.util.HashMap function2(java.util.HashMap domainHash, java.lang.String[] orderby, int[] resellerId)

and domainHash is accepting the domainname and the number of years as name value pair

$result = $obj->function2(array(“domain1.com”=>1,”domain2.com”=>2),array(“column1″,”column2″),array(22,33))
For Calling a Function which takes a Vector and a boolean as its parameters

public java.lang.String function3(java.util.Vector nameServers, boolean add)
$result = $obj->function3(array(“ns1.domain.com”,”ns2.domain.com”),true)

Step 3. Extract the files from the API Kit archive
You should get the following directory & files structure

examples/ – Pre-written examples. You can directly run these examples to test API functionality
lib/ – The PHP class files, library files and wsdl files that you need to run your application

Step 4. Run the examples
You can run the pre-written examples provided in the “examples” folder. Note the following steps to do so -

1. Upload the “examples” and “lib” folders to your web server where you run your PHP scripts. Make sure that both these folders are uploaded to the same parent folder.

2. You must have PHP 4 installed on the server

3. You must have a Demo account ready the first time. Read the General instructions if you have not yet setup your demo account. Reference: General API Integration Instructions >>

IMPORTANT

The Demo server duplicates all functionality of the live server, however all Domain Names will appear as available on the Demo Server. It does not query the live registry and therefore names which are not available on the live registry will still appear as available on the Demo Server. At times connectivity to the DEMO Registry may be down resulting in errors.

4. Make the appropriate changes to “constants.php” in the “examples” folder, by putting in the values for your “SERVICE_USERNAME”, “SERVICE_PASSWORD”, “SERVICE_PARENTID”. The remaining settings have already been made for you in this file. You may only need to change the path for the “lib” folder if you have uploaded the lib folder elsewhere

5. The URL to which the call is made is maintained in the “config.php” file inside the “lib” folder. By default all calls are made to the demo server URL using HTTP. You can make changes to this file and redirect your calls to the appropriate server

IMPORTANT

If you are using HTTPS calls you MUST have the extension for CURL installed and enabled in your PHP installation.

6. Another important parameter maintained in the “config.php” file is the variable $DEBUG. If this variable is set to “true”, then for each call you will see the entire XML Request and Response in the output. You should keep it to “true” during testing, but set it to false on the live environment.

7. Every Example file has a set of functions which you can run.

8. Once you have modified the appropriate example file, access it over your webserver by putting in your URL such as http://yourserver/examples/html and choose the required function from the links given in the left frame.

IMPORTANT

Step 6. Writing your own code
After running each example above, if you simply refer to the corresponding .php file in the examples folder you will easily be able to figure out the code snippet you need to write in order to make a similar call.

Making an API call to perform any action is a matter of three steps:

(i) Include the appropriate PHP Class file as below

include($LIB_DIR.”Order.class.php”);

(ii) Obtain a pointer to the required Class. This is done by using the code below

$serviceObj = new Order($LIB_DIR . “wsdl/Order.wsdl”);

(iii) Call the required method on this object. A complete reference of all methods is available in the Docs folder. This can be achieved by using the code below

$AssociativeArray = $serviceObj->setCustomerLock($SERVICE_USERNAME, $SERVICE_PASSWORD, $SERVICE_ROLE, $SERVICE_LANGPREF, $SERVICE_PARENTID, $orderId);

IMPORTANT

You will notice above that EVERY method in the docs takes the same first 5 parameters as below

String SERVICE_USERNAME, String SERVICE_PASSWORD, String SERVICE_ROLE, String SERVICE_LANGPREF, int SERVICE_PARENTID

In the examples these parameters have been put into a single constants file from which they are accessed by including the constants file. These parameters are common no matter which method you call. These parameters mean the following:

String SERVICE_USERNAME: Your Username String SERVICE_PASSWORD: Your Password String SERVICE_ROLE: This will always be a string "reseller" String SERVICE_LANGPREF: The 2 letter code of the language in which you wish to receive errors and descriptions - "en" for English int SERVICE_PARENTID: The ID of your parent which you can get from your profile section

IMPORTANT

Remember, when passing numerical data in hashtables, please ensure that the number is passed as a String.

Step 7. Change the information to Live information when you are ready
Once you have followed the steps above and got the test examples to work successfully, you can duplicate the same code in your live application and replace the Demo Server and Reseller account information with your live username and password. The URL that you make your calls to also needs to change to the LIVE Server URL. You will make this change in the “config.php” file in the “lib” folder

Once again note, if you are using the HTTPS URL you MUST have the extension for CURL installed and enabled in your PHP installation.

Tags: Api, Api Documentation, Api Guide, Api Kit, appropriate server, Datatype, Datatypes, Demo Server, Docs, Explanations, http, Integers, Integration Guide, Java, Java Data Types, Javadocs, Parameters, Php, Php Guide, PHP installation, Php Java, Php Kit, Php Language, Php4, Platforms, Reference, Step 1, Step 2, Variables, Web Server, Xml

Filed in PHP API Kit with 0 Comments

19 Aug 10 Change Log

Changes in version 3.10

Java Docs updated

Changes related to classes and methods:

New Classes and Methods

Domains Kit
New Class Name	New Method
ThirdLevelDotUk	String invoiceOption
ThirdLevelDotUk	String existingEndTime

New Parameters introduced in Existing Methods

Other Products Kit
Class Name	Method Name	New Parameters
EngageOrder	renew	String invoiceOption
EngageOrder	renew	String existingEndTime

Deprecated Parameters in Methods

Domains Kit
Class Name	Method Name	Deprecated Parameters
ZoneOrder	add	“No Of Records” in DomainHash

Deprecated Methods

Domains Kit
Class Name	Deprecated Method	Suggested Class	Suggested Method
DomContact	addDefaultContact	DomContact	addDefaultContacts
DomContact	add	DomContact	addContact
DomContact	list	DomContact	listByType
DomContactExt	isValidRegistrantContact	DomContactExt	isValidContact
DomOrder	transferDomain	DomOrder	addTransferDomain
DomOrder	add	DomOrder	registerDomain
ZoneOrder	mod	ZoneOrder	Functionality not required anymore
DotEu	tradeDomain	DotEu	trade
DotEu	transferDomain	DotEu	transfer
DotEu	add	DomOrder	registerDomain
Core Kit
Class Name	Deprecated Method	Suggested Class	Suggested Method
Customer	addCustomer	Customer	signUp
Customer	modDetails	Customer	mod
Reseller	addReseller	Reseller	signUp
Reseller	modDetails	Reseller	mod
Reseller	addResellerWithStateId	Reseller	Functionality not required anymore
OrderSetup	getResellerSlabPercentageForProducts	OrderSetup	Functionality not required anymore
OrderSetup	getCustomerSlabPercentage	OrderSetup	Functionality not required anymore

Changes in version 3.9

Java Docs updated
Changes related to classes and methods:

The following method in the Domains Kit is deprecated and its use should be discontinued -

Deprecated method Class New method to be used

isValidRegistrantContact DomContactExt isValidContact

Changes in version 3.8

Java Docs updated
Changes related to classes and methods:
1. The following changes have been introduced under the DotEu class within the Domains Kit -
  - New methods
    - trade
    - transfer
  - Deprecated methods
    - tradeDomain
    - transferDomain
2. The following new methods have been introduced under DigitalCertificateOrder class within the Other Products Kit -
  - enrollForThawteCertificate
  - reissue
  - renew
  - checkDigitalCertificateStatus
  - del
  - cancelDigicertOrder
  - changeDigicertPassword
  - addAdditionalLicenses
  - getDetails
  - getDetailsByDomain
  - getOrderIdByDomain

Changes in version 3.7

Java Docs updated

Changes related to classes and methods:

Some old parameters have been removed and new parameters introduced in their place under the following methods -

LinuxHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

WindowsHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

MailHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*
mod	Hashtable orderHash	String packagekey^, int additionalMailBoxes^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*
getModPricing	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*

SiteBuilder Class
Method	Old Parameter	New Parameters
mod	Hashtable orderParams	String packageKey^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*

NOTE:

^* packageKey will be the Identifier Key of the Plan (plan1, plan2, plan3, plan4) for which the Order needs to be added/modified.

^# ssl will be true or false depending whether the user wants Dedicated IP / SSL for the Order placed.

^## excessBandwidth is the Bandwidth which the user wants over and above the Bandwidth of the Order’s current plan.

^** additionalMailBoxes is the number of additional mail boxes over and above the existing ones in blocks of 100 accounts.

The following classes and their methods are removed:
- LinuxHostingPlanOnlyOrder
- WindowsHostingPlanOnlyOrder
- MailHostingPlanOnlyOrder
The SiteBuilderLite class has been renamed to SiteBuilder.
Two new methods, mod and signUp, have been introduced under the Reseller and Customer classes.
The return type of the ListByType method of DomContact class in the Domains Kit has been changed to Hashtable from Vector.

Changes in version 3.6

Java Docs updated

Changes related to classes and methods:

New methods have been added in the Core Kit under the following class: getProductMetadata – Product class
New methods have been added in the Domains Kit under the following classes:getDefaultContactId – DomContactExt class
listByType – DomContact class
addTransferDomain – DomOrder class
changePrivacyProtectionStatus – DomOrder class
registerDomain – DomOrder class
Changes to the DomOrder class in Domains Kit:

The following methods in the Domains Kit are deprecated and their use should be discontinued:

Deprecated method	Class	New method to be used

add	DomContact	addContact
addDefaultContact	DomContact	addDefaultContacts
list	DomContact	listByType
add	DomOrder	registerDomain
transferDomain	DomOrder	addTransferDomain
transferDomainWithoutValidation	DomOrder	addTransferDomain
addTransferDomainWithoutvalidation	DomOrder	addTransferDomain
add	DotEu	registerDomain in DomOrder class

IMPORTANT

While these methods are currently available, they are no longer supported and may be discontinued in the near future.

New methods have been added in the Hosting Kit under the following class: getHostingMetaData – WebHostingOrderData class
Changes to classes in the Hosting Kit:The invoiceOption parameter has been added to the add method of MailHostingPlanOnlyOrder, WindowsHostingPlanOnlyOrder and LinuxHostingPlanOnlyOrder classes

Changes in version 3.5

Java Docs updated
Changes related to classes and functions:
- New functions have been added in the Core Kit under the following classes: getList – Country class
  getStateListForCountry – Country class
  getDetails – Order class
  addResellerWithStateId – Reseller class
- An extra option called Supersite is added in the getDetails function of the Reseller class in the Core Kit.
- A new class LegalAgreement is added with the following methods under the Core Kit:getRegistrantAgreement
  getProductCategory
  getAgreement
  getAllAgreements
- A new function has been added in the Domains Kit under the following class:addCoopContact – DotCoopContact class
- The following functions in the DomOrder class in the Domains Kit are changed to show the Invoice options also:validateDomainRegistrationParams
  validateDomainTransferParams
  addWithoutValidation

Changes in version 3.4

Java Docs Updated
New Classes introduced in all Kits:

Core Kit

TaxService
getApplicableTaxes
getHashedTaxRules
Domains Kit

DotEu
    getEUCountryList
    tradeDomain
    transferDomain
    add
    isEUCountry

DotEuContact
    mod
    add
    addEuDefaultContact

DomOrder
    validateDomainRegistrationParams
    validateDomainTransferParams
    addTransferDomainWithoutvalidation
    addWithoutValidation
Hosting Kit

WindowsHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

LinuxHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

MailHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount
    list

MailHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

WindowsHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

LinuxHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap
Other Products Kit

DigitalCertificateOrder
    add
    getCertPrice

SiteBuilderSetup
    getPricingKeyPricingParamMap

EngageSetup
    getPricingKeyPricingParamMap

Changes in version 3.3

3 new functions have been added in the Core Kit under the following classes:

authenticateCustomerId – Customer class
login – Customer class
getOrderIdByDomainAndProductCategory – Order class
The name of the jar file in every kit is now unique.
Bug Fix – A minor Java Script problem was causing the frame links in the examples to not work in some browsers like Mozilla and Opera.

Changes in version 3.2

New methods added viz. Order.removeCustomerLock, Order.getLockList
The testing form provided now has a third frame which accepts the standard parameters passed in every call. If you set these parameters from the form, you can make test calls independent of the settings in the properties/constants file.

Changes in version 3.1

Minor bugs in WSDL files fixed.

Version 3.0 Released

Extensive changes made. Please download the kit and read the appropriate Javadocs for details

Changes in version 2.6

Added the method Customer.delete() which allows you to delete a Customer
Added the method DomOrder.cancelTransferRequest() which allows you to cancel the transfer-in request for a domain name
Added the method Order.sendRfa() which allows you to re/send the email asking for transfer-in approval for domain names.

Changes in version 2.5

Bug fix in Modify Customer Details and Modify Contact Details forms
More details in the Javadocs for DomOrder.getDetails()
Link to new Demo Server added.

Changes in version 2.3

Move Website functionality added in API
Add Funds functionality for both Sub-Resellers and Customers also added
Domain Forwarding, Mail Forwarding, Managed DNS Products now available through the API.

Changes in version 2.2

In customer class new method (authenticateCustomer) is added to authenticate the Customer.

Changes in version 2.1

DomUsContact.class

API for DomUsContact.class is provided
The characteristics of DomUsContact.class includes the method setContactDetails() that needs to be called for any contact used as Registrant contact for .US. for providing applicationPurpose and nexusCategory facility.

list() method

list() method of DomContact.class is now available to Customer as well as Reseller.
The function signature of listContact() is also changed – One has to pass Customer Id after Parent Id besides other parameters.

getCustomerAvailableBalance() fuction

getCustomerAvailableBalance() fuction is added to the Fund.class
This function returns the available balance of a Customer.

getCustomerId() function

getCustomerId() function is added to the Customer.class
This function returns the customer id of the customer.

The prefix of all user classes changed to Customer eg. UserService to CustomerService, UserServiceTest to CustomerServiceTest

Method signature change in DomContact.class
OLD – int add(java.lang.String userName, java.lang.String password, java.lang.String role, java.lang.String langpref, int parentid, int customerId)

NEW – int addDefaultContact(java.lang.String userName, java.lang.String password, java.lang.String role, java.lang.String langpref, int parentid, int customerId)

Tags: Api, Core Kit, Customer Signup, Deprecated Methods, DNS, Java, Java Docs, Kit Class, New Domains, nexusCategory facility, Parameters, Registerdomain, Reseller, SSL

Filed in Java API Kit with 0 Comments

17 Aug 10 Sample Hosting API Flow and some Notes

Buying Process for a Hosting Plan or Custom Package

Retrieve all Product Keys: First get the list of Product Keys from your local store. These Product keys are currently:
- lhbbudgetusa
- lhbbudgetplanus
- w2kbudgetusa
- w2kbudgetplanus
- lhbpremiumusa
- w2kpremiumusa
- mailboxbudgetusa
- mailboxbudgetplanus
- mailboxpremiumusa
Retrieve Hosting Plans for a Product Key: Now use WebHostingOrderData.getHostingPlans() to get the 3 hosting plans (premium, budget and custom) available per product key except for lhbbudgetplanus, w2kbudgetplanus and mailboxpremiumusa. Each of these three product keys have the custom build feature disabled and are associated with only 2 hosting plans, premium and standard. The return value is a hash of hashes with a serial number as the key. Per plan, the most important information is the planid, the planname and the totalprice. Use OrderSetup.getPricingKeyDisplayName() and OrderSetup.getPricingParamsDisplayName() to get the standard names for these values to build you display. You can also use getMonthlyCostAndValidate() under the appropriate HostingOrder class to get the pro-rata pricing for the plan.
Buy a Hosting Plan: Use add() under the appropriate HostingOrder class to add an order. Be sure to pass in ‘planid‘ as the key and the actual plan id as the value. You can specify the invoice options as well.
Buy a Custom Package: Use OrderSetup.getPricingKeyPricingParamMap() to get a list of all pricing keys and their related pricing params. Once more, you can use OrderSetup.getPricingParamsDisplayName() and OrderSetup.getPricingKeyDisplayName() to get the standard names for these values to build you display. You can also use getMonthlyCostAndValidate() under the appropriate HostingOrder class to get the pro-rata pricing for the package. Calling fetchAlternateLocationDetailsAndMonthlyCosts() under the appropriate HostingOrder class will give you the cost for a similiar order configuration at an alternate location. Once everything is set, you call add() under the appropriate HostingOrder class and passing it all the key:value pairs required.

Modifying a Hosting Plan or Custom Package

Reference: Renewing/Upgrading/Downgrading/Deleting a Web Hosting package >>

Retrieve the price of the new modification: First call getModPricing() under the appropriate HostingOrder class to get the pricing for the modifications you wish to make, passing in all the key:value pairs, not just the ones which have changed.
Modify the order: Now call mod() under the appropriate HostingOrder class and pass it a complete hash once more, with all the keys and their related values, not just the ones which have changed.

Deleting a Hosting Plan or Custom Package

Reference: Renewing/Upgrading/Downgrading/Deleting a Web Hosting package >>

Simply call del() under the appropriate HostingOrder class with the appropriate orderid.

Renewing a Hosting Plan or Custom Package

Reference: Renewing/Upgrading/Downgrading/Deleting a Web Hosting package >>

Simply call renew() under the appropriate HostingOrder class with the appropriate orderid and the months to renew for.

IMPORTANT

Tags: Alternate Location, Api, Budget, Custom Package, First call, Hash, Hashes, Hosting Package, Hosting Plan, Hosting Plans, Important Information, Local Store, Plan Id, Product Key, Product Keys, Serial Number, Web Hosting package

Filed in Sample API Flow with 0 Comments

14 Aug 10 Debugging API Calls and Retrieving the XML Sent / Recieved by our Server

The Debug API Parameters interface allows you to enable/disable API Call Debugging, emulate individual API calls and retrieve the XML Sent and Received by our server to compare with those returned by the specific emulator for debugging. Follow the process outlined below to commence this process:

1. Login into your Reseller Control Panel from http://manage.gossimer.biz/reseller

2. Click on Settings -> API -> Debug Your API Calls

3. Select the API method (any one or all) that you want to debug and click on the Start Debugging button.

4. Mention the last n calls (between 1 to 1000) that you want us to record by mentioning a value in the text box provided.

If you have already integrated with one of our API Kits and are facing an error that you wish to debug, then proceed to the next step.

If however, you are testing our API and wish to emulate API calls, then you may do so by selecting any of the PHP API Kits that we have deployed, by clicking on it (at the bottom of the interface). Clicking on any of the API Kits link will open the respective emulator in a new browser window.

6. Once you have tried a few calls, you may compare the XML Sent/Received with the ones logged in the system, by clicking on the Refresh button in the previous browser window.

7. Once you have completed your debugging exercise, turn off Debugging by clicking on the Stop Debugging button.

IMPORTANT

Turning on debugging for you API calls will slow them down significantly. Please turn debugging off as soon as possible to
maintain optimal performance.
Since enabling debugging also increases the load on our server, it will automatically be turned off after 1 hour.
Turning Debugging Off deletes the API log file, so please be sure to save the content of the textbox if you wish to refer to it later.

Troubleshooting Errors

In case you encounter an error message, please read the following links:

If you continue to face an error message, please contact our Support Team at support@gossimer.com.

Tags: Api, Browser Window, Emulator, Error Message, Exercise, Interface, New Browser, Optimal Performance, Parameters, Php, Reseller Control Panel, Xml

Filed in Emulate and Debug your API Calls with 0 Comments

13 Aug 10 Change Log

Changes in version 3.10

Java Docs updated

Changes related to classes and methods:

New Classes and Methods

Domains Kit

New Class Name New Method

ThirdLevelDotUk String invoiceOption

ThirdLevelDotUk String existingEndTime

New Parameters introduced in Existing Methods

Other Products Kit

Class Name Method Name New Parameters

EngageOrder renew String invoiceOption

EngageOrder renew String existingEndTime

Deprecated Parameters in Methods

Domains Kit

Class Name Method Name Deprecated Parameters

ZoneOrder add "No Of Records" in DomainHash

Deprecated Methods

Domains Kit

Class Name Deprecated Method Suggested Class Suggested Method

DomContact addDefaultContact DomContact addDefaultContacts

DomContact add DomContact addContact

DomContact list DomContact listByType

DomContactExt isValidRegistrantContact DomContactExt isValidContact

DomOrder transferDomain DomOrder addTransferDomain

DomOrder add DomOrder registerDomain

ZoneOrder mod ZoneOrder Functionality not required anymore

DotEu tradeDomain DotEu trade

DotEu transferDomain DotEu transfer

DotEu add DomOrder registerDomain

Core Kit

Class Name Deprecated Method Suggested Class Suggested Method

Customer addCustomer Customer signUp

Customer modDetails Customer mod

Reseller addReseller Reseller signUp

Reseller modDetails Reseller mod

Reseller addResellerWithStateId Reseller Functionality not required anymore

OrderSetup getResellerSlabPercentageForProducts OrderSetup Functionality not required anymore

OrderSetup getCustomerSlabPercentage OrderSetup Functionality not required anymore

Changes in version 3.9

Java Docs updated

Changes related to classes and methods:

The following method in the Domains Kit is deprecated and its use should be discontinued -

Deprecated method Class New method to be used

isValidRegistrantContact DomContactExt isValidContact

Changes in version 3.8

Java Docs updated

Changes related to classes and methods:

The following changes have been introduced under the DotEu class within the Domains Kit -
The following new methods have been introduced under DigitalCertificateOrder class within the Other Products Kit -
- enrollForThawteCertificate
- reissue
- renew
- checkDigitalCertificateStatus
- del
- cancelDigicertOrder
- changeDigicertPassword
- addAdditionalLicenses
- getDetails
- getDetailsByDomain
- getOrderIdByDomain

Changes in version 3.7

Java Docs updated

Changes related to classes and methods:

Some old parameters have been removed and new parameters introduced in their place under the following methods -

LinuxHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

WindowsHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*, boolean ssl^#
mod	Hashtable orderParams	String packagekey^*, boolean ssl^#, int excessBandwidth^##
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##
getModPricing	Hashtable orderParams	String packageKey^*, boolean ssl^#, int execessBandwidth^##

MailHostingOrder Class
Method	Old Parameter	New Parameters
add	Hashtable orderParams	String packageKey^*
mod	Hashtable orderHash	String packagekey^, int additionalMailBoxes^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*
getModPricing	Hashtable orderParams	String packageKey^, int additionalMailBoxes^*

SiteBuilder Class
Method	Old Parameter	New Parameters
mod	Hashtable orderParams	String packageKey^*
getMonthlyCostAndValidate	Hashtable orderParams	String packageKey^*

NOTE:
^* packageKey will be the Identifier Key of the Plan (plan1, plan2, plan3, plan4) for which the Order needs to be added/modified.

^# ssl will be true or false depending whether the user wants Dedicated IP / SSL for the Order placed.

^## excessBandwidth is the Bandwidth which the user wants over and above the Bandwidth of the Order’s current plan.

^** additionalMailBoxes is the number of additional mail boxes over and above the existing ones in blocks of 100 accounts.

The following classes and their methods are removed:

LinuxHostingPlanOnlyOrder
WindowsHostingPlanOnlyOrder
MailHostingPlanOnlyOrder

The SiteBuilderLite class has been renamed to SiteBuilder.

Two new methods, mod and signUp, have been introduced under the Reseller and Customer classes.

Code for registerDomain method in PERL Domains Kit has been modified.

The return type of the ListByType method of DomContact class in the Domains Kit has been changed to Hashtable from Vector.

Changes in version 3.6

Java Docs updated

Changes related to classes and methods:

New methods have been added in the Core Kit under the following class:

getProductMetadata – Product class
New methods have been added in the Domains Kit under the following classes:
getDefaultContactId – DomContactExt class
listByType – DomContact class
addTransferDomain – DomOrder class
changePrivacyProtectionStatus – DomOrder class
registerDomain – DomOrder class
Changes to the DomOrder class in Domains Kit:

The following methods in the Domains Kit are deprecated and their use should be discontinued:

Deprecated method	Class	New method to be used

add	DomContact	addContact
addDefaultContact	DomContact	addDefaultContacts
list	DomContact	listByType
add	DomOrder	registerDomain
transferDomain	DomOrder	addTransferDomain
transferDomainWithoutValidation	DomOrder	addTransferDomain
addTransferDomainWithoutvalidation	DomOrder	addTransferDomain
add	DotEu	registerDomain in DomOrder class

IMPORTANT

While these methods are currently available, they are no longer supported and may be discontinued in the near future.

New methods have been added in the Hosting Kit under the following class:

getHostingMetaData – WebHostingOrderData class

Changes to classes in the Hosting Kit:

The invoiceOption parameter has been added to the add method of MailHostingPlanOnlyOrder, WindowsHostingPlanOnlyOrder and LinuxHostingPlanOnlyOrder classes

Changes in version 3.5

Java Docs updated

Changes related to classes and functions:

New functions have been added in the Core Kit under the following classes:

getList – Country class
getStateListForCountry – Country class
getDetails – Order class
addResellerWithStateId – Reseller class
An extra option called Supersite is added in the getDetails function of the Reseller class in the Core Kit.
A new class LegalAgreement is added with the following methods under the Core Kit:
getRegistrantAgreement
getProductCategory
getAgreement
getAllAgreements
A new function has been added in the Domains Kit under the following class:
addCoopContact – DotCoopContact class
The following functions in the DomOrder class in the Domains Kit are changed to show the Invoice options also:
validateDomainRegistrationParams
validateDomainTransferParams
addWithoutValidation

Changes in version 3.4

Java Docs Updated

New Classes introduced in all Kits:

Core Kit

TaxService
getApplicableTaxes
getHashedTaxRules
Domains Kit

DotEu
    getEUCountryList
    tradeDomain
    transferDomain
    add
    isEUCountry

DotEuContact
    mod
    add
    addEuDefaultContact

DomOrder
    validateDomainRegistrationParams
    validateDomainTransferParams
    addTransferDomainWithoutvalidation
    addWithoutValidation
Hosting Kit

WindowsHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

LinuxHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount

MailHostingPlanOnlyOrder
    getDetails
    getDetailsByDomain
    getOrderIdByDomain
    add
    mod
    renew
    del
    getMonthlyCostAndValidate
    getModPricing
    getDeletionRefundAmount
    list

MailHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

WindowsHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap

LinuxHostingSetup
    getHostingKeyDisplayName
    getHostingParamsDisplayName
    getPricingKeyPricingParamMap
Other Products Kit

DigitalCertificateOrder
    add
    getCertPrice

SiteBuilderSetup
    getPricingKeyPricingParamMap

EngageSetup
    getPricingKeyPricingParamMap

Changes in version 3.3

3 new functions have been added in the Core Kit under the following classes:

authenticateCustomerId – Customer class
login – Customer class
getOrderIdByDomainAndProductCategory – Order class

Bug Fix – A minor Java Script problem was causing the frame links in the examples to not work in some browsers like Mozilla and Opera.

Changes in version 3.2.1

WSDL Endpoint changed

Changes in version 3.2

New methods added viz. Order.removeCustomerLock, Order.getLockList

Changes in version 3.1

Minor bugs in WSDL files fixed.

Version 3.0 Released

Extensive changes made. Please download the kit and read the appropriate Javadocs for details.

Changes in version 2.6

Added the method Customer.delete() which allows you to delete a Customer

Added the method DomOrder.cancelTransferRequest() which allows you to cancel the transfer-in request for a domain name

Added the method Order.sendRfa() which allows you to re/send the email asking for transfer-in approval for domain names.

Changes in version 2.5

Bug fix in Modify Customer Details and Modify Contact Details forms

More details in the Javadocs for DomOrder.getDetails()

Link to new Demo Server added.

Version 2.3

Perl API KIT added

Tags: Api, Java, Perl, SSL

Filed in Perl API Kit with 0 Comments

31 Aug 10 .NET API Kit and Integration Guide

30 Aug 10 Data Validation of Parameters passed in an API Method Call

29 Aug 10 Emulating API Calls

29 Aug 10 General Finance Setting

23 Aug 10 Sample Domain Names API Flow and some Notes

22 Aug 10 Transferring your .EU Domain Name

22 Aug 10 Add / Modify a PayPal Direct Payment API Gateway

22 Aug 10 Read this FIRST: Reseller Account Startup Guide

22 Aug 10 IMPORTANT: API Abuse

21 Aug 10 Read This FIRST – General API Integration Instructions

19 Aug 10 PHP API Kit and Integration Guide

17 Aug 10 Sample Hosting API Flow and some Notes

14 Aug 10 Debugging API Calls and Retrieving the XML Sent / Recieved by our Server

13 Aug 10 Change Log

13 Aug 10 Transferring your .UK Domain Name

Recent Posts

Some good Links

Favorite Gossimer Links

Categories

Tags

Gossimer in the News

Gossimer Promotions and Announcements

01 Sep 10 Change Log

31 Aug 10 .NET API Kit and Integration Guide

30 Aug 10 Data Validation of Parameters passed in an API Method Call

29 Aug 10 Emulating API Calls

29 Aug 10 General Finance Setting

25 Aug 10 About Authorize.Net

24 Aug 10 Change Log

23 Aug 10 Sample Domain Names API Flow and some Notes

22 Aug 10 Transferring your .EU Domain Name

22 Aug 10 Add / Modify a PayPal Direct Payment API Gateway

22 Aug 10 Read this FIRST: Reseller Account Startup Guide

22 Aug 10 IMPORTANT: API Abuse

21 Aug 10 Managing Managed DNS, Web Hosting, Email Hosting, Live Chat, Website Builder Orders through your API integration

21 Aug 10 Read This FIRST – General API Integration Instructions

19 Aug 10 PHP API Kit and Integration Guide

19 Aug 10 Change Log

17 Aug 10 Sample Hosting API Flow and some Notes

14 Aug 10 Debugging API Calls and Retrieving the XML Sent / Recieved by our Server

13 Aug 10 Change Log

13 Aug 10 Transferring your .UK Domain Name

Recent Posts

Some good Links

Favorite Gossimer Links

Categories

Tags

Gossimer in the News

Gossimer Promotions and Announcements