> 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-retrieval-api-against-fis-codeconnect/1.-integration-setup.md).

# 1. Integration Setup

**Creating the Integration**

\
The first step to building a Customer360 retrieval API would be to create a new row on the integration table of the build page.\
\
Navigate to the Build page and change the current component to the **Integration** option.

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2F1Ab6sQKclzdDyioFfyZl%2Fimage.png?alt=media&amp;token=2ac67cf7-8a48-4884-8d81-30ee440815f7" alt=""><figcaption></figcaption></figure>

\
Once there, press the "Add Row" button to create the integration. You'll need to provide a **Path Name** as well as a **description** in order to save the added integration using the save button on the bottom of the screen.<br>

**Configuring the Integration**\
\
\&#xNAN;*To complete this step, you'll need access to the* Integration Gateway *Admin Page.*\
\
Navigate to the Admin Page using the panel on the left hand side of the screen. Scroll down until you find the configuration item labelled "Integration Configs" and click the "Add New" button next to it.\
\
Choose the appropriate integration name that you created earlier and choose the settings you'd like configured for this integration. Check the "Store payloads in run history" box to trace the data when building and using the integration.\
\
From here, find the configuration item labelled "Adapter Configs: FIS IBS (Code Connect)**"** in the left-hand side menu and click to add a new item.\
\
\&#xNAN;*`If you are building an integration to a different CodeConnect core, choose the appropriate item; i.e. "Adapter Configs: FIS Horizon (Code Connect) " for the Horizon core.`*\
\
Fill in the corresponding credentials on the configuration page. You'll need to reference your CodeConnect portal or reach out to your FIS account representative for access to some of this information.

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2FLsYx9wmhV4GoDYt8kCoS%2FScreenshot%202025-02-25%20at%204.39.10%E2%80%AFPM.png?alt=media&amp;token=e807028f-58b6-4420-9cd7-a60cad48e164" alt=""><figcaption></figcaption></figure>

Once completed, scroll down the left pane until you find the configuration item labelled "Adapter Config Bindings" and add a new item. Choose the corresponding integration that you just created and the Adapter Config you just created and click save. This step essentially assigns the **Integration** to use the adapter configuration information we just provided when interacting with the core.


---

# 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-retrieval-api-against-fis-codeconnect/1.-integration-setup.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.
