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

# Jonas i4

Jonas i4 and Jonas Compete have different integration capabilities.

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

* **Attendance** — Reward gym check-ins, class attendance and appointments.
* **Purchases** — Reward in-club purchases.
* **Other earning** — Support referral and birthday awards.

## 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

### Can I use the Jonas Compete setup instructions?

Confirm the product and connection requirements with your CSR. Do not assume the Compete setup or activity list applies to i4.

See the [Jonas i4 partner profile](https://partners.perkville.com/partners/jonas-fitness) for more information.

## Related Jonas integration

Using Jonas Compete instead? See [Jonas Compete](https://docs.perkville.com/integrations/integration-reference/jonas-compete.md) for that product's separate earning capabilities and setup requirements. In particular, Jonas i4 documents class and appointment attendance, while the Jonas Compete guide lists gym check-ins; do not assume the same events are available across both systems.


---

# 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/jonas-i4.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.
