POST /v1/containers
Create a Container
Create a new container within a storage service
POST
POST /v1/containers
Documentation Index
Fetch the complete documentation index at: https://openmetadata-codex-audit-docs-codebase-alignment.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Create a Container
Create a new container within a storage service.Body Parameters
Name of the container. Must be unique within the parent storage service or parent container.
Fully qualified name of the parent StorageService (e.g.,
s3_datalake).Human-readable display name for the container.
Description of the container in Markdown format.
Reference to a parent container for nested containers.
Path prefix for objects in the container (e.g.,
/raw/events/).Number of objects stored in the container.
Total size of the container in bytes.
List of file formats stored in the container (e.g.,
csv, tsv, parquet, avro, json, jsonl, jsonGz, jsonZip).Data model describing the schema of files in the container.
Full path of the container (e.g.,
s3://analytics-bucket/raw/events).Array of owner references (users or teams) to assign to the container.
Fully qualified name of the domain to assign for governance purposes.
Array of classification tags to apply to the container.
Custom property values defined by your organization’s metadata schema.
POST /v1/containers
Returns
Returns the created container object with all specified properties and system-generated fields.Response
Unique identifier for the container (UUID format).
Container name.
Fully qualified name in format
service.containerName.Human-readable display name.
Description of the container in Markdown format.
Reference to the parent storage service.
Type of storage service (e.g., S3, GCS, ADLS, CustomStorage).
Path prefix for objects in the container.
Number of objects stored in the container.
Total size of the container in bytes.
List of file formats stored in the container.
Data model describing the schema of files.
Full path of the container.
List of owners assigned to the container.
Domain assignments for governance.
Classification tags applied to the container.
Custom property values defined by your organization’s metadata schema.
Version number for the entity (starts at 0.1).
Create or Update (PUT)
UsePUT /v1/containers instead of POST to perform an upsert. If a container with the same fullyQualifiedName already exists, it will be updated; otherwise, a new container is created. The request body is the same as POST.
PUT will not return a 409 conflict error if the entity already exists — it will update the existing entity instead.Bulk Create or Update (PUT)
UsePUT /v1/containers/bulk to create or update multiple containers in a single request. The request body is an array of create request objects.
Error Handling
| Code | Error Type | Description |
|---|---|---|
400 | BAD_REQUEST | Invalid request body or missing required fields |
401 | UNAUTHORIZED | Invalid or missing authentication token |
403 | FORBIDDEN | User lacks permission to create containers |
409 | ENTITY_ALREADY_EXISTS | Container with same name already exists in service (POST only) |