UDS API / Reference

JSON Schema directory

Core schemas are served from the API contract definitions using JSON Schema 2020-12. They describe accepted request fields, not permission grants. Cross-record ownership, source relationships, exact-byte semantics and other database-dependent validation still apply.

Read the evidence semantics alongside the request schemas.

Message evidence

Message request schema covers complete, partial and unavailable observations. Exactly-one encoding, nonempty bytes, segment overlap and artifact verification have additional semantic validation. Batches accept an envelope durably before validating each item; see the import operations in OpenAPI.

Core resource inputs

Use returned IDs in path parameters. Nested create request schemas exclude the parent ID because the URL supplies it. PATCH accepts only the listed mutable fields and requires If-Match.

ResourceSchemaCreate route
organizationCreate request/catalog/organizations
vehicle nodeCreate request/catalog/vehicle-nodes
vehicle relationCreate request/catalog/vehicle-relations
vehicle variantCreate request/catalog/vehicle-variants
vehicleCreate request / Patch request/vehicles
ecu familyCreate request/catalog/ecu-families
ecu hardwareCreate request/catalog/ecu-hardware
ecuCreate request / Patch request/ecus
installationCreate request/installations
software componentCreate request/catalog/software-components
identifierCreate request/identifiers
sourceCreate request / Patch request/sources
source recordCreate request/source-records
extraction runCreate request/extraction-runs
sessionCreate request / Patch request/sessions
session sourceCreate request/sessions/:sessionId/sources
vehicle observationCreate request / Patch request/sessions/:sessionId/vehicle-observations
ecu observationCreate request / Patch request/sessions/:sessionId/ecu-observations
ecu componentCreate request/ecu-observations/:ecuObservationId/components
connectionCreate request/sessions/:sessionId/connections
endpointCreate request/connections/:connectionId/endpoints
operationCreate request/sessions/:sessionId/operations
eventCreate request/sessions/:sessionId/events
message linkCreate request/message-links
operation message linkCreate request/operation-message-links
decodingCreate request/messages/:messageId/decodings
factCreate request/facts
definitionCreate request / Patch request/definitions
definition versionCreate request/definitions/:definitionId/versions
applicabilityCreate request/definition-versions/:definitionVersionId/applicability
evidence linkCreate request/evidence-links
reviewCreate request/reviews
revisionCreate request/revisions
redactionCreate request/redactions

Imports, artifacts and extensions

The generated OpenAPI components include import, batch and artifact-registration bodies. Authenticated GET /api/v1/uds/schemas returns registered extension schemas; GET /api/v1/uds/reference-codes returns registered code catalogs. Do not fetch arbitrary schema URLs supplied inside source evidence.

This directory indexes the initial 1.0.0 contract. Confirm the deployed contract and effective limits before ingestion. Public schema access does not permit reading or writing dataset records.