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