Invoke public and private APIs
Access an API
Restlet Cloud web APIs are either public or private. This affects the way you access the Web API's documentation, including access tokens, but does not have an affect on invoking the API at runtime.
Access a private API
In order to browse a private web API's documentation and get your access tokens, you need to be a member of the API. To see how to create web API members, please visit the User Groups page.
Navigate to the API's overview. If you are a member of the API, it will appear in your Dashboard.
Select an Endpoint in the left panel. The central panel displays your access tokens.
Access a public API
Public web APIs can be browsed by anyone, without authentication. A public API is not necessarily open to anyone at runtime. This is configured from the User Groups page.
Basic authentication access tokens
To view your security tokens to access an API, select an Endpoint from the list in the left panel of the Overview tab. The central panel displays your access tokens.
Invoke an API
In order to invoke an API, you must belong to one of the API's consumer groups with sufficient runtime permissions.
However, some APIs are open to anyone without authentication.
To see how to configure a web API's runtime permissions, including opening an API to anyone, please visit the User Groups page.
Making HTTP calls
Restlet Cloud web APIs respect the principles of REST. Therefore, CRUD operations can be performed on resources exposed by the APIs.
Invoking a collection resource
A collection resource is typically identified by a URL that ends in the name of a type of data, in plural.
Sending a GET request to this URL will list all Contacts stored by the server.
Sending POST request to this URL with result in the creation of a new Contact, and the payload of the request will be used to initialise the Contact's properties.
Invoking an element resource
An element resource is typically identified by a URL that ends in the name of a type of data followed by the unique identifier of the element.
Sending a GET request to this URL will list the details of the Contact whose identifier is 1234.
Sending a PUT request to this URL will update the Contact whose identifier is 1234, the update will be based on the payload of the request.
Sending a DELETE request to this URL will delete the Contact whose identifier is 1234.
Entity stores exposed through a web API support a rich query language for collection resources. The query language is based on a set of special parameters that are passed as query parameters in HTTP GET requests on collection resources.
The results of a GET request on a collection resource can be filtered based on the values of properties of the representations returned.
By default, every property of a representation can be used as a filter criteria.
Currently, the only supported comparison operator is equality.
All filter criteria in a GET request are combined with AND logic.
Note: When querying an API for String values, if there is a space in the property value, the query parameter must be surrounded by double quotes e.g.
GET https://fireworks.restlet.net/v1/towns/?City="Jackson Hole".
$sort query parameter is used to sort results in either ascending or descending order based on the value of a property. Multiple sort criteria can be used simultaneously.
Ascending order is used by default if none is specified.
GET https://<endpoint>/<collection-name>/?$sort=<property1> <sort-order>,<property2> <sort-order>,...
GET https://myapi.restlet.net/v1/messages/?$sort=creationDate ASC,size DESC
In this request, we sort a collection of messages by their creation date in ascending order, and then by size in descending order.
In case you have many entries stored in a collection, you may not want to read them all at once when invoking the API. The
$size query parameters let you specify the size of a page, and which page number to load.
Note: Page numbers start from 0.
Restlet Cloud provides a total items count through headers for paginated APIs that import Entity Stores, SQL wrappers or Google Sheets wrappers. Here is a list of the available headers:
- X-Page-Count -> total number of pages
- X-page-Number -> page number
- X-Page-Size -> page capacity (maximum number of items per page is set to 25)
- X-Total-Count -> total number of items
Configuring server and client-side caching will allow you to improve response time for your APIs. As an API is invoked, Restlet Cloud adds information in the HTTP header. The validity duration of these data can be set from your API's Settings tab. You can thus increase the data conservation duration and avoid performing requests on data you already collected.
This feature is disabled by default. If you want to specify how long GET responses should be cached by our HTTP client and the Restlet Cloud server-side cache, select the Enabled checkbox and specify the time in minutes, hours, days or months.
You will need to redeploy your API once you have configured your cache in order for your modifications to be saved.