Model API Server

Read Operations

Mutation Operations (Plan/Apply)

View Operations

Script Execution

Plan/Apply Pattern (Mutations)

All model mutations use POST /model/apply with a changes array. Each change has an op field:

Model operations: createElement, createOrGetElement, createRelationship, createOrGetRelationship, updateElement, updateRelationship, deleteElement, deleteRelationship, setProperty, moveToFolder, createFolder

View operations: addToView, addConnectionToView, nestInView, deleteConnectionFromView, styleViewObject, styleConnection, moveViewObject, createNote, createGroup, createView, deleteView

Workflow

1. Apply -- POST /model/apply with { "changes": [...] }. Returns operationId immediately.
2. Poll -- GET /ops/status?opId=<id> until status is complete or error.
3. Undo -- All changes appear in Archi's Edit > Undo menu.

TempId Cross-referencing

Operations within a single batch can reference each other using tempId:

{
  "changes": [
    { "op": "createElement", "type": "business-actor", "name": "Actor A", "tempId": "t1" },
    { "op": "createElement", "type": "business-process", "name": "Process B", "tempId": "t2" },
    { "op": "createRelationship", "type": "serving-relationship", "sourceId": "t1", "targetId": "t2", "tempId": "t3" },
    { "op": "addToView", "viewId": "view-id-here", "elementId": "t1", "tempId": "v1", "x": 50, "y": 50 },
    { "op": "addToView", "viewId": "view-id-here", "elementId": "t2", "tempId": "v2", "x": 300, "y": 50 },
    { "op": "addConnectionToView", "viewId": "view-id-here", "relationshipId": "t3", "autoResolveVisuals": true }
  ]
}

The response includes tempIdMappings that map each tempId to its resolved real ID.

Duplicate Handling

Set duplicateStrategy at the request level or onDuplicate per-operation:

• "error" (default) -- fail if a same-type/same-name element exists
• "reuse" -- return the existing element instead of creating a new one
• "rename" -- auto-rename with a suffix (e.g., "Actor (2)")

Idempotency

Include "idempotencyKey": "unique-key" in the apply request body. Replaying the same key within 24 hours returns the existing operation result instead of re-applying.

Script Execution via API

POST /scripts/run executes JArchi code on the SWT display thread:

{ "code": "var elements = findElements('business-actor'); __scriptResult.value = elements;" }

Preamble helpers available in API-executed scripts (no need to load libraries):

• getModel() -- get the server's bound model
• findElements(type) -- find elements (returns array of {id, name, type, documentation})
• findViews(name) -- find views
• findRelationships(type) -- find relationships
• model -- pre-bound to the server's model
• $() -- auto-scoped to the server's model
• __scriptResult.value -- set return value
• __scriptResult.files -- set output file paths

Limitation: JArchi proxy mutators fail in API script context because CommandHandler.compoundcommands is null:

• element.name = "..." — NPE
• el.prop(key, value) — NPE from CommandHandler.executeCommand
• Use /model/apply with updateElement/setProperty for single changes
• For bulk property updates, raw EMF in /scripts/run is most reliable:

  var el = ArchimateModelUtils.getObjectByID(model, id);
  var props = el.getProperties();
  for (var i = 0; i < props.size(); i++) {
      if (props.get(i).getKey().equals(key)) { props.get(i).setValue(val); return; }
  }
  // Add new property if not found
  var p = IArchimateFactory.eINSTANCE.createProperty();
  p.setKey(key); p.setValue(val); props.add(p);
  

  Note: raw EMF mutations bypass the undo stack (not Ctrl+Z undoable).

Path note: __DIR__ is automatically replaced with __scriptsDir__ in API-executed scripts. Use __scriptsDir__ when loading libraries (e.g., load(__scriptsDir__ + "lib/log.js")).

Common curl Patterns

# Health check
curl http://localhost:8765/health

# Search elements by name
curl -X POST http://localhost:8765/model/search \
  -H "Content-Type: application/json" \
  -d '{"namePattern": "Customer", "type": "business-actor"}'

# Create an element
curl -X POST http://localhost:8765/model/apply \
  -H "Content-Type: application/json" \
  -d '{"changes": [{"op": "createElement", "type": "business-process", "name": "New Process"}]}'

# Poll operation status
curl "http://localhost:8765/ops/status?opId=op_1234567890"

# Export view as PNG
curl -X POST http://localhost:8765/views/VIEW_ID/export \
  -H "Content-Type: application/json" \
  -d '{"format": "png", "scale": 2}'

Critical Constraints

• Always open a view before starting the server — the undo/redo command stack requires an open editor
• Use POST /model/search for targeted lookups instead of POST /model/query (which returns the full snapshot)
• POST /scripts/run runs synchronously on the SWT display thread — long-running scripts block other API requests
• Rate limit: 600 requests/minute. Max request body: 1 MB. Max changes per apply: 1000.
• The full OpenAPI 3.1 specification is in context/openapi.yaml

Reference Files

For detailed endpoint schemas and operation specifications, consult these files in this skill's directory:

• references/endpoint-reference.md -- Consult when constructing API requests: full request/response schemas, query parameters, and example responses for every endpoint
• references/plan-apply-operations.md -- Consult when building changes arrays for /model/apply: all 21 change operation types with field descriptions, type enums, and a complete batch example