> 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-multi-system-integration/1.-connecting-to-the-core.md).

# 1. Connecting to the Core

Start by opening the integration we built. Navigate to the **Build page** using the navigation bar.

Right click on your integration and click *Configure*. This will open the *Configuration Wizard* you used when you first created the integration. Click *Continue* to move to the *Systems* page, and click *+ Add System* to add a second adapter to configure our connection to the mock core.

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2Fhp1C3f26eR8xcM6QHNeJ%2FScreenshot%202025-02-13%20at%203.42.57%E2%80%AFPM.png?alt=media&amp;token=3e269708-cb7c-4319-a961-21821b1f7047" alt=""><figcaption><p>Add the adapter for the Sandbox Mock Core</p></figcaption></figure>

Select *Mockcore* from the dropdown. Beneath it, click on the *Select Adapter Config* dropdown, then click *Add New Adapter*. This will open a popup window.

In the popup window, enter the following:

* Name: `Mock Banking Core`
* Host: `sandbox.demo-systems.sandboxbanking.com`

Leave all other fields bank / as-is and click *Save*, then click *Save Adapter Bindings.*

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2Fq6EIXGRI0vYnbysIWliB%2FScreenshot%202025-02-13%20at%203.44.05%E2%80%AFPM.png?alt=media&amp;token=79aab71e-6975-43c7-a9d3-e74fcfd5da39" alt=""><figcaption><p>Add details for the Sandbox Mock Core</p></figcaption></figure>

After saving, close the window.

{% hint style="info" %}
The Mock Banking Core is a playground created by Sandbox Banking to represent a banking core within an integration. It can be accessed [here](https://sandbox.demo-systems.sandboxbanking.com).\
\
The Mock Banking Core is useful for visualizing the effect of integrations before Integration Gateway is connected to a real core.
{% endhint %}

Right click on the integration and select *Go To > Service Request*. You should see the service request we already created, with its `Formula Variable` set to `request_users`.

Click *+ Add Row* to create a new service request. Fill out the following columns on the service request:

| Column           | Value                 |
| ---------------- | --------------------- |
| System           | `MOCKCORE`            |
| Service Name     | `n/a`                 |
| Formula Variable | `create_new_customer` |

This service request will communicate with the Mock Core and pass it the data that we will set up in the next step.

<figure><img src="https://688288018-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1flQ2To8tQpCQWl2Ty9U%2Fuploads%2FL45fjK2RNjPQ8MQSiJRp%2FScreenshot%202025-02-25%20at%204.28.53%E2%80%AFPM.png?alt=media&amp;token=07cf7f8d-b186-487d-9f02-a19fc809c64b" alt=""><figcaption><p>New Service Request for the Mock Core</p></figcaption></figure>

Save your changes.


---

# 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-multi-system-integration/1.-connecting-to-the-core.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.
