> 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/2.-service-request-setup.md).

# 2. Service Request Setup

**Creating the Service Request**\
\
\&#xNAN;*For reference:* [*Service Request Documentation*](/reference/integration_components/servicerequest.md)\
\
Click on the "View Site" button at the top right of the page to return to the main Integration Gateway UI. From here, you'll need to navigate back to the Build screen.\
\
Right click on the Integration you created and Go To -> Service Requests. Add a new row to this table.\
\
Set the Sequence Number to 1, as this service request should represents the first API call to CodeConnect.\
\
Underneath the System column, enter "CODECONNECT.IBS" to determine which system we are calling out to. (Replace this with "CODECONNECT.HORIZON" or other applicable cores if necessary).

**Configuring the Service Request**\
\
To complete the next steps, you may need to reference the latest CodeConnect documentation that is available on the CodeConnect portal.\
\
For our example in this How-To Guide, we will be using the Get Customer (IBS Customer Information - v2) endpoint to retrieve information about a given customer on the IBS core.\
\
In the Build Page, enter the service name "IBSCI/v2" or whichever IBS service you want to use. This establishes which API group the service request will use within CodeConnect.\
\
Under formula variable, we recommend entering a formula name that corresponds to what the service is doing. In our example case, we use a formula variable of "getCustomer" as it accurately describes what our service is doing.\
\
Click the Save button at the bottom of the screen.

<figure><img src="/files/hfBVhaI8VCfcNElZN4M0" alt=""><figcaption></figcaption></figure>


---

# 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/2.-service-request-setup.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.