# 1.1.0 — shared developer access

- Redline account API keys automatically provision private UDS evidence workspaces.
- Global approval/revision/redaction/publication controls and explicit credential/workspace grants apply to developer, service and Firebase credentials. Privileged API capabilities default off; evidence submission remains available.
- Added curated published-protocol reads and explicit publication/withdrawal operations.
- Added schema migration 4; existing frozen v1.0.0 snapshots remain unchanged.
- See [API access](../api-access/guide.md) and the internal developer-access deployment runbook for migration details.

# UDS API changelog

Canonical documentation: https://api.redlineautohaus.com/docs/uds/.

## 1.0.0 - September 10, 2026

Initial Phase 1 contract and documentation for diagnostic evidence ingestion in Redline API.

- Manufacturer-neutral sources, sessions, evidence records and messages with optional vehicle/ECU context.
- Complete, partial and unavailable byte representations; preserved source order, uncertainty and provenance.
- Authenticated scope isolation, idempotent POSTs, immutable occurrence identity and bounded durable imports.
- Separate submitted interpretations, definitions, evidence links and privileged review/revisions.
- Public HTML, Markdown, synthetic curl/Node examples and runtime-generated OpenAPI/JSON Schemas.

This changelog records the contract/documentation release, not operational sign-off. Read the deployed `/api/v1/uds/capabilities` for effective contract version, permissions, features and limits. Load targets, approved retention and disaster-recovery objectives require separate measured acceptance.

## Compatibility policy

The API prefix is `/api/v1/uds`. Clients must not assume an optional feature exists merely because the broad Phase 1 scope describes it. Use the active contract and capabilities. Unknown top-level request keys and unsupported structured extension versions fail validation; unknown bounded extension namespaces remain unvalidated.

Keep stable occurrence keys and idempotency keys across retries. Never rely on payload hash as event identity. Existing evidence remains traceable when a correction or interpretation is superseded.

No deprecations are declared in this initial contract. Future releases must identify changed request/response fields, limits, replay guarantees and deprecation dates, and publish the corresponding versioned contract.