> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/data-binding/data-binding-types/bind-data-to-ui-multiple-requests.md).

# Bind multiple API requests to one screen

If you create several API requests, you can bind them to a single screen in the app, so it can interact with data from different requests. This allows to create a screen with several lists, for instance.

This tutorial is a continuation after you have retrieved data from a database. If you haven't done that yet, check out:

👉 [Get data from any database with REST API](/connect-api/set-up-api-requests/creating-an-api-collection/airtable/set-up-an-api-get-request-for-list-page-airtable.md)

{% hint style="info" %}
We are using [this design file](https://www.figma.com/community/file/1032382259074385867/Bravo-Sample%3A-Multiple-API-Requests) and [this Airtable](https://airtable.com/shrWagUN5OboNmFAK) base for the tutorial. In this example, we're displaying three lists in a single screen. Each list has the data from each of the tables.
{% endhint %}

## Binding data from multiple requests

First, you'll need to have several API requests created in the Data Collections section. In this case, we have three GET requests that return a list of items.

![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MXpqEanvOhm8vMtIH8i%2F-MlB39Na72rkZIkdq06_%2F-MlB569yaGRlUIvtK3pE%2Fimagen.png?alt=media\&token=96376f12-1000-4357-83bf-5ea34888c44a)

We'll use the data from these requests in the Data Binding section. In our sample design file, we have three list [containers](broken://pages/-MfgiCryp4HdueTetP8C). We'll bind each container to the list data from each API request.

![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MXpqEanvOhm8vMtIH8i%2F-MlBCC-Qv0gcTpKFiTva%2F-MlBE1jx6Socezq2lLj1%2FGrabacio%CC%81n%20de%20pantalla%202021-09-30%20a%20las%2017.11.36.gif?alt=media\&token=2690f744-5eb2-4162-aea6-ecceaf99b724)

After binding the list containers, we'll bind the individual UI elements inside each list. Once an API collection and a request are selected for a UI element, the same will be automatically selected for all elements in the same container. However, they can be changed if needed.

![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MXpqEanvOhm8vMtIH8i%2F-MlBCC-Qv0gcTpKFiTva%2F-MlBEAbXKo1GUL-h7lBg%2FGrabacio%CC%81n%20de%20pantalla%202021-09-30%20a%20las%2017.17.17.gif?alt=media\&token=1ed68753-3a53-4cc8-afe6-20fdca3e3a02)

{% hint style="info" %}
In addition to lists, you can also bind individual data items coming from different API requests. 

**For instance**: In this design example, you can bind individual text elements to the title on the screen, so these texts don't need to be changed statically in the design file, but rather fetched from the backend.
{% endhint %}


---

# 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.bravostudio.app/data-binding/data-binding-types/bind-data-to-ui-multiple-requests.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.