> 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/fitdegree.md).

# fitDEGREE

Reward fitDEGREE bookings, attendance and purchases.

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

{% hint style="info" %}

* **Eligibility** — Earning eligibility can use the consumable used for the activity.
  {% endhint %}

* **Events** — Reward bookings, attendance and pre-booking.

* **Membership tier rewards** — Offer points, instant rewards, or both for qualifying active membership tiers, including when members join at a higher tier or upgrade. Each tier is earned once. See [Membership tiers](https://docs.perkville.com/features/earning-rules/membership-tiers.md) for setup.

Uses the membership name derived from current membership consumables and the mapped status. Confirm the resulting type when a customer holds multiple memberships. Memberships and tier rewards must be enabled in Perkville, with the qualifying membership types and active statuses syncing from your system.

* **Other earning rules** — Qualifying purchases and membership/package sign-ups use separate configured earning rules.

{% hint style="warning" %}

* **Limitations** — Refund deductions and automatic redemptions are not included in the listed integration.
  {% endhint %}

Your configured rules determine which eligible activities award points and which workflows are enabled.

## Integration Steps

To connect to fitDEGREE, you’ll need to create an **API Key** and securely share it with your Customer Success Representative.

For security, please use [**One Time Secret**](https://onetimesecret.com/) to send the API key. In your email to your CSR:

* Include the **One Time Secret link**
* Share the **password** to open the link in the body of the email

> **Tip:** Be sure to save a copy of the API Key in case there are issues accessing the One Time Secret link later.

#### How to Create an API Key in fitDEGREE:

1. Log in to: <https://admin.fitdegree.com/>
2. Click the **menu icon** (top left), then click the **setup icon**
3. In the side menu, go to the **“My fitSpot”** section and select **Integrations**
4. Open the **“API Keys”** tab
5. Click the **“Create New API Key”** button
6. Enter a label to identify the API key, then click the green **“Create”** button

Once created, copy the API key and send it securely as described above.

## FAQ

### Can the payment entitlement affect eligibility?

The integration supports eligibility by consumable. Give your CSR the consumables that should qualify.

See the [fitDEGREE partner profile](https://partners.perkville.com/partners/fitdegree) for additional integration 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/fitdegree.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.
