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.10.0 — 2026-10-04
Compatible extension with a room calendar for pharmacy rooms: day and range closures, changed hours, extra openings, weekly schedules from a date and statutory holidays per federal state. Existing room operations and schemas are unchanged.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.10.0
- OpenAPI YAML 1.10.0
- Checksums 1.10.0
- Changelog 1.10.0
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.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.9.0
- OpenAPI YAML 1.9.0
- Checksums 1.9.0
- Changelog 1.9.0
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.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.8.0
- OpenAPI YAML 1.8.0
- Checksums 1.8.0
- Changelog 1.8.0
1.7.0 — 2026-09-19
Compatible read-only Preview and atomic, revision-bound Apply operations for allowlisted partner-pharmacy configuration.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.7.0
- OpenAPI YAML 1.7.0
- Checksums 1.7.0
- Changelog 1.7.0
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.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.6.0
- OpenAPI YAML 1.6.0
- Checksums 1.6.0
- Changelog 1.6.0
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.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.5.0
- OpenAPI YAML 1.5.0
- Checksums 1.5.0
- Changelog 1.5.0
1.4.0 — 2026-09-16
Compatible additions for revision-protected SMS confirmation configuration at organization and appointment-type level with explicit inheritance.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.4.0
- OpenAPI YAML 1.4.0
- Checksums 1.4.0
- Changelog 1.4.0
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.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.3.0
- OpenAPI YAML 1.3.0
- Checksums 1.3.0
- Changelog 1.3.0
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.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.2.0
- OpenAPI YAML 1.2.0
- Checksums 1.2.0
- Changelog 1.2.0
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.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.1.0
- OpenAPI YAML 1.1.0
- Checksums 1.1.0
- Changelog 1.1.0
1.0.0 — 2026-08-02
First stable release of the arztkonsultation Partner API with explicitly published server-to-server operations.
- Status: stable
- Compatibility namespace:
/api/v1/s2s/ - OpenAPI JSON 1.0.0
- OpenAPI YAML 1.0.0
- Checksums 1.0.0
- Changelog 1.0.0
No silent breaks
An incompatible change receives a new major namespace. Existing v1 partners are never broken by silently replacing the v1 contract.