---
title: "Create a schematic vertex (port, junction, or terminal)"
method: POST
path: "/api/v0/components/{component_id}/schematic/vertices"
tags: ["Components"]
---

# Create a schematic vertex (port, junction, or terminal)

`POST /api/v0/components/{component_id}/schematic/vertices`

## Path parameters

- `component_id` string, required

## Query parameters

- `vc_id` string, required — Public ID of the target visual component

## Request body

- CreateVertexRequest
  - `id` string, uuid4, required
  - `kind` 'port' | 'junction' | 'terminal', required
  - `x` number, required
  - `y` number, required
  - `node_id` string, nullable

## Response `200`

Successful Response

- union
  - Port — A connection point on a node's bounding box perimeter. Wire/response shape only — runtime ports live as `PortPosition` entries inside `NodePayload.ports`.
    - `id` string, required
    - `node_id` string, required
    - `x` number, required
    - `y` number, required
  - SchematicJunction — A point where three or more line segments meet, not on any node. Wire/response shape only — runtime junctions live as `JunctionModel`.
    - `id` string, required
    - `x` number, required
    - `y` number, required
    - `arrow_id` string, nullable
  - SchematicTerminal — An endpoint where a line segment reaches the drawing boundary. Wire/response shape only — runtime terminals live as `TerminalModel`.
    - `id` string, required
    - `x` number, required
    - `y` number, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/outerport/apis/outerport-api.md) · [All operations](https://skmtc.dev/outerport/apis/outerport-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/outerport/outerport-api/revisions/f565b46daaea/schema)