POST /v1/apiCollections
Create an API Collection
Create a new API collection within an API service
POST
POST /v1/apiCollections
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 an API Collection
Create a new API collection within an API service.Body Parameters
Name of the API collection. Must be unique within the parent API service.
Fully qualified name of the parent APIService (e.g.,
sample_api_service).Base URL for the API collection (e.g.,
https://petstore3.swagger.io/#/pet).Human-readable display name for the API collection.
Description of the API collection in Markdown format.
Array of owner references (users or teams) to assign to the API collection.
Fully qualified name of the domain to assign for governance purposes.
Array of classification tags to apply to the API collection.
Custom property values defined by your organization’s metadata schema.
POST /v1/apiCollections
Returns
Returns the created API collection object with all specified properties and system-generated fields.Response
Unique identifier for the API collection (UUID format).
API collection name.
Fully qualified name in format
service.collectionName.Human-readable display name.
Description of the API collection in Markdown format.
Base URL for the API collection.
Reference to the parent API service.
Type of API service (e.g., Rest).
List of owners assigned to the API collection.
Domain assignments for governance.
Classification tags applied to the API collection.
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/apiCollections instead of POST to perform an upsert. If an API collection with the same fullyQualifiedName already exists, it will be updated; otherwise, a new API collection 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/apiCollections/bulk to create or update multiple API collections 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 API collections |
409 | ENTITY_ALREADY_EXISTS | API collection with same name already exists in service (POST only) |