> For the complete documentation index, see [llms.txt](https://glyue.docs.sandboxbanking.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://glyue.docs.sandboxbanking.com/tutorials/building-a-restful-crud-web-service/1.-integration-setup.md).
# 1. Integration Setup
### Add Integration
We will setup an integration for each of the services listed below to read and/or write from/to vault. We will set up and name our vault **data** in the next guide.
* Get all customers
* Get a specific customer by Id
* Create a customer
* Update a customer
* Delete a customer
To create an integration, log into Integration Gateway, if necessary and navigate to the **Build** page. The default component for the **Build** page is the **Integration** table, therefore, click on the **Add Row** button.
This integration will retrieve all customers from the **data** vault. Fill in the path name and the description field with the following information.
* **Path Name** - get\_all\_customers
* **Description** - This integration will retrieve all customers from the data vault.
Click on the **Save** button below.
Create an integration for the remaining services as shown in the image below.
### Add Integration Config
{% hint style="warning" %}
To perform the following steps, the user must be a Integration Gateway administrator for the target environment.
{% endhint %}
Log into Integration Gateway, if necessary and navigate to the **Admin** site.
Scroll to the **Configuration** section, locate **Integration Config** and click **Add**.
On the **Add** **Integration Config** page, select the integration `get_all_customers` from the Integration dropdown menu and check the box **Store payloads in run history for x days**.
Click on the **Save** button below**.**
Add an integration config for each integration we had created.
---
# 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://glyue.docs.sandboxbanking.com/tutorials/building-a-restful-crud-web-service/1.-integration-setup.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.
