# Understanding CloudIO REST APIs

A REST resource in CloudIO can be any piece of information, ranging from a single data record to a collection of records. Each resource in the CloudIO REST API:

* is identified by a named URI
* is accessed using the standard HTTP POST method
* are used to interact with any datasource within CloudIO Platform

For example, you can:

* Obtain detailed information about any CloudIO datasource such as RaUsers or RaRoles
* Obtain detailed information about any application-specific datasource
* Perform a search on any datasource
* Insert, update or delete records

The prominent characteristics of the CloudIO REST API resources and architecture include:

* **Stateless**  Every request from the client to the server contains all the information necessary to understand the request along with the sessionId.
* **Caching** Since all the REST APIs are executed via a datasource and in real-time against a database, the results are not cacheable.
* **HTTP**  All REST APIs are accessed using the HTTP.
* **URI**  All REST APIs are named using a base URI that follows your CloudIO URI. For example, \[[https://host:port/api/Datasource\[/operation\](https://host:port/api/Datasource\[/operation)\\](https://host/:port/api/Datasource\[/operation]\(https://host:port/api/Datasource\[/operation\)/)] where operation is one of the following values—insert, update, delete, post or query


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cloudio.io/creating-datasources/working-with-datasources/accessing-data-sources-using-rest-api/understanding-cloudio-rest-apis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.