REST APIs

Since the API is based on REST principles, it's very easy to write and test applications. You can use your browser to access URLs, and you can use pretty much any HTTP client in any programming language to interact with the API.

This section provides all the basic information you need to use Cloud4Wi REST APIs.If you are getting started, then you have to follow the workflow below:

Get your API Secret.

Open the "Cloud4Wi API" application, ask for the API secret and agree to terms and conditions for the service.

Cloud4Wi REST APIs are based on REST principles, so you can easily interact with them regardless of the language you use.You can find some examples in the Developer Portal

Getting your API secret

Please note that in order to interact with the Cloud4Wi REST APIs, it is necessary to have an "API key" / "API Secret" pair.

You can get your API credentials by accessing the "Cloud4Wi API" page form the Marketplace section of the Admin Panel. The API key identifies a Tenant and cannot be changed. You can, however, change your API secret at any time by clicking on the Renew API Secret button in the "Cloud4Wi API" page. The API secret is a secret shared between Cloud4Wi and your application and for this reason, it must not be public in any case.

If you are using your account for the first time, you need to generate your API secret by clicking the "+" button and accepting terms of use for the API service.

Data scrolling and pagination

When you deal with a large number of records, you need to retrieve smaller chunks of data with multiple API calls.

Most of the API endpoints use the pagination method to move across multiple chunks of records, using the limit and offset parameters. The limit parameter determines the maximum number of records returned in a single API call. The offset parameter indicates the index of the first records to be retrieved.

Some API endpoints are designed to provide access to the data at a faster speed. This method requires you to use the ScrollId parameter, and it is available in the following endpoints: