> 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/databases/xano.md).
# Xano
This guide explains how to quickly connect Xano back-end to a Jet Admin front-end.
Xano is the fastest way to build a powerful, scalable backend for your app without code. We will guide you how you can quickly connect Xano back-end to Jet Admin.
[Create a new Project in Jet Admin](https://app.jetadmin.io/) if you don't have one. Choose Xano as a Data Source that you would like to connect.
Copy **API Group Base URL** from Xano to Jet Admin
In case if you would like to protect **API endpoints** from unauthorized access, you can learn how to set it up in the video and get an **Access token**:
{% embed url="" %}
Once authentication endpoint is set up, **generate an Auth Token** for **Jet Admin** integration.
{% hint style="warning" %}
Make sure to **set expiration to "0"** in endpoint *Create Authentication Token step* to make Auth Token permanent.
{% endhint %}
Copy **Authorization token** to **Authorization header** in Jet Admin.
Next, choose Data Sync, which allows you to do SQL queries, and blend and join data from 30+ data sources.
Copy authToken value to insert it in Jet Admin.
#### Check out our Tutorials: How to build a Custom CRM using Xano
{% embed url="" %}
{% embed url="" %}
---
# 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/databases/xano.md?ask=&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.
