You cannot register this service. Contact Support

API dinahosting

All the commands you need
If you have doubts, we help you for free

api.cta__h1
Lorenzo and Ander. Support

Dinahosting API

All the commands you need to implement your own sales platform and manage domains, web hosting, VPS... using your interface, automating and planning actions in one or more services.

  • API in PDF

    Download Last update 17/07/2026 10:51:10

  • File library

    Download Dinahosting HTTP_Request libary files

API documentation

All of the documentation on dinahosting’s API and the list of the commands available are shown below. Each command includes a detailed description of how it works, the settings it accepts and the possible types of responses.

By selecting a command, a request builder and response simulator will also be displayed, which will enable you to test how to call the API and see the actual response returned by the server.

List of commands

List of errors

Types of requests

Our API accepts different request formats so that you can choose the one that best suits your integration. Each type sets the way in which data and the instructions to the server are sent.

Jsonrpc

Json Remote Procedure Call request.Special HTTP request that sends JSON encoded arguments and expects a JSON encoded response.Characteristics and requeriments:
  • Request data sent through HTTP POST query .
  • Content-type indicated as "application/json" on HTTP headers.
  • User login data must be sent at "Authorization: Basic" on HTTP headers .
  • Parameters can be sent in any order. Keys are case sensitive.
  • Only used with Jsonrpc response type.
  • Simulation mode only available on web server at https://dinahosting.com/api/.

Simple

Simple HTTP REQUEST .Standard HTTP request that sends key=value pairs in a URL encoded request.Characteristics and requeriments:
  • Request data sent through a standard HTTP GET or POST query .
  • User login authentication data might be sent at "Authorization: Basic" on HTTP headers or in request parameters AUTH_USER and AUTH_PWD.
  • Parameters can be sent in any order. Keys are case sensitive.
  • Can be used with any responseType.
  • Can force client-side activation of simulation mode. Just add a boolean parameter SIMULATE=true to the request.
Example: https://dinahosting.com/special/api.php?AUTH_USER=yourUser&AUTH_PWD=yourPass&command=System_GetRequestTypes&responseType=Xml&SIMULATE=false

Xmlrpc

Standard Xml Remote Procedure Call request.Special HTTP request that sends XML encoded arguments and expects a XML encoded response.Characteristics and requeriments:
  • Request data sent through HTTP POST query .
  • Content-type indicated as "application/xml" on HTTP headers.
  • User login data must be sent at "Authorization: Basic" on HTTP headers .
  • Parameters must arrive ordered, as described in method signature.
  • Only used with Xmlrpc response type.
  • Simulation mode only available on web server at https://dinahosting.com/api/ .

Response types

You can select the response format you prefer for receiving the information returned by the API. This allows you to easily process the results on your application, regardless of the language or environment.

Xml

Extensible markup language response. Multi-plataform language. Lighter than our XmlRpc. Used with standard (Simple) HTTP requests.

Json

JavaScript Object Notation response. Lightweight, multi-plataform, easy parseable response type. Used with standard (Simple) HTTP requests.

Test

Testing response. Returns valid PHP code. Harder to parse than Json or XML. Used with standard (Simple) HTTP requests.

Jsonrpc

JavaScript Object Notation Remote procedure call response. Same as standard Json . Only for JsonRpc requests.

Simple

Simple key value plain text response. Lightest response, but it isn't standard. Parsing may be troublesome if response data is complex. Useful for testing purposes. Used with standard (Simple) HTTP requests.

Xmlrpc

Extensible markup language Remote procedure call response. Standard XML response built with Zend XmlRpc server. Easy to parse with Zend XmlRpc client, but heavier communication. Recommended only for XmlRpc requests.

Debug

Debuging response. Used with standard (Simple) HTTP requests.

Request use of the API

Do you want to use our API? All you need is an active account at dinahosting and fill out the following form to enable your credentials.

Introduce el texto mostrado en la imagen