Partner API version history

Historical contracts remain publicly readable. A published contract version is never overwritten. For reproducible builds and audits, integrations always select a concrete version.

Available

1.9.0 — 2026-09-28

Compatible optional read fields for the effective pharmacy login mode on active, uniquely bound S2S directory entries. Existing link fields are unchanged.

1.8.0 — 2026-09-23

Compatible read, set and removal operations for one optional KIM address on an existing partner pharmacy. Operations are bound to the partner, consumer and pharmacy.

1.7.0 — 2026-09-19

Compatible read-only Preview and atomic, revision-bound Apply operations for allowlisted partner-pharmacy configuration.

1.6.0 — 2026-09-18

Compatible additions for revision-protected email content and logo visibility at organization and appointment-type level with per-field inheritance.

1.5.0 — 2026-09-17

Compatible additions for revision-protected email reminder configuration at organization and appointment-type level with explicit inheritance and bounded lead times.

1.4.0 — 2026-09-16

Compatible additions for revision-protected SMS confirmation configuration at organization and appointment-type level with explicit inheritance.

1.3.0 — 2026-09-15

Compatible additions for up to five normalized additional appointment-confirmation recipients per existing partner pharmacy. An empty list disables additional delivery.

1.2.0 — 2026-09-15

Compatible additions for one optional non-secret SMED identifier per existing partner pharmacy. Blank or null disables the assignment; credentials and URL tokens are not part of the contract.

1.1.0 — 2026-09-14

Compatible additions for the partner pharmacy directory, control claim, scheduling policies, channel webhooks, master-data management and appointment-type intake fields.

1.0.0 — 2026-08-02

First stable release of the arztkonsultation Partner API with explicitly published server-to-server operations.

No silent breaks

An incompatible change receives a new major namespace. Existing v1 partners are never broken by silently replacing the v1 contract.