Session management

Revision as of 22:13, 1 August 2017 by Netim (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Open / close sessions

Each time, you connect the control panel or use the Login function of the API, a session is opened into our system.


Each reseller can open by default 10 concurrent sessions.
All opened sessions will be closed automaticaly after 20 minutes of inactivity.

With the API, you must first use the Login (API version 1) or SessionOpen (API version 2) function which will return a session ID. This value must be provided to all subsequent functions in order to autorize the requests. Any opened session will remain alive until a call to the Logout (API version 1) ou SessionClose (API version 2) function which will close it.

It means that you must explicitly close all opened sessions. In this way, you should catch all exception in your code in order close properly the opened session (even if your code fails)

Synchronous and Asynchronous sessions

This notion corresponds to the mode of execution of an operation in our system.

When the session is asynchronous, all operations are processed later by the system. Then the reseller have to record the operation number to follow up at a later stage.

When the session is synchronous, all operations are processed at the time of submission. Consequently, the result will be immediate when possible or pending if the operation is inherently asynchronous. The reseller obtains in the return of the function the status of the operation and can itself process the result according to the cases (synchronously or asynchronously).

With API <=1.5, sessions are systematically asynchronous
With API > 2.0, sessions are synchronous by default. A session can change its status in real time with the function SessionSetPreference

It is therefore up to the reseller to determine whether he wants to work in synchronous or asynchronous mode according to his own management of the operations. In particular, he must be aware that the processing time in synchronous mode may take several seconds.

Sessions follow-up

Any user can follow the session history in the Web Interface, section "Account" then "Access management"

The connection list contains the following information:

Connection date 
IP used
Connection attempt

IP Restriction

At the Web Interface level

The reseller can set a restriction by IP address to the interface

Setup an IP Restriction

At the API level

Setting the IP restriction at the API level is not yet available online

Please contact us to set these restrictions on our firewall.

Common errors

M0101 - Bad login / password combinaison

Check your username and password. Also check that you are not using your credential for production into the OTE system and vice et versa.

M0103 - Too much sessions are already opened You can't log anymore because you have too many opened sessions.

You have two possibilities:

Wait 20 minutes in order to have them automaticaly closed by our system
Contact us in order to flush your connexion pool or increase the maximum number of sessions allowed
Personal tools

Your account
Domain names
Shared Hosting
Old Hosting offers
SSL Certificates
Contact Us