> 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/api-builder/endpoint-response-outputs.md).

# Endpoint Response Outputs

In Jet Admin's RestAPI Builder, endpoints can return data in four different formats: JSON, XML, Text, and Blob. Each format serves specific purposes and is compatible with Jet Admin's capabilities for accepting data from endpoints.

<figure><img src="/files/8BmOJscqib1grTGNzFke" alt=""><figcaption></figcaption></figure>

### **JSON (JavaScript Object Notation)**

**When to Use:** Jet Admin accepts JSON-formatted data from endpoints when it needs to retrieve structured data, such as objects or arrays.

### **XML (eXtensible Markup Language)**

**When to Use:** If endpoints return data in XML format, Jet Admin can handle it effectively. XML format is used when the data requires a hierarchical structure and needs to be compatible with systems using this format.

### **Text**

**When to Use:** Jet Admin accepts text data from endpoints for various purposes, including returning simple messages, logs, or raw content.

### **Blob (Binary Large Object)**

**When to Use:** When endpoints return binary data that needs to be downloaded or processed by the client, Jet Admin accepts Blob format. This allows for seamless handling and management of Blob data within the platform.

{% hint style="info" %}
**Choosing the Right Response Output:**

Select the appropriate response output format (JSON, XML, Text, or Blob) based on the structure and type of data returned by your endpoints.
{% endhint %}

By accepting data in these four response output formats, Jet Admin enables efficient processing, visualization, and use of data received from endpoints within the platform.


---

# 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.jetadmin.io/user-guide/data/api-builder/endpoint-response-outputs.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.