> For the complete documentation index, see [llms.txt](https://docs.bunny.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bunny.com/guide/release-notes/feb-19-2026-release.md).

# Feb 19, 2026 release

### Custom fields (beta)

You can now add custom fields to various objects, such as Account, Contact, Deal, Quote, Subscription, Product and Plan. The field types support are string, integer, date, boolean and rich text. Custom fields appear in the UI in a special section called Custom fields and are available for reading and writing via the API.

### Recurring coupons

Coupons can now be recurring as opposed to just being applied once at the checkout.

### Quote sharing improvements

You can now share a quote in two different ways. The quote can be downloaded as a PDF and marked it as shared. Sharing via email now allows you to edit a personal, unbranded email that the customer can respond to.

### Plan add-on trials

It's now possible to trial plan add-ons in the same way regular plans can be trialed.

### Small improvements

* `account.net_payment_days` is now available in workflows
* Improvements to rendering of usage-based pricing in the portal's plan picker
* Added ability to specify a billing period when linking to the plan picker in the portal


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bunny.com/guide/release-notes/feb-19-2026-release.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
