Intercax is excited to announce the release of Syndeia 3.7.1.

In this section, the availability, downloads, and the list of improvements in Syndeia 3.7.1 are presented.

Availability

1. Syndeia 3.7.1 is available for download starting Jun 1, 2026.

2. Syndeia 3.7.1 includes:

   1. Syndeia Cloud 3.7.1, including Syndeia Web Dashboard

   2. Syndeia Cloud REST API 3.7.1

   3. Syndeia local clients 3.7.1

      1. Syndeia MagicDraw/Cameo plugin

      2. Syndeia Rhapsody plugin

      3. Syndeia Standalone

Downloads and Installation

1. Existing Syndeia users with an active subscription can request downloads for Syndeia 3.7.1 by opening a request on our helpdesk.

2. For Syndeia local clients, follow the instructions under the Installation sections.

   1. MagicDraw/Cameo plugin - Installation - Syndeia for MagicDraw | Cameo

   2. Rhapsody plugin - Installation - Syndeia for Rhapsody

   3. Standalone - Syndeia Standalone

3. For Syndeia Cloud, follow the instructions here: Deployment & Maintenance

   1. New users, who are downloading Syndeia for the first time, should directly get started with Syndeia Cloud 3.7.1. Refer to: Deployment Methods. Select one from three different deployment approaches:

      1. Containerized Deployment

      2. Ansible Deployment

      3. Automated Deployment

   2. Users working with Syndeia Cloud 3.7 can upgrade to 3.7.1. Refer to: Upgrades and Migration.

Improvements

1. Syndeia Cloud Web Dashboard Improvements

1.1. Repository-specific color preferences

Syndeia 3.7.1 enables users to set color preferences specific to a repository. Two repositories of the same repository type can now have different display colors in the Digital Thread Explorer and graph visualization. Color preferences for a repository can be set under Repository Settings → Preferences, as shown below.

Open

Set color preferences for a repository under Repository Settings

When browsing digital thread projects in the DTE, the repository-specific colors can be seen. The figure below shows an example of digital thread relations between Teamwork Cloud (TWC) 2024x and 2026x repositories.

Open

Repository-specific colors visible in Digital Thread Explorer, as shown for relations between Teamwork Cloud 2024x & 2026x elements.

• Specific Improvement: SYN-5809

1.2. Digital Thread Explorer (DTE) Backend Improvements

Syndeia 3.7.1 includes significant improvements in the DTE backend for graph visualization and navigation of both intra-model (within a repository) and inter-model (across repositories) relations in the digital thread. This set of improvements are focused on backend API calls, performance, graph rendering, component reuse, and other aspects. This set of improvements are foundational to major new features in the offing for the DTE in upcoming Syndeia releases.

• Specific improvement: SYN-5262

1.3. Repository-specific Attribute Selection

Syndeia 3.7.1 includes improvements in the user interface for selecting attributes to display for each artifact type in a repository. This capability is available under Repository Settings → Preferences tab for each repository, as also shown in the figure with 1.1 above.

• Specific improvement: SYN-5657

2. Syndeia Cloud API Improvements

2.1. Performance improvement in PUT requests

Syndeia Cloud 3.7.1 REST API includes performance improvements in PUT requests when repositories, container, artifacts relations, and their types are persisted in Syndeia for the digital thread graph.

• Specific improvement: SYN-5856

2.2. Repository-specific colors via API

As an API-first platform, all Syndeia capabilities are available via its REST API. The repository-specific color preferences, as presented in section 1.1 above, can also be set using the Syndeia API via PUT repository endpoint. Background and foreground colors can be assigned using hex codes.

• Specific improvement: SYN-5822

3. Syndeia Pipeline and API Cookbook Improvements

Syndeia 3.7.1 includes an expanded cookbook for Pipelines and API notebooks (Jupyter). Refer to the following pages for details.

• Pipelines Cookbook lists 28 pipelines shipped with this release.

• API Cookbook lists 28 Jupyter notebooks shipped with this release.

• Overall, Syndeia 3.7.1 includes 56 working examples of pipelines and notebooks for automating digital engineering workflows using the Syndeia API.

• Specific improvements: SYN-5874, 5873, 5828, 5783, 5782, 5746, 5841, 5740, 5741, 5737, 5712, 5708, 5701, 5552

4. Integration Improvements

Syndeia 3.7.1 comes with significant improvements to existing integrations. These improvements are listed below and organized alphabetically by the integrated applications.

4.1. Azure DevOps

4.1.1. Improved search for projects and work items

Syndeia 3.7.1 includes improvements related to paginated responses when searching projects (containers) and work items (artifacts) in the Syndeia Web Dashboard, Client Dashboard, and API for Azure DevOps repositories. For searching work items, these improvements are related to the display of results when executing Work Item Query Language (WIQL) expressions in Syndeia.

• Specific improvement: SYN-5675

4.1.2.Fixed relation direction display issue on Web Dashboard

Syndeia 3.7.1 fixes an issue related to the display of relation directions when viewing incoming and outgoing relations for an Azure DevOps artifact in the Web Dashboard Tree View.

• Specific improvement: SYN-5673

4.1.3. Improved compare and sync of Integer attributes in Syndeia Clients

Syndeia 3.7.1 resolves an issue with the compare and sync of artifact attributes typed by Integer in Syndeia Clients (Cameo and Rhapsody plugins) for Azure DevOps repositories.

• Specific improvement: SYN-5890

4.1.4. Improved sync of Reference relations in Syndeia Clients

Syndeia 3.7.1 resolves an issue with the sync of reference relations in Syndeia Clients (Cameo and Rhapsody plugins) from/to artifacts in Azure DevOps repository.

• Specific improvement: SYN-5681

4.2. Bitbucket

4.2.1. Upgrades related to deprecated endpoints in Bitbucket API

Syndeia 3.7.1 includes upgrades that use newer endpoints provided by the Bitbucket API and removes the usage of recently deprecated endpoints.

• Specific improvement: SYN-5840

4.2.2. Fetch all attributes for Bitbucket artifacts

Syndeia 3.7.1 includes improvements related to attributes of Bitbucket artifacts, such as branch, commit, tag, content (file/folder), commit diffs, and others. Syndeia will return all attributes of Bitbucket artifacts when includeAttributes query parameter is set to ALL in the Syndeia Bitbucket endpoints. Until 3.7.1, these endpoints were returning only the key attributes, but not all. This improvement applies to both Bitbucket Cloud and Data Center.

• Specific improvements: SYN-5700, SYN-5709, SYN-5657

4.3. Codebeamer

4.3.1. Improved support for Codebeamer 3.x releases

Syndeia 3.7.1 provides improved support for Codebeamer 3.x releases. These improvements are related to the changes in the Codebeamer native API related to incoming/outgoing relations between artifacts (tracker items).

• Specific improvements: SYN-5677, SYN-5761, IHD-5532

4.3.2. Improved support for custom fields in Codebeamer

Syndeia 3.7.1 provides improved support for custom fields of trackers and tracker item artifacts in Codebeamer. These improvements are related to the fetching, setting, and updating the values of custom fields via Syndeia Codebeamer API endpoints, resulting in improvements in transform, compare, and sync operations in Syndeia Client (Cameo and Rhapsody plugins) and Syndeia Cloud Pipelines.

• Specific improvements: SYN-5775, SYN-5769, IHD-5481, IHD-5421

4.3.3. Resolves issue with navigating to Codebeamer from Digital Thread Explorer

Syndeia 3.7.1 resolves an issue with the More Details menu action when a user right-clicks on any Codebeamer artifact in the Digital Thread Explorer (DTE). This menu action is supposed to open the selected artifact in Codebeamer’s native web application. However, in certain scenarios this was not functioning as expected since the HTML URL was not being set correctly when Codebeamer artifacts were fetched via relations in the DTE. This issue has been resolved in 3.7.1.

• Specific improvements: SYN-5904, SYN-5765

4.4. DS-E3

4.4.1. Test endpoint on DS-E3 API

Syndeia 3.7.1 fixes an issue with the test endpoint on Syndeia DS-E3 API. This endpoint was returning a 201 instead of a 200 status code when the connectivity test to a DS-E3 repository was successful. This issue has been resolved.

• Specific improvement: SYN-5738

4.5. GENESYS

4.5.1. Unauthorized response on invalid auth tokens

Syndeia 3.7.1 includes an improvement to the GENESYS GET container endpoints. These endpoints were returning a 500 status code when requested with invalid or expired auth tokens because the native GENESYS GET project API endpoints were doing so. Starting with 3.7.1, Syndeia GENESYS GET container endpoints will return a 401 (Unauthorized) status code for invalid auth tokens even if the native GENESYS GET project endpoints return a 500.

• Specific improvement: SYN-4788

4.6. GitHub

4.6.1. Fetch and Display All Attributes

Syndeia 3.7.1 includes improvements related to attributes of GitHub artifacts, such as file, folder, commit, branch, issue, tags, and others. Syndeia will return all attributes of GitHub artifacts for selection in GitHub repository preferences (as shown below) or when making Syndeia API calls.

Open

All GitHub artifact attributes available for selection under Repository Settings

Selected GitHub artifact attributes can be seen in the Details panel when browsing GitHub repositories, as shown below.

Open

Display of GitHub artifact attributes in the Details panel

• Specific improvement: SYN-5693

4.7. Jama

4.7.1. Grant Type for OAuth sign-in

In Syndeia 3.7, the Grant Type field was editable and set to an incorrect default value when connecting to Jama repositories using OAuth. This issue has been resolved in 3.7.1. Grant Type is set to client_credentials and is not editable, conforming to Jama API for OAuth sign-in.

Open

Grant Type is set to client_credentials and not editable

• Specific improvement: SYN-5795

4.8. Jira

4.8.1. Improved Support for Changes in Jira Cloud and Data Center

Both Jira Cloud and Jira Data Center API endpoints for fetching artifact (issue) types and their attribute definitions have recently evolved. Syndeia 3.7.1 provides improved support for these recent changes in Jira API endpoints related to issue types and allowable attributes.

• Specific improvements: SYN-5707, SYN-5772, SYN-5690, IHD-5335

4.8.2. Artifact (Issue) Types in Repository Preferences

Syndeia 3.7.1 resolves an issue with duplicate artifact (issue) types showing up under Repository Preferences. When a container (project) is selected, the exact list of artifact (issue) types relevant for that container are visible for selection.

Open

• Specific improvement: SYN-5834

4.8.3. Attribute Definitions for Artifact (Issue) Types

Due to changes in the native APIs for Jira Cloud and Jira Datacenter, the following changes were done in the Syndeia Cloud Jira endpoints.

1. The GET all artifact types endpoint (GET /external/jira/{repoKey}/types/artifact) does not provide the includeAttributeDefinitions query parameter anymore. This endpoint can return Jira artifact (issue) types in a given project (container.externalKey) but not the attribute definitions (issue field types).

2. The GET artifact type by external key endpoint (GET /external/jira/{repoKey}/types/artifact/{externalKey}) also requires the key of the parent Jira project (container.externalKey) to be provided if the attribute definitions are requested (includeAttributeDefinitions = ALL), and will return all attribute definitions of the given artifact (issue) type in the given Jira project.

3. The GET artifact type by external id endpoint (POST /external/jira/{repoKey}/types/artifact/external/id) has the same changes as (2) above.

• Specific improvement: SYN-5798

4.9. Teamwork Cloud (TWC)

4.9.1. Improved support for Teamwork Cloud 2026x

Syndeia 3.7.1 includes improved support for TWC 2026x. There was an issue expanding model elements that contain other nested model elements using TWC’s native API. Expansion of model elements in the Syndeia Tree View was not showing nested model elements correctly. This issue has been resolved in the 3.7.1 release.

• Specific improvement: SYN-5754

4.9.2. New Tutorials for TWC on Web Dashboard

Syndeia 3.7.1 includes new tutorials for Teamwork Cloud on Syndeia Web Dashboard. These new tutorials showcase the significant improvements made in Teamwork Cloud integration in 3.7 and further enhancements in 3.7.1. Refer to the tutorials here:

• Exercise 20.1 - Teamwork Cloud Integration on Web Dashboard

• Exercise 20.2 - Exploring the Search/Details/Relations Tab and Graph View of TWC Artifacts

• Exercise 20.3 - Digital Thread Queries for Teamwork Cloud

• Specific improvements: SYN-5509, SYN-5717, SYN-5718, SYN-5736

4.9.3. Documentation metadata available via Syndeia Cloud TWC API

Each element in a Cameo model (UML, SysML, UAF) has a Documentation/Comments metadata field. This field is used by end users to provide documentation or description for elements in a model, as shown for a UAF Capability element in the figure below.

Open

Documentation/Comments field for an element in Cameo

In Syndeia 3.7.1, this Documentation metadata field and its value is available via the Syndeia Cloud TWC API. The Documentation field value is stored as a UML Comment element nested under the main element when the Cameo model is persisted in Teamwork Cloud. The value of this field is available via the Syndeia Cloud TWC API endpoints and also now visible in the Web Dashboard, as shown in the figure below.

This field is used by Syndeia Pipelines to automatically generate reports, e.g. Confluence pages, for Teamwork Cloud models.

Open

Documentation field available via Syndeia Cloud TWC API endpoints and Web Dashboard

• Specific improvement: SYN-5808

4.9.4. User-Id is not mandatory for endpoints

In Syndeia 3.7, User-Id was a mandatory header field that needed to be supplied for all Syndeia Cloud TWC API endpoints. However, this header should only be required when using Basic Auth and not required when using OAuth. This issue has been resolved in Syndeia 3.7.1. The User-Id header is not mandatory for Syndeia Cloud TWC endpoints.

• Specific improvements: SYN-5710, SYN-5826

4.9.5. New API Cookbook for Teamwork Cloud

Syndeia 3.7.1 includes a new API Cookbook demonstrating the use of Syndeia Cloud TWC integration endpoints for navigating and querying UML/SysML/UAF model elements and relations in Teamwork Cloud.

• Specific improvement: SYN-5524

4.10. Windchill

Syndeia Cloud 3.7.1 includes the following improvements for the Windchill integration API endpoints in the Syndeia Cloud REST API.

4.10.1. Windchill Tree View Improvements

Syndeia 3.7.1 includes significant improvements to the Windchill Tree View in the Syndeia Web Dashboard. Some of the key improvements are listed here and illustrated in the figure below.

• View the Version displayed next to each part

• View Version History of each part

• View Uses and Occurrence relations separately under each part

• View Described By docs associated with each part

• View References docs associated with each part

• View Related CAD Docs (EPM docs) associated with each part

Open

Windchill Tree View improvements

For additional details, refer to the revised Windchill repository navigation guide for Syndeia Web Dashboard: Windchill Repositories.

These improvements are also available for the Syndeia Client Dashboard (e.g. Cameo plugin): Exercise 4.1 - Browsing Windchill Tree in Syndeia

• Specific improvements: SYN-5750, SYN-5751, SYN-5752, SYN-5753

4.10.2. Windchill improvements in Syndeia Clients

Syndeia 3.7.1 brings significant improvements for Windchill integration in the Syndeia Client Dashboard, e.g. Cameo plugin, Rhapsody plugin, and Standalone. Some of the key updates are as follows.

• Connecting to Windchill repositories using OAuth2 from Syndeia Client is enabled. Refer to the following:

  • Adding Windchill repository using OAuth

• Custom mappings are supported for Windchill model transforms. See tutorial links below.

• New step-by-step tutorials for Windchill with custom mappings are available. Refer to the following:

  • Exercise 4.1 - Browsing Windchill Tree in Syndeia

  • Exercise 4.2 - Creating SysML - Windchill Mappings

  • Exercise 4.3 - SysML to Windchill Model Transform with Mappings

  • Exercise 4.4 - Windchill to SysML Model Transform with Mappings

• Windchill integration on Syndeia Client now depends on Syndeia Cloud Windchill service that uses the Windchill REST API. Syndeia Client does not use the old Windchill InfoEngine services. This implies that the Windchill jar files (libWC folder) is no longer needed.

• All improvements related to Windchill Tree View presented above for the Web Dashboard also apply for the Client Dashboard.

• Digital thread relations created between SysML and Windchill artifacts from the Syndeia Clients (Cameo or Rhapsody plugin) in any Syndeia release until 3.7 were using the old Windchill InfoEngine services. A new Windchill Relation Migration Utility is available with Syndeia 3.7.1. release to migrate and upgrade these digital thread relations to use the new Windchill integration with support for custom mappings. Refer to the following page for details: Windchill Relations Migration (Syndeia 3.7.1).

• Specific improvements: SYN-3643, SYN-5861, SYN-5847, SYN-5814, SYN-5869, SYN-2689

4.10.3. Display Usage relations only in DTE

Windchill has two types of relations to represent the decomposition of assemblies into sub-assemblies and parts, namely Uses and Occurrences. Uses relations are the default. If reference designators are provided for each Uses relation, Windchill also creates Occurrence relations. In the Syndeia Tree View for a Windchill repository, users can see both Uses and Occurrence, as shown below.

Open

Both Uses and Occurrence relations are shown in the Tree View

However, showing both in the graph view results in duplicate and overlapping edges. Starting with Syndeia 3.7.1, Uses relations are shown and Occurrence relations are hidden in the Digital Thread Explorer when navigating Windchill repository, as shown below.

Open

Uses relations are shown and Occurrence relations are hidden in the Digital Thread Explorer (Graph View)

• Specific improvement: SYN-5837

4.10.4. Improved response in fetching folder contents

Syndeia 3.7.1 includes improvements in API endpoints to fetch folder contents without making any extra calls. This change leverages recent improvements in the native Windchill API. For end users, this implies improved response times when fetching folder contents on the Syndeia Web Dashboard, Client Dashboard, and via the Syndeia Windchill API endpoints.

• Specific improvement: SYN-5694

4.10.5. User-Id is not mandatory for endpoints

In Syndeia 3.7, User-Id was a mandatory header field that needed to be supplied for all Syndeia Cloud Windchill API endpoints. However, this header should only be required when using Basic Auth and not required when using OAuth. This issue has been resolved in Syndeia 3.7.1. The User-Id header is not mandatory for Syndeia Cloud Windchill endpoints.

• Specific improvement: SYN-5710

4.10.6. Get attributes of Windchill relations in Syndeia Windchill API endpoints

Syndeia 3.7.1 enables API users to fetch attributes of Windchill relations (e.g. Uses and Occurrences) in the Syndeia Windchill API endpoints. As an example, users can fetch quantity, reference designator, and other attributes for Uses relations.

• Specific improvement: SYN-5859

4.10.7. Improvements in Windchill Delete operations using OAuth2

Syndeia 3.7.1 resolves an issue with deletion of relations (e.g. Uses or Occurrences) in Windchill when connected using OAuth2. In some cases, relations won’t be deleted when connected using OAuth2. This has now been resolved.

• Specific improvement: SYN-5842

4.10.8. Windchill Content Security Policy (CSP) update for dynamic loading of icons

For EPM/CAD Documents, Syndeia Windchill integration uses custom icons received as part of the API response. Syndeia Cloud Web Dashboard will fetch these icons and show them dynamically, maintaining consistency with Windchill native UI. Refer to the CSP filter updates added for Windchill in Syndeia Cloud Web Gateway (application.conf) here: Web-Gateway Content Security Policy (CSP) Allowlisting.

• Specific improvement: SYN-5780

4.10.9. Improved error handling on Windchill assembly reference designators and component ids

Syndeia 3.7.1 resolves an issue with reference designators and component ids for part usages and occurrences in a Windchill part (assembly). Specifically, there are cases in certain Windchill deployments where the native Windchill API returns a value = null versus empty or no value. Syndeia 3.7.1 provides improved handling of these edge cases.

• Specific improvements: SYN-5763, IHD-5398

4.11. VOLTA

4.11.1. Support for API v2 added, v1 removed

Syndeia Cloud 3.7.1 is upgraded to use version 2 (v2) of the VOLTA API. Version 1 (v1) of the VOLTA API was deprecated in VOLTA 2025R1, and is removed and no longer supported in VOLTA 2026R1 release. As a result of this change, Syndeia has been updated to use VOLTA API v2, starting with this 3.7.1 release.

• Specific improvements: SYN-5825, 5839

4.11.2. User-Id is not mandatory for endpoints

In Syndeia 3.7, User-Id was a mandatory header field that needed to be supplied for all Syndeia Cloud VOLTA API endpoints. However, this header should only be required when using Basic Auth and not required when using OAuth. This issue has been resolved in Syndeia 3.7.1. The User-Id header is not mandatory for Syndeia Cloud VOLTA endpoints.

• Specific improvement: SYN-5710

5. Syndeia Client Dashboard

Section 4 above details out the integration-specific improvements in Syndeia 3.7.1 release. All of these improvements apply to both Syndeia Web Dashboard and Syndeia Client Dashboard. In this section, additional general improvements for Syndeia Client Dashboard in 3.7.1 are listed.

5.1. Connecting to Syndeia Cloud using OAuth2

Syndeia 3.7.1 adds the capability to connect to Syndeia Cloud from Syndeia Clients (e.g. Cameo Plugin, Rhapsody Plugin, or Standalone) using OAuth2. Support for OAuth2 sign-in was added in Syndeia Cloud API with 3.7 release, Starting with 3.7.1, Syndeia Client will be able to connect to Syndeia Cloud using OAuth2, as shown below.

Open

Connect to Syndeia Cloud from Syndeia Client using OAuth2 flow

For additional details, refer to the Syndeia Client docs for OAuth2 sign-in here: Connecting to Syndeia Cloud using OAuth

• Specific improvements: SYN-5674, SYN-5862, SYN-5843, IHD-5607, IHD-5364

5.2. Windchill integration improvements

Refer to the Windchill improvements in Syndeia Clients sub-section under the Windchill section.

Syndeia 3.7.1 - Improvements

5.3. Improved support for IBM Rhapsody 10.x

Syndeia 3.7.1 Rhapsody plugin includes improved support for Rhapsody 10.x.

• Specific improvements: SYN-4982, IHD-5400, IHD-4547

5.4. Fix for Export to Excel functionality

Syndeia 3.7.1 includes fixes for the Export to Excel functionality in the Syndeia Client dashboard. The Export to Excel capability was failing in some scenarios. The underlying issues have been resolved.

• Specific improvement: SYN-4486

6. Syndeia Cloud Deployment Improvements

In this section, the new features and improvements related to Syndeia Cloud deployment in the 3.7.1 release are presented.

6.1. Containerization Deployment Upgrade

Containerized deployment was introduced as a new feature in the Syndeia 3.7 release. As a result, Syndeia 3.7.1 includes instructions for upgrading containerized deployment from 3.7 → 3.7.1. Refer to the following page for details: Upgrading with Docker (3.7 -> 3.7.1)

• Specific improvements: SYN-5697, SYN-5906

6.2. Ansible Deployment Upgrade

Ansible playbook-based deployment was introduced as a new feature in the Syndeia 3.7 release. As a result, Syndeia 3.7.1 includes instructions for upgrading Ansible deployment from 3.7 → 3.7.1. Refer to the following page for details: Upgrading with Ansible (3.7 -> 3.7.1).

• Specific improvement: SYN-5696

In addition to the Containerized and Ansible deployment upgrades, instructions for the Automated (scripted) deployment upgrade are also available at: Upgrading with Syndeia Automated Deployment (3.7 -> 3.7.1).

6.3. Instructions for configuring MS Entra as a SAML2 Identity Provider

Syndeia Cloud can be configured for Single Sign On (SSO) using any SAML2 Identity Provider (IdP). This includes Okta, Ping Federate, Microsoft Entra, and others. With the Syndeia 3.7.1 release, we have added specific instructions for configuring MS Entra as a SAML2 IdP for Syndeia Cloud. Refer to this page for details: SAML2 and Microsoft Entra.

• Specific improvement: SYN-5399

6.4. Containerized Deployment - Enabling HTTPS and Certificates

Syndeia 3.7.1 provides two key features related to enabling HTTPS and certificates for Containerized deployment.

1. For a fresh containerized deployment of Syndeia 3.7.1, admins can automatically configure HTTPS with a self-signed certificate during the setup. For details, refer to the following page: Containerized Deployment Guide 3.7.1

2. For upgrading HTTPS-enabled containerized deployment from 3.7 → 3.7.1, the HTTPS enablement and certificates will carry forward to the resulting 3.7.1 containerized deployment. For details, refer to the following page: Upgrading with Syndeia Automated Deployment (3.7 -> 3.7.1)

• Specific improvement: SYN-5882

6.5. Cassandra 4.1.9 as the default Cassandra version

Syndeia 3.7.1 deployments use Cassandra 4.1.9 as the default version instead of Cassandra 4.1.0. This has been done to leverage security improvements in Cassandra 4.1.9. This change is applicable for all deployment modes - Automated, Ansible, and Containerized.

• Specific improvement: SYN-5608

7. Other Improvements

In addition to the specific improvements listed above, Syndeia 3.7.1 includes significant improvements related to the following.

• Syndeia Documentation (this site)

• Syndeia Cloud REST API Documentation - Swagger doc

• Syndeia Cloud Deployment

• Syndeia Web Dashboard usability