> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/pos-integration-how-flaik-connects-to-your-pos/pos-integration-api-overview/how-to-upgrade-the-flaik-resort-api-to-2.6.0.md).

# HOW TO: Upgrade the flaik Resort API to 2.6.0

[Install Folder for Current releases.](https://drive.google.com/drive/folders/1Safce3aAGzvwe1EoADroFAzmqpvg09XN)

### Upgrading from 2.5.11 (or any earlier 2.x) to 2.6.0

Version 2.6.0 ships a rebuilt MSI installer that installs to a **new location** (`C:\Program Files\Flaik\Flaik POS Integration API\`; previously `C:\Program Files\Flaik Resort Service\`). Because the location changes, your existing configuration is not carried across automatically — capture it first, then reconfigure after install.

> We are available to run this upgrade with you — book a session via the link in your upgrade email.

#### Step 1 — Record your current configuration

Open `C:\Program Files\Flaik POS Integration API\appsettings.json` on the resort machine and record these values from the `FlaikServiceSettings` section:

| Field                                 | Key                                                                                   |
| ------------------------------------- | ------------------------------------------------------------------------------------- |
| flaik DB connection string            | `FlaikDatabaseConnectionString`                                                       |
| Resort/POS DB connection string       | `ResortDatabaseConnectionString`                                                      |
| POS software code                     | `ResortPosSoftwareCode` (RTP One = 1, Siriusware = 2, InTouch = 5, Guest Connect = 8) |
| Install identifier                    | `InstallIdentifier`                                                                   |
| Custom listen port, if you changed it | `Kestrel.Endpoints.Http.Url` (default 8001)                                           |

Also note any non-default values in your provider file (`appsettings.rtpone.json`, `appsettings.siriusware.json`, or `appsettings.intouch.json`).

**Do not copy `ApiKey`.** The stored value is encrypted to the old installation and cannot be reused. The new version generates a fresh key on first start and flaik central picks it up automatically.

#### Step 2 — Uninstall the old version

Stop the Service and then uninstall "Flaik POS Integration API" via Settings → Installed Apps, or from PowerShell:

```powershell
$code = (Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*" |
         Where-Object DisplayName -eq "NAME OF YOUR FLAIK INSTALL").PSChildName
msiexec /x $code /qb /l*v uninstall-old.log
```

The old installer intentionally leaves `appsettings.json` behind at the old path. Once Step 1 is captured, delete the leftover folder:

```powershell
Remove-Item -Recurse -Force "C:\Program Files\FLAIK FOLDER"
```

#### Step 3 — Install 2.6.0

Run `Flaik.POS.Integration.Installer.2.6.0.msi` (or the `.Staging.` MSI for staging). In the wizard, select your POS software type and enter your site identifier on the flaik configuration screen — use the values recorded in Step 1.

#### Step 4 — Apply the captured configuration

Open `C:\Program Files\Flaik\Flaik POS Integration API\appsettings.json` and paste the recorded values into `FlaikServiceSettings`. Leave `ApiKey` empty. If you had a custom listen port, set the `Kestrel__EndPoints__Http__Url` environment variable for the service rather than editing environment config files (those are replaced on future upgrades).

#### Step 5 — Run the database scripts

Execute the SQL scripts from `C:\Program Files\Flaik\Flaik POS Integration API\SQL\`: the flaik scripts plus the subfolder matching your POS (`RtpOne\`, `Siriusware\`, ...). 2.6.0 updates the flaik database version to 2.6.0.0. Contact flaik support if you'd like these run together.

#### Step 6 — Restart and verify

```powershell
Restart-Service FlaikResortService
```

Browse to `http://localhost:8001/health` (production) or `http://localhost:8002/health` (staging). Confirm:

* the reported version is 2.6.0, and
* the provider configuration section shows a `PosSoftwareVersion` value (new in 2.6.0).

If the port is exposed externally, re-test the external URL and firewall rule.

### Upgrading between 2.6.x versions (future patches)

From 2.6.0 onward, upgrades are in-place again: run the newer MSI and it upgrades the existing installation directly. Your `appsettings.json` and provider config files are never overwritten — no capture/re-entry step. flaik-managed defaults (`appsettings.flaik.json` and the environment file) are refreshed automatically as part of the upgrade.


---

# 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://knowledgebase.flaik.com/flaik-knowledge-base/for-it-specialists/pos-integration-how-flaik-connects-to-your-pos/pos-integration-api-overview/how-to-upgrade-the-flaik-resort-api-to-2.6.0.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.