Skip to content
Switch branches/tags
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


semantic-release Build Status PyPI - Python Version PyPI Documentation Status License: MIT PRs welcome

This module is a connector library for the insanely fast HEXONET Backend API. For further informations visit our homepage and do not hesitate to contact us.



  • Automatic IDN Domain name conversion to punycode (our API accepts only punycode format in commands)
  • Allows nested associative arrays in API commands to improve for bulk parameters
  • Connecting and communication with our API
  • Possibility to use a custom mechanism for debug mode
  • Several ways to access and deal with response data
  • Getting the command again returned together with the response
  • Sessionless communication
  • Session based communication
  • Possibility to save API session identifier in session
  • Configure a Proxy for API communication
  • Configure a Referer for API communication
  • High Performance Proxy Setup

High Performance Proxy Setup

Long distances to our main data center in Germany may result in high network latencies. If you encounter such problems, we highly recommend to use this setup, as it uses persistent connections to our API server and the overhead for connection establishments is omitted.

Step 1: Required Apache2 packages / modules

At least Apache version 2.2.9 is required.

The following Apache2 modules must be installed and activated:

ssl.conf # for HTTPs connection to our API server
ssl.load # for HTTPs connection to our API server

Step 2: Apache configuration

An example Apache configuration with binding to localhost:

    ServerAdmin webmaster@localhost
    ServerSignature Off
    SSLProxyEngine on
    ProxyPass /api/call.cgi min=1 max=2
    <Proxy *>
        Order Deny,Allow
        Deny from none
        Allow from all

After saving your configuration changes please restart the Apache webserver.

Step 3: Using this setup

from hexonet.apiconnector.apiclient import APIClient as AC

cl = AC()
cl.useHighPerformanceConnectionSetup() # Default Connection Setup would be used otherwise by default
cl.setCredentials('test.user', 'test.passw0rd')
r = cl.request({"COMMAND" => "StatusAccount"})

So, what happens in code behind the scenes? We communicate with localhost (so our proxy setup) that passes the requests to the HEXONET API. Of course we can't activate this setup by default as it is based on Steps 1 and 2. Otherwise connecting to our API wouldn't work.

Just in case the above port or ip address can't be used, use function setURL instead to set a different URL / Port. is the default URL for the High Performance Proxy Setup. e.g. $cl->setURL(""); would change the port. Configure that port also in the Apache Configuration (-> Step 2)!

Don't use https for that setup as it leads to slowing things down as of the https overhead of securing the connection. In this setup we just connect to localhost, so no direct outgoing network traffic using http. The apache configuration finally takes care passing it to https for the final communication to the HEXONET API.

Customize Logging / Outputs

When having the debug mode activated hexonet.apiconnector.logger will be used for doing outputs by default. Of course it could be of interest for integrators to look for a way of getting this replaced by a custom mechanism like forwarding things to a 3rd-party software, logging into file or whatever.

from hexonet.apiconnector.apiclient import APIClient as AC
# import your module from your custom namespace of course
from hexonet.apiconnector.customlogger import CustomLogger as CL

cl = AC()
# LIVE System would be used otherwise by default
# enable debug output (inactive by default)
# provide your custom logger mechanism
cl.setCredentials("test.user", "test.passw0rd")
r = cl.request({"COMMAND" => "StatusAccount"})

NOTE: Find an example for a custom logger class implementation in hexonet/apiconnector/ If you have questions, feel free to open a github issue.

How to use this module in your project

All you need to know, can be found here.


Please read our development guide for details on our code of conduct, and the process for submitting pull requests to us.

pip3 install -e .


List of responsible developers can be found here

See also the list of contributors who participated in this project.


This project is licensed under the MIT License - see the LICENSE file for details.