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

# Pike 13

Integration Steps

Reward Pike13 class, appointment, workshop and purchase activity.

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

{% columns %}
{% column %}

### Visits & purchases

* **Events** — Reward classes, appointments, workshops and pre-booking.
* **Purchases** — Filter by item/item type; refund handling is supported.
  {% endcolumn %}

{% column %}

### Membership tiers & eligibility

* **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 synced membership name and mapped member status. The standard member sync does not send an original join date; tier qualification does not require that date. Memberships and tier rewards must be enabled in Perkville, with the qualifying membership types and active statuses syncing from your system.

* **Other earning rules** — Confirm the qualifying event for a separate sign-up reward; the standard member sync does not supply an original join date.
  {% endcolumn %}
  {% endcolumns %}

### Referrals & rewards

* **Rewards** — Pike13 supports single-use and multi-use coupons; automatic redemption fulfillment is not included in the listed integration.

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

During onboarding, the business admin on your Pike13 account will be added to our integration platform, **Middle**, via email by your Perkville Customer Success Representative. You’ll need to activate your Middle account by creating a password and logging in. Once logged into Middle, follow the steps below to connect your Pike13 account:

1. Click **Add New App Connection**.
2. Select **Pike13** from the list and scroll to the bottom of the page.
3. Click **Add Connection**. Name the connection with your business name and location name.
4. Enter your Pike13 **Business URL Name** in the field labeled *BusinessURL Name*.
5. Click **Save**.
6. Click **Launch OAuth Flow**.
   * When completing the OAuth process, be sure you are logged into a Pike13 user account with **Admin** privileges.
7. Once available, click **Launch OAuth Process** and follow the on-screen prompts to complete the connection.

If you experience any issues during setup, please contact your Perkville Customer Success Representative for assistance.<br>

## FAQ

### Does coupon support mean automatic reward fulfillment?

No. Coupon support in Pike13 and automatic fulfillment by the integration are separate capabilities.

See the [Pike 13 partner profile](https://partners.perkville.com/partners/pike13) 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/pike-13.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.
