> For the complete documentation index, see [llms.txt](https://docs.cosmocloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cosmocloud.io/resources/apis.md).

# APIs

REST APIs are the essence of Backend Development, the most used way for your frontend (client) to talk to your backend layer.

## Creating APIs

There are various ways to create APIs in your Cosmocloud project -

* [Using Templates](#using-templates)
* [Building from Scratch](#building-from-scratch)

### Using Templates <a href="#using-templates" id="using-templates"></a>

You can quickly start creating the APIs and their corresponding models using use-case based Templates. These help you in auto generating convention based APIs and models for faster productivity.

You can then [customise](#customising-api-flow-logic) and edit any API or Model that is created via Templates.

#### Available Templates <a href="#available-templates" id="available-templates"></a>

* Entity CRUD APIs
* Entity Search APIs
* Fetch / Upload Media APIs

### Building from Scratch <a href="#building-from-scratch" id="building-from-scratch"></a>

This is the method where you can start building your APIs from scratch. This will help you in customising your API endpoints, request methods as well as any [Query Param](/resources/models.md#query-params-model) Models / [Request Body](/resources/models.md#request-body-model) Models you want to use.

## Customising API Flow Logic

After creating an API, you can create or customise the APIs logic, using Cosmocloud's [Flow Builder](/flow-builder.md). To be able to customise this -

1. Navigate to APIs listing page from **Application Layer -> APIs**.
2. Open the API you want to edit.
3. Switch to the **Flow** tab of the particular API.
4. Start editing!

{% hint style="info" %}
Checkout Cosmocloud's [Flow Builder](/flow-builder.md) for more details on customising flows in Cosmocloud.
{% endhint %}

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-hidden></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Creating Flows</strong></td><td></td><td></td><td><a href="/pages/8z0rUKU7stKO2y2rf6fw">/pages/8z0rUKU7stKO2y2rf6fw</a></td></tr><tr><td><strong>Magical Autocomplete</strong></td><td></td><td></td><td><a href="/pages/RJ2ouQTCjKiUMsBHftne">/pages/RJ2ouQTCjKiUMsBHftne</a></td></tr><tr><td><strong>Node Types</strong></td><td></td><td></td><td><a href="/pages/dG5YfkRM4ULDTeTC9n14">/pages/dG5YfkRM4ULDTeTC9n14</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.cosmocloud.io/resources/apis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.