> 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/5.-testing-the-integration.md).
# 5. Testing the Integration
Now that all of the setup is complete, you can now test the integration. During this phase, you may run into certain connection or configuration errors; if these do show up, you will need to troubleshoot the issues as necessary.
Navigate to the Swagger API page on the left. Here, you should see a list of **Integration Execution Endpoints**, one of which being the Integration you just created.
Click on the integration and to open the dropdown menu:
From here, click on the "Try it out" button in the top left of the menu. This allows us to change the **Input Payload** that we send through the integration. During the [Integration and Service Request Hook Setup](/tutorials/building-a-retrieval-api-against-fis-codeconnect/4.-integration-and-service-request-hook-setup.md), if you chose to set the `customerNumber` variable to something within the input payload like this:
```
customerNumber = input.payload.testNumber
keep(customerNumber = customerNumber)
```
Then copy and paste this JSON payload into the Swagger Page:
```json
{
"testNumber": "00000000001"
}
```
Click on the "Execute" button to run the integration. After executing, navigate to the Run History Page to see the results of your test. If successful, the output record in run history should look something like this:
---
# 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://glyue.docs.sandboxbanking.com/tutorials/building-a-retrieval-api-against-fis-codeconnect/5.-testing-the-integration.md?ask=&goal=
```
`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.