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

Section
API Name
Required (Yes/No)
Order of Implementation
Overview

Registration APIs

Yes

1

APIs required to register and identify the connector to MBSE Core.

Yes

Returns connector metadata and supported capabilities.

Yes

Returns discovery information and SDK capabilities.

Authentication APIs

Yes

2

APIs required to initialize and cleanup connector sessions.

Yes

Initializes connection with end system, loads cache, validates credentials.

Yes

Cleans up session resources and logs out from end system.

Metadata APIs

Yes

3

APIs required for configuration, metadata discovery, and system understanding.

Yes

Returns server-level configuration such as max page size and timezone.

Yes

Returns all projects available in the end system.

Optional

Returns available workspaces if supported by the system.

Yes

Returns configuration details for a given element type.

Yes

Returns stereotype metadata definitions.

Yes

Returns property metadata for a given element type and stereotype.

Yes

Returns enumeration values for a property or tag.

Multi Element Revision APIs

Yes

4

APIs used for revision-based synchronization.

Yes

Returns list of revisions for a project.

Yes

Returns elements changed between two revisions.

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.

Yes

Retrieves element details based on ID.

Yes

Creates a new element.

Yes

Updates an existing element.

Yes

Searches elements based on criteria and pagination.

Relation APIs

Yes

6

APIs to manage relationships between elements.

Yes

Creates a relation between elements.

Yes

Deletes an existing relation.

Branch APIs

Optional*

7

Required only if branch-based synchronization is enabled.

Optional

Retrieves branch details.

Optional

Creates a new branch.

Optional

Deletes a branch.

Optional

Merges a branch into the main/master/trunk branch.


  1. Registration APIs

  2. Authentication APIs

  3. Metadata APIs

  4. Revision APIs

  5. Element CRUD APIs

  6. Relation APIs

  7. 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.



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