Skip to main content
GET
Export ODCS

Import & Export

Data contracts can be imported and exported using the Open Data Contract Standard (ODCS) v3.1.0 format. Both JSON and YAML are supported, with smart merge and full replace modes for updates.

Export to ODCS

Export by ID (JSON)

GET /v1/dataContracts/{id}/odcs

Export by ID (YAML)

GET /v1/dataContracts/{id}/odcs/yaml

Export by FQN (JSON)

GET /v1/dataContracts/name/{fqn}/odcs

Export by FQN (YAML)

GET /v1/dataContracts/name/{fqn}/odcs/yaml
id
string
UUID of the data contract.
fqn
string
Fully qualified name of the data contract.
fields
string
Fields to include in the export. Defaults to owners,reviewers,extension,schema,sla,security.
Export ODCS

Import from ODCS

Create from ODCS JSON

POST /v1/dataContracts/odcs

Create from ODCS YAML

POST /v1/dataContracts/odcs/yaml

Create or Update from ODCS JSON

PUT /v1/dataContracts/odcs

Create or Update from ODCS YAML

PUT /v1/dataContracts/odcs/yaml
entityId
string
required
UUID of the entity to attach the contract to.
entityType
string
required
Type of the entity (e.g., table, topic, apiEndpoint).
mode
string
default:"merge"
Import mode for PUT endpoints: merge (preserves existing fields not in the import) or replace (fully overwrites the contract).
objectName
string
Schema object name to import for multi-object ODCS contracts. If not specified, auto-selects based on entity name.
Import ODCS
Import ODCS
Import ODCS

Parse ODCS YAML

Preview an ODCS YAML contract without importing. Useful for inspecting multi-object contracts. POST /v1/dataContracts/odcs/parse/yaml
Parse YAML
Response

Validate ODCS YAML

Validate an ODCS YAML contract against a target entity without creating it. POST /v1/dataContracts/odcs/validate/yaml
entityId
string
required
UUID of the entity to validate against.
entityType
string
required
Type of the entity.
objectName
string
Schema object name for multi-object contracts.
Validate YAML
Response

Supported ODCS Versions


Error Handling