> For the complete documentation index, see [llms.txt](https://docs-integration.squake.earth/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-integration.squake.earth/notable-changes/release-notes/2023/2023-mar.md).

# Product Release Notes March 2023 - Smarter Codes, Better Emails, and Idempotent Purchases

* 🌐 **\[General]**

  • New locales added for broader language support.
* 🚗 **\[Calculations – ACRISS]**

  • Support for **SIPP codes** in the ACRISS methodology.
* ✈️ **\[Calculations – Flights]**

  • Added `booking_class` resolution for flight methodologies.

  • IATA codes now supported by M\&M. 🎉
* 📧 **\[V2 Purchases]**

  • Clients now receive **confirmation emails** after successful v2 purchases.

***

**📈 Improvements**

* 🛒 **\[Purchases]**

  • `/purchase` request is now fully **idempotent** — prevents accidental duplicate charges or records.
* 📩 **\[Client Notifications]**

  • All users related to a client are now emailed when a project is retired.
* 🌍 **\[Translations]**

  • Updated language translations.
* 🛠 **\[General]**

  • Better input validations across endpoints.

  • Removed unused `valid_until` field from responses.


---

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

```
GET https://docs-integration.squake.earth/notable-changes/release-notes/2023/2023-mar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
