Tricentis Tosca Application API Endpoints used by ConnectALL

Products

• ConnectAll On-Prem
• ConnectALL
• ConnectAll SaaS

Issue/Introduction

We would like to request your support in identifying the exact API endpoints used by ConnectALL for integration with Tosca, in order to proceed with our internal API Gateway implementation and validation activities.

As part of our architecture, we need to virtualize and expose the required Tosca APIs through our API Gateway (Axway). While we already have access to the general Tosca REST API documentation, our integration team requires the specific endpoints actively used by ConnectALL, rather than the full API set (which includes 35+ endpoints).

In particular, we kindly ask for:

• A list of exact Tosca API endpoints used by ConnectALL (including methods such as GET, POST, etc.)
• Typical API patterns or examples (e.g., /rest/ToscaCommander/{workspace}/object/{object-id}/association)
• Any available documentation, Swagger/OpenAPI specification, or reference material
• Clarification on whether ConnectALL uses a fixed set of endpoints or dynamically interacts with Tosca APIs

This information is critical to:

• Define the scope of APIs to be virtualized
• Avoid unnecessary exposure of endpoints
• Ensure a secure and maintainable integration setup

Environment

4.x

Resolution

Attached document lists all the API endpoints that ConnectALL invokes to communicate with the Tricentis Tosca application. The endpoints are organized by functional category and HTTP method.