API messages can now be generated from OpenAPI or WSDL specifications, giving release owners a faster route from interface definition to executable API testing. The October 2026 release also expands the assets that teams can share across workspaces, supporting more consistent test design and configuration reuse.
Generate API messages from specifications
Teams can create API messages from an API specification instead of building them manually. The release specifically supports specifications such as OpenAPI and WSDL.
For enterprise API testing, this change can shorten initial test preparation when services are defined through governed interface contracts. It also gives QA and development teams a common starting point for API-message design, reducing avoidable variation between projects.
Practical workflow implications include:
- Start API test design from an existing/established OpenAPI or WSDL definition.
- Reduce repetitive message construction for documented services.
- Create a more repeatable handoff between API design, development, and quality teams.
- Review generated messages within existing test governance before using them in release playlists.
The control point remains important with a generated API message accelerates authoring, but it does not replace validation of authentication, test data, assertions, negative scenarios, or service-level risk coverage.
Expand reuse across workspaces
Tosca Cloud now allows more asset types to be shared with teams across multiple workspaces. Newly shareable assets include:
- Test cases
- Parameter sets
- Mobile connections
- API connections
- Data Integrity connections
- Capability sets
This broader sharing model matters where multiple delivery teams test common services, mobile-device configurations, or data-validation patterns. Rather than recreating equivalent assets in separate workspaces, organizations can establish reusable assets with clear ownership and change controls.
Governance considerations for release leaders
Cross-workspace reuse can reduce maintenance, but it increases the importance of asset stewardship. Teams should define who owns shared API connections, parameter sets, and capability sets; how changes are reviewed; and which workspaces may consume a shared asset.
For audit and operational control, consider documenting:
- Asset owners and approved maintainers.
- Naming conventions that distinguish shared assets from team-specific variants.
- Review expectations before changes affect consuming workspaces.
- Evidence needed to show which shared test assets supported a release decision.
A governed shared-asset model helps prevent parallel teams from testing the same integration with conflicting connection details or parameter values. It also makes the effects of asset changes easier to assess across a portfolio.
Rollout timing
Some October 2026 capabilities are rolling out gradually and may take a few days to appear in an environment. Release managers should verify availability before scheduling enablement sessions or making shared-asset workflow changes dependent on these functions.
How Merito helps
Merito can help teams define operating practices for API-test adoption, shared-asset ownership, workspace controls, and evidence requirements for release governance. For ongoing administration and quality engineering support, review Managed Services and the Tricentis practice overview.
For prior context on access governance and playlist configuration, see Tricentis Tosca Cloud September 2026.
Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory. Our Tricentis Tosca Cloud team helps you adopt the October 2026 changes, with implementation services to configure them for your environment and training and enablement to bring your teams up to speed.