Get Element
API Name
API Name: Element – Get
Overview
This API retrieves a single element from the end system.
MBSE Core uses this API to:
Fetch element details
Perform on-demand synchronization
Retrieve full element state
Support relation and file expansion
Connector responsibility:
Retrieve the element using the end system API with the given
elementId.Respect project and branch scoping.
Based on
expandoptions:Load properties
Load tags
Load relations
Load files
For tags, connector may need to:
Extract tag GUIDs from element metadata
Fetch tag details separately
Fetch relations and files if requested.
Convert all retrieved data into
MbseElementformat.
API URI
Path Parameters
elementId
True
String
ID of the element to retrieve.
URI Parameters
projectId
True
String
ID of the project.
elementTypeId
True
String
ID of the element type.
branchId
False
String
ID of the branch. If omitted, default branch behavior applies.
expand
False
List
Controls which additional information is included. Possible values: PROPERTIES, TAGS, FILES, RELATIONS.
properties
False
List
List of property IDs to include. Applicable only if PROPERTIES is included in expand.
tags
False
List
List of tag IDs to include. Applicable only if TAGS is included in expand.
Expand Parameter Behavior
The expand parameter controls what additional data is returned:
PROPERTIES
Include element properties.
If
propertiesis provided, return only those properties.If omitted, return all properties.
TAGS
Include tagged values.
If
tagsis provided, return only those tags.If omitted, return all tags.
FILES
Include files attached to the element.
RELATIONS
Include element relations.
If expand is omitted, only base element metadata must be returned.
Behavior Rules
The element must be retrieved within the scope of:
projectIdelementTypeIdOptional
branchId
If element does not exist:
Return HTTP
404 Not Found.
If
expandis not provided:Do not return properties, tags, files, or relations.
Respect filtering parameters (
properties,tags).Do not return unrelated data.
Response must strictly follow
MbseElementstructure.
Response Payload
Sample Response
Response Parameters
Element Object
elementId
True
String
Unique element identifier.
name
False
String
Name of the element.
elementTypeId
True
String
ID of the element type.
qualifiedName
False
String
Fully qualified name.
projectId
True
String
Project ID.
createdBy
False
String
User who created the element.
updatedBy
False
String
User who last updated the element.
createdDate
False
String (ISO-8601)
Creation timestamp.
updatedDate
False
String (ISO-8601)
Last update timestamp.
parentElementId
False
String
Parent element ID.
properties
False
Map<String,Object>
Element properties (if expanded).
tags
False
Map<String,Object>
Tagged values (if expanded).
relations
False
List
Element relations (if expanded).
files
False
List
Attached files (if expanded).
Relation Object
relationType
True
String
Type of relation (association, dependency, etc.).
targetElementId
True
String
Target element ID.
targetElementTypeId
True
String
Target element type ID.
projectId
True
String
Project ID.
author
False
String
Creator of relation.
createdDate
False
String
Relation creation timestamp (ISO-8601).
File Object
fileId
True
String
Unique file identifier.
fileName
True
String
File name.
filePath
False
String
File path.
downloadUrl
False
String
File download URL.
label
False
String
File label.
contentType
False
String
MIME type.
contentLength
False
Long
File size in bytes.
author
False
String
File uploader.
fileType
False
String
File category/type.
lastModifiedDate
False
String
Last modified timestamp (ISO-8601).
Example Use Case
Get Element with Properties and Tags
Implementation Guidelines
Always scope element retrieval to project and branch.
Validate element type consistency.
Fetch tags separately if end system stores them independently.
Do not over-fetch data if
expandis not specified.Convert all data strictly into
MbseElementformat.Ensure consistent timestamp formatting (ISO-8601).
Design Rationale
This API provides controlled and expandable element retrieval.
By:
Supporting selective expansion
Supporting property/tag filtering
Maintaining strict scoping
The API ensures performance efficiency and predictable synchronization behavior across heterogeneous MBSE systems.
Last updated

