Skip to main content
POST
POST /v1/apiEndpoints

Create an API Endpoint

Create a new API endpoint within an API collection.

Body Parameters

string
required
Name of the API endpoint. Must be unique within the parent API collection.
string
required
Fully qualified name of the parent APICollection (e.g., sample_api_service.pet).
string
URL for the API endpoint (e.g., https://petstore3.swagger.io/#/pet/addPet).
string
HTTP request method: GET, POST, PUT, PATCH, or DELETE.
object
Schema describing the request body.
object
Schema describing the response body.
string
Human-readable display name for the API endpoint.
string
Description of the API endpoint in Markdown format.
array
Array of owner references (users or teams) to assign to the API endpoint.
string
Fully qualified name of the domain to assign for governance purposes.
array
Array of classification tags to apply to the API endpoint.
object
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

string
Unique identifier for the API endpoint (UUID format).
string
API endpoint name.
string
Fully qualified name in format service.collection.endpointName.
string
Human-readable display name.
string
Description of the API endpoint in Markdown format.
string
URL for the API endpoint.
string
HTTP request method (GET, POST, PUT, PATCH, DELETE).
object
Schema describing the request body.
object
Schema describing the response body.
object
Reference to the parent API service.
string
Type of API service (e.g., Rest).
array
List of owners assigned to the API endpoint.
array
Domain assignments for governance.
array
Classification tags applied to the API endpoint.
object
Custom property values defined by your organization’s metadata schema.
number
Version number for the entity (starts at 0.1).

Create or Update (PUT)

Use PUT /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)

Use PUT /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