You can download the API examples from the Abiquo 3.8 API Examples Archive. The example pages are named based on the REST option (e.g. GET) and the URL of the API resource and method, as well as the media types and formats.The API examples are simple cURL commands designed to help new developers get an overall picture of the Abiquo API. We also hope that the examples may be useful in providing information about the vitally important resource links that can be found in most Abiquo resources, but which present challenges in documentation.
We expect every user will have their preferred tools for making quick test requests, such as POSTman, or Advanced REST client and their own development languages. Therefore, we have tried to create consistent, easy to read examples to help you quickly translate the information in the documentation into actions in the real world of the Abiquo API.
In order to quickly and efficiently produce examples of most of the requests of the very expansive Abiquo API, we have taken advantage of the output of the Abiquo integration tests. This means that dummy entities, strange text strings or empty lists may at times appear in the examples. As there around 900 examples, the revision of these files is an ongoing project.
The integration tests may be run using HTTP with a localhost address on port 9000. To use the examples, you will need to change this, for example to use HTTPS, and replace the URL and port with those of of your Abiquo system. For example, https://my.abiquo.com/api. For simplicity, user and password authentication is shown in the examples. However, for production systems, OAuth is recommended. See Authentication.
To enable cut and paste to a shell, backslashes are placed at the end of each line to escape the new line. Requests should contain single quotation marks, not back ticks. Every effort has been made to ensure that single quotation marks are used in the examples, to enable copy and paste where required. However, you may achieve better results by checking and modifying the command in a text editor before pasting it in a shell. You should always use the version number with your media types in requests to the Abiquo API in order to avoid compatibilty issues in future versions.
To ensure JSON compatibility, double quotation marks are used in JSON strings. You can validate your data entities with JSON or XML formatters or checkers.
To achieve consistency for all request payloads, regardless of their length, we use a data file format in the examples. The cURL command has a -d parameter, which indicates the request payload. The \@ symbol means that the following text is a file name. To run the query, you can create a file with the name requestpayload.<format>, where format could be json, xml, text, etc. Or you could put the request payload inline. In this case, the easiest approach is to put the authentication line (-u user:password --verbose) above the payload line with a backslash at the end. The payload line should be -d followed by single quotation marks enclosing the data entity.
Put and post requests contain a request payload. We have made these payloads visible, rather than using file attachments, because we believe that they can provide useful information about the data entities involved in each query. However, you must remember that the payloads are not a specially designed template for creating a new resource or modifying a resource. For create requests, you may be able to find examples of simple entities by looking at requests made by the Abiquo UI. For modify requests, you should perform a get of an existing object and then make your changes. See Get Started with the Abiquo API. The Abiquo API will return posts in the accept media type you specify in your requests. When you use cURL, then the response payload will be raw data. You can then pipe this output to a formatter, such as xmllint, xmlindent or pjson. Or cut and paste to format it in an online tool.
So here is an example of how a cURL command might look for a test system, where the insecure -k connection is used with https.