

# Changelog

Relevant changes to this documentation, newest first. Each entry lists what
changed and where, so integrators and AI agents can see at a glance whether a
page they rely on has been updated. Typo fixes, wording and layout tweaks are
not listed.

This changelog covers the documentation. For releases of the Frontend SDKs,
see [Documentation & Changelog](https://developer.anybill.de/the_anybill_sdk/native_sdks).

## 2026-10-06

- **Vendor API**: new page [E-Invoice (ZUGFeRD / XRechnung)](https://developer.anybill.de/vendor_api/e_invoice).
  Describes how a POS marks a receipt as an e-invoice via
  `bill.misc.extension:anybill.receiptType = EInvoice`, how the buyer requests a
  ZUGFeRD PDF or XRechnung XML on the receipt page, and which receipt fields the
  e-invoice is built from. Linked from the [Bill Endpoints](https://developer.anybill.de/vendor_api/bill_endpoints)
  and [Bill Data Model](https://developer.anybill.de/vendor_api/bill_data_model) pages.

## 2026-09-29

- **Vendor API**: `cardPan` is documented consistently as a *masked* PAN. The
  [Bill Data Model](https://developer.anybill.de/vendor_api/bill_data_model) carries a PCI DSS warning (at most
  the first 6 and the last 4 digits), the payment examples use `123456******1234`,
  and the rule was added to `anybill-vendorapi-AGENTS.md`.

## 2026-09-17

- **Site**: new [Privacy Policy](https://developer.anybill.de/privacy/) page. Usage analytics and the AI chat
  widget only run after consent.

## 2026-09-16

- **Vendor API**: status-code tables with retry guidance added to
  [Bill Endpoints](https://developer.anybill.de/vendor_api/bill_endpoints),
  [Store Endpoints](https://developer.anybill.de/vendor_api/store_endpoints) and
  [Loyalty Endpoints](https://developer.anybill.de/vendor_api/loyalty_endpoints) (which codes are retryable,
  which require a payload fix, how `bill.id` keeps retries idempotent). The retry
  section of `anybill-vendorapi-AGENTS.md` was extended accordingly.
- **POS SDK**: [Configuration](https://developer.anybill.de/vendor_api_sdk/configuration) rewritten: feed URL,
  `dotnet` CLI, `nuget.exe`, Visual Studio and project-level `NuGet.config`
  instructions plus a troubleshooting section.

## 2026-09-09

- **Vendor API**: documentation aligned with the actual backend behaviour:
  - The base URL carries the `/api` prefix (`https://vendor.anybill.de/api`); all
    routes and curl examples were updated.
  - `POST /v3/bill/url` and `POST /v3/store/search` are POST, not GET.
  - A duplicate self-generated receipt id answers `409` with a plain-string body;
    a `bill.id` that was not pre-registered answers `404 pregeneratedbill-notfound`.
  - `DELETE /v3/bill/{billId}` always answers `204` (asynchronous).
  - Store endpoints: upsert semantics (`201`/`200`), `Total-Count` header, search
    body, field length limits.
  - Loyalty: generic `PUT /v3/loyalty/transactions` with `externalUserId` is the
    documented route; the HelloAgain-specific routes are marked deprecated.
  - Data model: new root field `bill.countryCode`, fourth line type `keyValue`,
    string enum names recommended over integers, Visa is `CardPayment` (13).
- **Vendor API**: new page [Fiscalization](https://developer.anybill.de/vendor_api/fiscalization) for
  `bill.security`: the `required` / `failure` flags, the `type` discriminator and
  its fallback to `Tse`, mandatory fields per type (Tse, Rksv, BoiTva, TBai, Sweden,
  Portugal, SecurityInformation) with examples, and how to handle a fiscal unit
  failure.
- **Vendor API**: the fiscalization fields are documented under their current
  names `security.fiscalization`, `failure` and `required`. The deprecated names
  `security.tse`, `tseFailure` and `tseRequired` only appear in a labelled
  migration note. The TSE example was corrected (`processType` and `processData`
  were swapped). The POS SDK C# page uses `Failure` / `Required`.

## 2026-09-08

- **Vendor API**: new page [AI-Assisted Integration](https://developer.anybill.de/vendor_api/ai_assisted_integration)
  for POS integrators, with the downloads
  <a href="https://developer.anybill.de/downloads/anybill-vendorapi-AGENTS.md" download>anybill-vendorapi-AGENTS.md</a> and
  [anybill-vendorapi-llms.txt](https://developer.anybill.de/downloads/anybill-vendorapi-llms.txt), and curl
  examples on the [Authentication](https://developer.anybill.de/vendor_api/authentication) and
  [Bill Endpoints](https://developer.anybill.de/vendor_api/bill_endpoints) pages.
- **iOS SDK**: the clipboard app-link check is documented as an app-side
  implementation; `AnybillAppLink.checkForAnybillAppLinkData()` no longer exists in
  the 2.x SDK.

## 2026-09-07

- **Vendor API**: new page [Integration Review](https://developer.anybill.de/vendor_api/integration_review)
  explaining the POS integration acceptance process and the receipt-content rules
  it checks. Replaces the former "Helpful" page.

## 2026-09-04

- **Frontend SDKs**: the [Android](https://developer.anybill.de/the_anybill_sdk/android_integration),
  [iOS](https://developer.anybill.de/the_anybill_sdk/ios_integration), [Flutter](https://developer.anybill.de/the_anybill_sdk/flutter_integration),
  [React Native](https://developer.anybill.de/the_anybill_sdk/react_native_integration) and
  [Web](https://developer.anybill.de/the_anybill_sdk/web_integration) pages were synchronised with the current
  SDK releases, including logout and account deletion, receipt export, return
  receipts, adding receipts and the AnybillMarketing module.

## 2026-09-03

- **Site**: new design with dark mode and full-text search. All URLs remain
  unchanged.
- **Vendor API**: the former single page was split into
  [Environments](https://developer.anybill.de/vendor_api/environments), [Authentication](https://developer.anybill.de/vendor_api/authentication),
  [Bill Endpoints](https://developer.anybill.de/vendor_api/bill_endpoints), [Bill Data Model](https://developer.anybill.de/vendor_api/bill_data_model),
  [Bill Examples](https://developer.anybill.de/vendor_api/bill_examples), [Print Buffer Format Guide](https://developer.anybill.de/vendor_api/print_buffer),
  [Store Endpoints](https://developer.anybill.de/vendor_api/store_endpoints) and
  [Loyalty Endpoints](https://developer.anybill.de/vendor_api/loyalty_endpoints). The old URL redirects to the
  [Vendor API overview](https://developer.anybill.de/vendor_api/).
- **API Reference**: interactive OpenAPI reference (Scalar) for the
  [Vendor API](https://developer.anybill.de/vendor_api/api_reference) and the
  [Partner Platform API](https://developer.anybill.de/partner_platform_api/api_reference).

## 2026-07-28

- **Vendor API**: discount documentation reworked: `discounts` in the line's
  `extension:anybill`, `fullAmountInclVatBeforeDiscounts`,
  `item.extension:anybill.pricePerUnitBeforeDiscounts`, the `sequenceNumber` for
  stacked discounts and the recommendation to send negative discount amounts.
- **Site**: AI chat assistant added to the documentation.

## 2026-07-24

- **Vendor API**: Retry Policy Guidelines restored (when to retry, strategy,
  idempotency, logging).

## 2026-06-19

- **Vendor API**: v2 and deprecated leftovers removed; the documentation and the
  v3 Postman collection were synchronised with the current OpenAPI specification.
  The Postman collection now includes the anybill OAuth flow, and its download link
  was fixed. Transparent user creation via `externalId` and the self-generated
  receipt id are documented in their own sections.
- **Web SDK**: fuzzy receipt search documented.

## 2026-06-12

- **Android and iOS SDK**: fuzzy receipt search documented.
- **Partner Platform API**: external user creation via `externalId` described in
  more detail on the [Endpoints](https://developer.anybill.de/partner_platform_api/api_v3) page.

## 2026-04-24

- **New page**: [Architecture and Data Flow](https://developer.anybill.de/architecture_and_data_flow/) with an
  overview diagram of how receipts flow between POS, anybill and the consumer.

## 2026-04-23

- **Authentication**: creating an anybill user is optional when an `externalId`
  (e.g. a customer card id) can be provided. The
  [Partner Platform API](https://developer.anybill.de/partner_platform_api/api_v3) describes implicit vs.
  explicit user creation, the [Vendor API](https://developer.anybill.de/vendor_api/) the user identification
  via `externalId`, and the [Frontend SDK overview](https://developer.anybill.de/the_anybill_sdk/overview) both
  authentication variants. `anybill-sdk-AGENTS.md` was updated accordingly.

## 2026-04-22

- **Frontend SDKs**: new page [AI-Assisted Integration](https://developer.anybill.de/the_anybill_sdk/ai_assisted_integration)
  with the download <a href="https://developer.anybill.de/downloads/anybill-sdk-AGENTS.md" download>anybill-sdk-AGENTS.md</a>
  and the site-wide [llms.txt](https://developer.anybill.de/llms.txt) for AI coding agents.
