Build Your Own Connector
The following table describes:
The list of MBSE Connector SDK APIs.
Which APIs are mandatory.
Recommended order of implementation.
A brief overview of how MBSE Core calls each API and the expected behavior.
Empty cells in the "Order of Implementation" column indicate optional APIs.
MBSE Connector SDK APIs
Registration APIs
Yes
1
APIs required to register and identify the connector to MBSE Core.
Authentication APIs
Yes
2
APIs required to initialize and cleanup connector sessions.
Metadata APIs
Yes
3
APIs required for configuration, metadata discovery, and system understanding.
Multi Element Revision APIs
Yes
4
APIs used for revision-based synchronization.
Optional
Returns element snapshot at a given revision. Required if diff details are not provided in the Get Elements Changed In Revision API.
Element APIs
Yes
5
Core CRUD APIs for elements.
Relation APIs
Yes
6
APIs to manage relationships between elements.
Branch APIs
Optional*
7
Required only if branch-based synchronization is enabled.
Recommended Order of Implementation
Registration APIs
Authentication APIs
Metadata APIs
Revision APIs
Element CRUD APIs
Relation APIs
Branch APIs (if applicable)
This order ensures:
Connector registration is validated first.
Session handling works properly.
Metadata configuration is accurate.
Revision synchronization is stable.
Element-level operations are reliable.
Relation handling is consistent.
Branch lifecycle is managed safely.
Mandatory vs Optional APIs
Mandatory APIs
These APIs are required for:
Revision-based synchronization
Element CRUD operations
Metadata configuration
Connector registration
Without these, the connector cannot function.
Optional APIs
These APIs are required only if:
Branch-based synchronization is enabled.
Workspace concept exists in the system.
Important Notes
All APIs must follow MBSE SDK URI structure.
All APIs must implement standardized error handling.
Pagination must be implemented where required.
ISO-8601 date format must be used for timestamps.
Expand behavior must be respected for performance optimization.
Connector must convert all responses into MBSE DTO structures.
Related Pages
This page serves as the master checklist for building an MBSE connector.
Implement APIs in the recommended order to ensure stable and predictable integration behavior.
Last updated

