> 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/overview/release-notes/september-2026.md).

# September 2026

### September 2, 2026

#### Challenges

* Added home location filter to the [Challenge Progress Report](https://docs.perkville.com/features/reports/challenge-progress-by-individual.md)
* Adding a confirmation modal when creating a challenge progress activity

#### Vouchers

* Additional UI adjustments to help with clarity
* Redesigned the referral offer and instant reward emails

### September 4, 2026

#### Referral API

* Fixing a validation issue that only completed staff-submitted referrals if the referred person earned points. Now staff-submitted referrals via the API can be completed for any qualifying transaction (i.e. progress activities)

### September 14, 2026

#### Mindbody

* Initial work to support logging into Perkville via the Mindbody Branded App

#### Miscellaneous

* Fixing an issue that could rarely result in a dashboard activity item staying "So-and-so joined the rewards program" despite already having joined

### September 15, 2026

#### Promotions

* Added **Calendar day** as an option for [Frequency bonuses](https://docs.perkville.com/features/earning-rules/promotions-and-bonus-earnings/frequency-bonus.md).

#### Loyalty Program

* Added [Loyalty Program History](https://docs.perkville.com/features/settings/loyalty-program/loyalty-program-history.md) to track perk creations, edits, deactivations, and reactivations. Administrators can review an individual perk's history or the program-wide history, apply filters, and export results as CSV.

### September 22, 2026

#### API

* Added structured time-bonus values to the Earning Rules response through `time_periods_structured`, using ISO weekday numbers and structured start/end times. See [Earning rules page](https://docs.perkville.com/integrations/integrating-perkville/integrating-your-app-with-perkville/earning-rules-page.md).
* Added optional `referral_date` support when creating referrals so integrations can preserve the date a referral actually occurred. See [Referral page](https://docs.perkville.com/integrations/integrating-perkville/integrating-your-app-with-perkville/referral-page.md).

#### Reports

* Added referral-submitter first name, last name, and email fields to the [Referral Details](https://docs.perkville.com/features/reports/referral-details.md) report.
* Added a **Date of last transaction** filter to the [Customer Details](https://docs.perkville.com/features/reports/customer-details.md) report.

### September 24, 2026

#### External rewards

* Added an authenticated customer handoff for participating external reward providers, allowing approved integrations to request a short-lived SSO launch URL for an external reward. See [Perkville → external reward provider customer handoff](https://docs.perkville.com/integrations/perkville-external-reward-provider-customer-handoff.md).

#### MINDBODY

* Added customer-facing support for opening Perkville from a branded MINDBODY app with single sign-on after the business completes the required setup. See [Branded MINDBODY App sign-in](https://docs.perkville.com/integrations/integration-reference/mindbody/branded-mindbody-app-sign-in.md).

### September 25, 2026

#### Mariana Tek

* Connected dollar-credit and service-credit rewards are now fulfilled in Mariana Tek in **real time** after redemption, replacing the prior scheduled delay. Existing connected rewards were transitioned automatically. See [Automated reward redemptions](https://docs.perkville.com/integrations/integration-reference/mariana-tek/automated-reward-redemptions.md).


---

# 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/overview/release-notes/september-2026.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.
