For the complete documentation index, see llms.txt. This page is also available as Markdown.

POS Integration — How flaik Connects to Your POS

flaik syncs lesson sales, guest details, and scheduling data with your point-of-sale system. There are two ways a POS connects to flaik — which one applies to you depends on the POS software your resort runs.

Pathway A — Direct API connection

flaik connects to your POS vendor's API directly, cloud to cloud. Nothing is installed or hosted at the resort. Setup is a credential exchange between flaik and your vendor, coordinated by flaik support.

→ See Direct API Connections: PSIA, InTouch, Axess AI (coming soon)

Pathway B — POS Integration API (resort-hosted)

A small Windows service, installed on a server at the resort that bridges your local POS database to the flaik cloud. Your IT team installs the MSI, points it at the POS database, and exposes one port to flaik.

Formerly known as the Resort Service API — same integration, renamed as of version 2.6.0.

→ See POS Integration API: installation, upgrade, release notes, and POS-specific setup for RTP|One and Siriusware

Which pathway is my resort on?

POS software
Pathway
Notes

RTP|One

B — POS Integration API

Siriusware

B — POS Integration API

InTouch

A — Direct API

Existing resort-hosted InTouch connections are being migrated to the direct API — flaik will coordinate your switch.

PSIA

A — Direct API

Axess AI

A — Direct API

Coming soon — contact flaik for timing.

Other / not listed

Contact flaik support — see the Integration Overview for the full systems picture.

Last updated

Was this helpful?