Requests

Use HTTP requests to read and write data from https://api.hostingreborn.com/. GET requests are used to retrieve information, POST requests to send information.

Most modern languages include libraries for handling HTTP requests and responses. It is assumed you understand HTTP requests and responses as it is beyond the scope of this documentation to explain such underlying principles.

Example: retrieving the current bandwidth price

GET /price/get_bandwidth/
<?xml version="1.0" encoding="utf-8"?>
<bandwidthprice>50</bandwidthprice>
	

Authenticated Requests

All functions are marked as public or private. Public functions can be accessed without any special permission.

Private requests require authentication in the form of a key argument. Each key is uniquely identified with a given account. You can retrieve your key from your API access management screen or through the API itself.

Limits

You can make 10,000 requests per IP address per month. This is intended to cover casual, personal or development uses. Further requests will return an access exception.

We will soon introduce the option to purchase additional request credits associated with your account. In the meantime, please contact us if you need to make more than 10,000 requests from a given IP address.

Common request value data types

Function documentation may refer to argument values as being of a certain data type. These are listed here, with the possible values they can accept.

Boolean

Boolean values are used as on/off switches. These are not case-sensitive. Note that we don't differentiate between the integer value 1 and the string value "1" as HTTP requests can be nothing but strings.

You may find that anything that is not an 'on' value is treated as an 'off' value. This is undocumented (unofficial) behaviour that you should not depend upon as it may change in the future and break your program.

'On' values
  • 1
  • true
  • on
  • yes
'Off' values
  • 0
  • false
  • off
  • no
  • blank
  1. Index
  2. About the API

    1. Summary
    2. Specification
    3. Do not use undocumented features
    4. Change log
  3. Using the API

    1. Requests
      1. Authenticated requests
      2. Limits
      3. Common request value data types
    2. Understanding responses
      1. HTTP status codes used
      2. Exceptions
        1. access
        2. account
        3. database
        4. hostingaccount
        5. server
        6. system
  4. Function reference