> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/user-guide/data-sources/apis/rest-api.md).

# Rest API

Connect Jet Admin to any REST API.

In addition to ready-to-use integrations, Jet Admin allows you to use REST API to connect to any tool you need to integrate into your workflow. 

{% embed url="<https://youtu.be/MlNuOS2sffQ>" %}

To connect a REST API or another resource, first select Add Resource from the project menu to open the resource selection pane:

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F1DdjwJCkQNWSDbZM714v%2Fimage.png?alt=media&amp;token=59fb4a6e-9030-41d4-bada-e9b20f8cbdd2" alt=""><figcaption></figcaption></figure>

You can also implement your own custom API using API Builder. For example, you can set up GET or POST requests to retrieve or update data based on your application's needs.

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F9aIYXU097ARUwiQ019DQ%2Fimage.png?alt=media&amp;token=aa8e7140-587b-40b4-b4fb-f20bce6c4d99" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/-MAARNCnpjDL0xKCL8Pp" %}
[Making API requests](/user-guide/sql-queries-and-api-requests/make-an-http-request.md)
{% endcontent-ref %}

### Connect custom API resource

Let's start with implementing **Rest API**, select it from the list of available resources, and specify the general information that will use for all API requests for this resource:&#x20;

* **Resource name** – unique name that indicates API resource in Jet Admin.
* **Base URL** – URL that will use for all requests for this resource (if you want to use different URL, create different resources for each URL).
* **Authentication** –  used to authenticate requests: [Bearer token](/user-guide/data-sources/apis/rest-api/bearer-token.md), [Basic Auth](/user-guide/data-sources/apis/rest-api/basic-authentication.md), [OAuth 2.0](/user-guide/data-sources/apis/rest-api/oauth-2.0.md).

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LQ08RFAKZvFADEiXKFy%2F-MEEy8r9TeZrjti2WcdH%2F-MEF0ooHWOzlsbGq1cEl%2Fimage.png?alt=media\&token=877903df-16f6-4cd0-b3e8-bd0284ae3504)

Once you have connected a REST API, you will need to configure the requests in the Data Editor. For more information, please look at the [Data Editor documentation here:](https://docs.jetadmin.io/user-guide/data/make-an-http-request)

{% content-ref url="/pages/-MAARNCnpjDL0xKCL8Pp" %}
[Making API requests](/user-guide/sql-queries-and-api-requests/make-an-http-request.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/user-guide/data-sources/apis/rest-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.