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

# November 2025

### November 4, 2025

#### [Blog](https://info.perkville.com/blog)

* Added links to recent blog posts on the business dashboard
* Added links to recent blog posts in the daily business report email

### November 7, 2025

#### [Points by Customer Report](https://docs.perkville.com/features/reports/points-by-customer.md)

* Added a new Points by Customer report

### November 10, 2025

#### [Add/Redeem dropdowns](https://docs.perkville.com/faqs/points/how-do-i-add-points-to-a-customers-account.md)

* Added Perk ID to these dropdowns for clarity on which perk was being used

#### [Customer details](https://docs.perkville.com/features/customers.md)

* (Admins only) In the customer's transaction history, now linking to the perk's edit page, if applicable

#### [Transaction API](https://www.perkville.com/developers/docs/v2/)

* Fixing an error that occurred when API clients posted transaction using external member identifiers for deactivated users

### November 19, 2025

#### [Billing](https://docs.perkville.com/faqs/miscellaneous/how-do-i-update-my-billing-information-e.g.-credit-card-on-file.md)

* Added a new billing page allowing businesses to update their credit card on file

#### [Referrals](https://docs.perkville.com/features/referrals.md)

* Submitted referrals and advertised referral offers will now be associated with the customer's currently selected location


---

# 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/november-2025.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.
