Pre-pilot status. The Integration API has not yet launched in
production. Entries below describe spec-level changes to the published
draft. Once Phase 1 ships, entries will tag runtime releases with git
tags and dates of availability.
2026-04-22 — v3 design snapshot
- Architecture RFC v3 published. Supersedes 2026-04-15 draft.
- Code-first OpenAPI workflow adopted (Springdoc + export-and-freeze +
oasdiffCI gate). Replaces the generator-driven contract-first approach that was rejected after red-team review. - Hand-written static mappers in the
integration-apimodule. MapStruct remains in the internal API. - Maven multi-module split added to Phase 0 (
core/internal-api/integration-api). Moneyvalue type standardized across modules.- Java records for all integration DTOs.
- Contract tests from Day 1 — committed spec examples validated against the running app in CI.
- AsyncAPI 3.1 spec for webhooks added.
- Endpoint changes:
- Removed
GET /orders/by-vin/{vin}— conflicted with/orders/{uuid}in static analysis. - Added
vinquery parameter toGET /ordersfor lookup.
- Removed
2026-04-20 — v2 architecture decisions locked
- 17 architectural decisions locked across vocabulary, URL structure, auth, concurrency, compliance rollup, document taxonomy, export file generation, idempotency, self-service token orchestration, subdomain routing, 10-event webhook catalog, rate-limit tiers, SLA posture, GDPR gates, and caching.
2026-04-15 — Initial RFC published
- First-pass architecture RFC. Focused on read-heavy Orders/KYC endpoints.
- Superseded by the v2 / v3 snapshots after council red-team and Santander scope clarification.
How to stay informed
- GitHub releases (post Phase 1 ship) — subscribe to the repo release notifications.
- Email announcements — [email protected] sends breaking-change notices to organization admins on record.
- Status page — link published here once the public status page is live.
Next
Versioning policy
Breaking vs non-breaking guarantees.
FAQ
Common questions.