ReadyAPI 4.1.0 አውርድ

Coming Soon: ReadyAPI MCP Server - Early July
ReadyAPI 4.1.0 lays the groundwork for agentic workflows through MCP tools. To keep you in control of your data and workspace, MCP support is opt-in and only active once you install the ReadyAPI MCP Plugin, releasing in early July.
Once installed, you'll be able to connect Claude, GitHub Copilot, Cursor, and other AI assistants directly to your ReadyAPI workspace and describe what you need in plain English - the MCP Server handles the rest:
- Generate tests - Scaffold test cases from any OpenAPI spec in seconds.
- Detect spec changes - Surface-breaking changes and the exact tests they affect.
- Heal failing tests - Apply AI-recommended fixes directly to your project.
- Run and inspect - Trigger test runs and fetch per-step results without leaving your AI assistant.
Works with Claude Desktop, VS Code + Copilot, Cursor, and any MCP-compatible client. Requires ReadyAPI 4.1.0 or later.
UI Update Notice
ReadyAPI 4.0.0 introduced a refreshed user interface.
During the documentation update process, some screenshots and videos may display the previous UI. Functionality and workflows remain unchanged.
ReadyAPI 4.1.0 includes the following updates. See Version History for changes in previous releases.
SmartBear AI Enhancements
- SmartBear AI is now available for SLM on-premises floating license users: With an SLM on-premises license installed and SmartBear AI enabled, your license is automatically validated against SLM SaaS and connected to the SmartBear AI endpoint. Ensure the SmartBear AI endpoint is whitelisted on your network. For more information, see Requirements on the Generate Tests with SmartBear AI page.
UI Enhancements
- Improved REST and SOAP Request Editor experience: The Request Editor now has a cleaner, more consistent layout with better use of space across panels, toolbars, input fields, and buttons - making it easier to navigate and work with your requests.
- Improved Data Source editor consistency: Grid, Groovy, XML, and JSON data source views now share a unified look and feel, with consistent spacing, alignment, and controls across all formats.
- Improved Security Test Transaction Log consistency: The Security Test Transaction Log now matches the appearance of the Functional Test Transaction Log, giving you a consistent experience across test reporting views.
Security Enhancements
- Authorization profiles in the Auth Repository can now be encrypted: Encrypt your authorization profiles by enabling the Encrypt Authorization Profiles (Auth Repository) setting in Project Properties. This setting is off by default and is independent of project-level encryption. Note that projects with encrypted authorization profiles are not backward compatible with older versions of ReadyAPI. For more information, see Encrypt authorization profiles on the Authentication page.
Virtualization Enhancements
- Response latency is now configurable per endpoint: Configure response latency per endpoint within each Virtual Action to inherit the service-level latency or override it with a fixed value or range, enabling more realistic simulation of services where different endpoints have different response times. For details, see Latency on the Behavior Settings page.
- Conditional Match now captures Path and Query parameters when recording from traffic: Path and Query parameter values are automatically saved in the Conditional Match configuration for each recorded request/response pair without overwriting existing entries. This mirrors the Path and Query parameter support introduced in ReadyAPI 3.66.0 for Import from file. For more information, see Query and path parameters in recorded traffic on the How to Use Conditional Match page.
General Updates
- Library Updates: ReadyAPI 4.1.0 uses newer versions of several libraries than 4.0.1. If your scripts reference any classes from the libraries updated in ReadyAPI 4.1.0, review and update them as needed.
- Apache HttpClient 5 support for load and performance tests (Experimental): Load and performance tests now support Apache HttpClient 5 as an optional upgrade for high-load scenarios. This client improves virtual thread compatibility and uses cached configuration to reduce virtual user (VU) thread contention. Apache HttpClient 4 remains the default.
To enable HttpClient 5, set the useLegacyHttpClientInLoadTests VM option to false. For instructions on setting VM options, see Modifying JVM Settings.
Note
HttpClient 5 delivers the best results with REST and HTTP Test Request steps. SOAP, XML-RPC, and DataSource steps continue to use the existing configuration behavior.
See Bug Fixes in ReadyAPI 4.1.0 for the complete list of fixes included in this release.