Generate API messages with a prompt lets release owners shorten API test setup while keeping the resulting test assets visible in the Tosca Cloud API playground for review.
In the July 2026 release, a user describes the API message they need to an AI assistant, and the assistant creates that message in the API playground through MCP. This is a focused authoring capability, not an autonomous release decision mechanism. Its practical value depends on how well the organization controls access, reviews generated assets, and promotes approved tests into delivery workflows.
What changed in July 2026
Tosca Cloud can now create an API message in the API playground from a natural-language prompt submitted through MCP.
Instead of manually assembling an initial request structure, testers can describe the intended interaction and begin from an AI-generated message. The message is created where API teams already organize and work with their API assets, which keeps it available for inspection and refinement.
For teams maintaining broad service portfolios, this can reduce time spent on repetitive setup work, especially when creating early test coverage for new endpoints or expanding a regression suite.
Why release owners should care
API test creation often becomes a delivery constraint when teams must translate functional requirements into requests, paths, query parameters, headers, payloads, and expected responses under time pressure. Prompt-based creation can speed up the first draft of that work.
The release benefit is operational rather than cosmetic:
- QA teams can begin API test design earlier in a delivery cycle.
- Engineers can review a concrete API message instead of an informal test idea.
