> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/fliip.md).

# FLiiP

Use FLiiP check-ins, PT sessions and membership records in Perkville.

## Integration at a glance <a href="#capabilities-and-use-cases" id="capabilities-and-use-cases"></a>

{% hint style="info" %}

* **Timing and limits** — The listed sync is daily. Purchase earning and automatic redemptions are not included.
  {% endhint %}

* **Attendance** — Reward check-ins and PT sessions; pre-booking is supported.

* **Memberships** — Reward membership sign-ups and use membership status/type for eligibility.

* **Membership tier rewards** — Confirm availability for your connection with your Perkville representative. Tier rewards require membership types and active statuses to sync to Perkville; a sign-up or purchase reward alone does not establish tier support. See [Membership tiers](https://docs.perkville.com/features/earning-rules/membership-tiers.md).

## Setup

Contact [Perkville Support](https://docs.perkville.com/overview/support.md) or your Customer Success Representative to confirm access, participating locations, data matching and the workflows for your program. Test the agreed use cases before launch.

## FAQ

### Why are points not appearing immediately?

The partner profile lists a daily sync. Confirm the scheduled processing window with your CSR.

See the [FLiiP partner profile](https://partners.perkville.com/partners/fliip) for more information.


---

# 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://docs.perkville.com/integrations/integration-reference/fliip.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.
