ReadyAPI: спампаваць старыя версіі

Available now: ReadyAPI MCP Server
ReadyAPI MCP Plugin 1.1.0 is now available. From ReadyAPI 4.1.0 onwards, you can now build human and agentic workflows through MCP tools, keeping you in control of your data and workspace. MCP support is opt-in and becomes active only after you install the ReadyAPI MCP Plugin. See MCP Integration to learn more.
Once installed, you can 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.3.0 introduces the following enhancements and updates. See Version History for changes in previous releases.
AsyncAPI Enhancements
- AsyncAPI 3.0 support: ReadyAPI now supports AsyncAPI 3.0 imports alongside existing 2.x definitions. Key changes include:
- Operation names from your definitions now appear in the Navigator exactly as defined - for both 2.x and 3.0.
- In AsyncAPI 3.0, publish/subscribe is replaced with send/receive.
- The Endpoints tab has been renamed to Servers.
- A read-only Specification tab and version badges are now available.
For more information, see AsyncAPI Support.
Virtualization Enhancements
- Support for Send as Text mode in REST attachments: The Attachments table for multipart/form-data requests now includes a Send as column, letting you choose whether each part is sent as a file attachment or as plain form-data text. Existing requests default to File. For more information, see the REST Attachments section.
- New script object for Virtual Service responses: The Groovy script context for Virtual Services now includes mockResponseLite, a high-performance alternative to mockResponse for high-concurrency scenarios. It is available only in the Edit Response script context. For more information, see Virtual Service Scripting and Virtual Service Script Editors.
Load Testing Improvements
- Improved Load Test Controller behavior: The Load Test Controller now handles high-concurrency scenarios more reliably by separating socket listening from message processing.
- New VM option for LoadUIAgent socket buffer configuration: If SmartBear Support advises you to tune TCP socket performance, you can now configure the receive and send buffer sizes for LoadUIAgent and ReadyAPI TCP sockets using a new JVM option: -Dloadui.agent.socket.buffer.size=<value in bytes>. For more information, see Load Test Agent.
- Compatibility notice for LoadUIAgent 4.3.0: LoadUIAgent 4.3.0 is not compatible with ReadyAPI versions earlier than 4.3.0, and ReadyAPI 4.3.0 is not compatible with LoadUIAgent versions earlier than 4.3.0. Upgrade both components together to maintain compatibility.
Integrations
- New Model Context Protocol sample project: A new Model Context Protocol (MCP) sample project is now available on the Dashboard. For more information, see MCP Integration.
General Updates
- Updated Groovy script compilation: Groovy script compilation is now faster, reducing project startup time.
- Library Updates: ReadyAPI 4.3.0 uses newer versions of several libraries than 4.2.0. If your scripts reference any classes from the Libraries Updated in 4.3.0, review and update them as needed.
Notice
Deprecated plugins: The following plugins are deprecated in ReadyAPI 4.3.0 and will be removed in version 4.4.0: API Blueprint, Axway API Manage

Available now: ReadyAPI MCP Server
ReadyAPI MCP Plugin 1.0.0 is now available. From ReadyAPI 4.1.0 onwards, you can now build human and agentic workflows through MCP tools, keeping you in control of your data and workspace. MCP support is opt-in and becomes active only after you install the ReadyAPI MCP Plugin. See MCP Integration to learn more.
Once installed, you can 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.
Coming soon: Version 1.1.0 of the ReadyAPI MCP Plugin is due to release later in August 2026.
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.2.0 includes the following updates. See Version History for changes in previous releases.
Before you upgrade
- H2 database migration: ReadyAPI 4.2.0 removes the H2 migrator. If you are upgrading from a version earlier than 3.51.0, complete the H2 database migration before upgrading to 4.2.0 by first upgrading to any version between 3.51.0 and 4.1.0. For more information, see H2 Migration.
AI Enhancements
- AI Test Generation plugin now uses Gemini 3: The AI Test Generation plugin no longer supports Gemini 2.5 as the performance model. Gemini 3 replaces it as the default.
- ReadyAPI MCP plugin update notifications: ReadyAPI now notifies you when a newer version of the MCP plugin is available, so you can keep your plugin up to date.
UI Enhancements
- Functional Test UI updates: The Coverage and History sections now share a consistent look and feel with the rest of ReadyAPI, making it easier to navigate between views.
- Security UI updates: The Security module, Security Tests creator, and Auth Manager now share a consistent look and feel with the rest of ReadyAPI, making security configuration easier to navigate.
- Virtualization UI updates: The JDBC Request dialog and Conditional Match configuration dialog now share a consistent look and feel with the rest of ReadyAPI, making virtualization setup easier to navigate. For more information, see JDBC Request, Conditional Match Overview, and How to Use Conditional Match.
Security Enhancements
- New VM option to enforce Auth Repository encryption: IT administrators can now add -AuthProfileEncrypt=true to the ReadyAPI deployment package to ensure the Auth Repository is encrypted by default for all users, preventing OAuth tokens and credentials from being exposed in project files. For more information, see Auth Repository.
Integrations
- Improved Zephyr Squad integration: Selecting a cycle in the Map to Zephyr dialog now filters the test case list to show only test cases for that cycle, making it easier to map the right test cases to the correct cycle. For more information, see 2. Map a ReadyAPI project to Zephyr Squad.
Performance Enhancements
- Improved TPS performance in Load Tests: ReadyAPI now handles thread contention more efficiently during Load Test execution, resulting in higher transactions per second (TPS).
- Improved Load Test step performance: ReadyAPI now caches settings for the most commonly used Load Test steps, reducing overhead and improving overall Load Test performance.
General Updates
- Reduced logging in Conditional Match: ReadyAPI now uses reduced logging frequency in Conditional Match, improving dispatching performance and throughput in the Virtualization module.
- Re

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 performan

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.0.1 is a patch release that resolves several UI and usability issues reported after the ReadyAPI 4.0.0 release.
Bug fixes
- Fixed an issue in the SOAP panel where the Assertions tab did not open correctly, and users could not expand or resize the split pane between the request and response editors.
- Fixed an issue where users could not edit endpoints directly in the endpoint cell, and the Edit Endpoint dialog did not display the selected endpoint correctly.
- Fixed an issue where users could not switch UI modes when working with encrypted projects because the setting change did not apply correctly.
- Fixed an issue where users could not rename APIs after creating them in a test project.
Library Updates: ReadyAPI 4.0.1 introduces no library changes that affect scripting compatibility.

UI Update Notice
ReadyAPI 4.0.0 introduces 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.0.0 introduces a refreshed user interface that modernizes the look and feel of the product while preserving the workflows and capabilities teams rely on for API testing.
This release focuses on visual improvements and consistent design across the product.
Key Updates
- Modernized interface: The ReadyAPI interface now offers a cleaner and more consistent experience across the application.
- Improved readability and layout: Updated panels, navigation elements, and editors improve clarity and make everyday testing workflows easier to use.
- No workflow changes: All existing ReadyAPI functionality remains the same. Your projects, tests, and automation pipelines continue to work as before.
Important Note on Scaling
ReadyAPI works best at a display resolution of 1920 × 1080 with 100% scaling.
If you use a lower resolution or different OS scaling, adjust UI scaling to improve readability and layout.
For resolutions below 1920 × 1080, set the following JVM option in your vmoptions file or startup command:
- Dreadyapi.ui.scaling=X
For more information, see Display scaling in ReadyAPI.
In version 4.1.0, ReadyAPI will include a built-in option to adjust scaling in Preferences.
Documentation Updates
The updated interface requires refreshed documentation screenshots and SmartBear videos, which are being updated gradually.
During the transition period:
- Some screenshots may still show the previous UI.
- Workflows and product functionality remain unchanged.
General Updates
- Library Updates: ReadyAPI 4.0.0 uses newer versions of several libraries compared to 3.67.0. If your scripts reference any classes from the libraries updated in ReadyAPI 4.0.0, review and update them as needed.
- SmartBear AI Test Generation is now generally available: This feature requires an SLM license hosted in manage.smartbear.com. Support for SLM on-premises floating licenses is planned for ReadyAPI 4.1.0 by the end of June.
No bug fixes were reported for ReadyAPI 4.0.0. See Bug Fixes in ReadyAPI 4.0.0 for additional information.

ReadyAPI 3.67.0 includes the following updates, which we are excited to share with you. See Version History for changes in previous releases.
Integration Improvements
- Fixed Zephyr Essential test search in Jira Cloud projects: Resolved an issue where ReadyAPI did not display Test issues from Zephyr Essential-enabled Jira Cloud projects in the UI. Outdated API paths caused the issue and triggered the WARN [RestClient] Failed to get Zephyr tests warning message. ReadyAPI now uses the updated API endpoints that follow Atlassian’s migration guidelines (see the Atlassian developer changelog). This change restores correct test retrieval and display.
Performance Improvements
- Enhanced Performance module efficiency: This update increases transactions per second (TPS) in load tests. Current improvements deliver a 10–20% increase in throughput, depending on use case and test complexity.
Planned enhancements for Q2 include upgrading to HTTP Client v5 and introducing Virtual Threads from Java 21 to further improve load testing throughput.
General Updates
- Library Updates: ReadyAPI 3.67.0 uses newer versions of several libraries compared to 3.66.0. If your scripts reference any classes from the libraries updated in ReadyAPI 3.67.0, review and update them as needed.
- Improved proxy handling in AI plugin HTTP client: The HTTP client in the SmartBear AI plugin now aligns with ReadyAPI proxy handling. This change ensures consistent behavior in environments that use proxy configurations.
This update is delivered through the ReadyAPI SmartBear AI plugin. Reinstall the plugin to apply the update.
- UXM Plugin Update: Updated UXM plugin to version 1.3.3.
See Bug Fixes in ReadyAPI 3.67.0 for the complete list of fixes included in this release.

Important Notice for ReadyAPI Customers
Starting from ReadyAPI 3.62.0, VirtServer 3.29.0, and TestEngine 1.34.0, SmartBear has deprecated file-based licenses in favor of the ID-based SmartBear License Management (SLM) system. As of October 1, 2025, file-based licenses are no longer issued, activated/deactivated, or supported; all new and updated licenses are managed through SLM. For further information and timelines, refer to the File-Based License End-of-Life Policy page.
Join the ReadyAPI UX Beta Feedback Program
SmartBear invites ReadyAPI users and stakeholders to take part in the ReadyAPI UX Beta Feedback Program. Share your feedback on the UI refresh and new SmartBear AI-powered features in ReadyAPI.
To learn more or join a feedback session with our team, select Book a ReadyAPI UX Beta Feedback Session.
ReadyAPI 3.66.0 includes the following updates, which we are excited to share with you. See Version History for changes in previous releases.
SmartBear AI Updates
- SmartBear AI is now available as a ReadyAPI plugin: This change allows us to release AI updates independently of the main ReadyAPI release cycle, so you receive improvements more frequently.
The functionality remains the same. After upgrading, install and manage SmartBear AI through the Plugin Manager.
- Improved naming for SmartBear AI-generated tests: When you generate tests using AI, ReadyAPI now automatically assigns meaningful names to Test Suites, Test Cases, and Test Steps. Each name reflects the objective defined in your prompt, making generated tests easier to understand and maintain.
API Request Handling Improvements
- Enhanced Content-Type handling for multipart/form-data: The multipart/form-data media type allows you to send multiple data types in a single request, such as files, images, JSON, and text.
Previously, ReadyAPI:
- Set the correct Content-Type for file and image attachments.
- Defaulted other parameter types to text/plain.
Now, when you define a parameter as a query parameter, you can explicitly set its Content-Type. This gives you greater control over multipart request configuration.
Conditional Match and Virtual Service Enhancements
- Improved support for importing query parameters and path variables in Conditional Match: ReadyAPI now allows you to import request/response file pairs that include query parameters and dynamic path variables. These parameters are recognized during import and can be used in Conditional Match rules, similarly to body parameters.
For more details, see Query Parameter Support in Conditional Match Overview and Importing query and path parameters in How to Use Conditional Match.
- Optimized Conditional Match logging: ReadyAPI reduces disk usage when running large Virtual Services by improving the Conditional Match logging mechanism. This update helps maintain performance during high-volume execution. For more details about Conditional Match logging and enabling Debug mode, see the Conditional Match Overview and How to Use Conditional Match.
Kafka Improvements
- Property expansion support for Schema Registry URL: Property expansion now works in the Schema Registry URL field.
- Get Data option for Kafka: The Kafka context menu now includes a Get Data option that automatically generates property expansion syntax, simplifying configuration and reducing manual errors.
General Updates
- New VM option for LoadTest time barrier: ReadyAPI now provides the VM option -DloadTestDisableTimeBarrier to control the LoadTest time barrier. Set -DloadTestDisableTimeBarrier=true to disable the time barrier. Use this option to remediate cases where the remote LoadUI agents on a VM have system clocks that are out of synch with the ReadyAPI controller instance. Default value: false. For more details about configuring JVM parameters in ReadyAPI, see Java Virtual Machine Parameters.
- Library Updates: ReadyAPI 3.66.0 uses newer versions of several libraries than 3.65.0 did. If your scripts refer to classes from Libraries Updated in Rea

Important Notice for ReadyAPI Customers
Starting from ReadyAPI 3.62.0, VirtServer 3.29.0, and TestEngine 1.34.0, SmartBear has deprecated file-based licenses in favor of the ID-based SmartBear License Management (SLM) system. As of October 1, 2025, file-based licenses are no longer issued, activated/deactivated, or supported; all new and updated licenses are managed through SLM. For further information and timelines, refer to the File-Based License End-of-Life Policy page.
Join the ReadyAPI UX Beta Feedback Program
SmartBear invites ReadyAPI users and stakeholders to take part in the ReadyAPI UX Beta Feedback Program. Share your feedback on the UI refresh and new SmartBear AI-powered features in ReadyAPI.
To learn more or join a feedback session with our team, select Book a ReadyAPI UX Beta Feedback Session.
Webinar: How to Build Automation-Ready API Tests with ReadyAPI
As API automation scales, complexity increases. Join this 30-minute technical session on February 19 to learn how to build scalable, reusable API tests in ReadyAPI and shorten testing cycles from days to hours in CI/CD. Register Now!
ReadyAPI 3.65.0 includes a few changes that we are excited to share with you. See Version History for changes in previous releases.
Authentication and Security Enhancements
- Custom parameters for OAuth2 requests: ReadyAPI now supports adding custom parameters to a standard OAuth2 request body. You can enable an option to include additional key–value pairs, which ReadyAPI appends to the request body. For details, see 2. Configure Authorization.
Property Expansion and Data Handling
- Advanced type casting for Property Expansion: ReadyAPI now stores the value type as part of Property Expansion when it creates magic strings, based on the response value. During request execution, ReadyAPI attempts to cast the request value to the stored type. If casting fails, ReadyAPI sends the value without casting and logs a detailed error message. A new preference, Advanced type casting for Property Expansion, lets you enable or disable this behavior. For details, see Enabling Conditional Match Property Expansion and Example: Adding a type to a property expansion. This capability is supported in VirtServer 3.31.0. For recommended ReadyAPI and VirtServer version pairings, see the ReadyAPI-VirtServer Compatibility Matrix.
SmartBear AI and Licensing Updates
- Improved error handling when SmartBear AI is disabled in SLM: ReadyAPI has improved error handling when SmartBear AI is disabled for ReadyAPI in SLM. When SmartBear AI is disabled in SLM, ReadyAPI now disables it in the application.
- Removed SmartBear AI button for offline licenses: SmartBear AI is not available for SLM Offline and SLM On-Prem licenses at this time. ReadyAPI now removes the Open SmartBear AI button from GUI when SLM Offline and SLM On-Prem licenses are installed to prevent confusion for offline users.
General Updates
- Updated tutorial links: ReadyAPI updates tutorial links to improve accuracy and ensure alignment with current product capabilities.
- Library Updates: ReadyAPI 3.65.0 includes newer versions of some libraries that version 3.64.0 used. If your scripts refer to classes from Libraries Updated in ReadyAPI 3.65.0, you may need to update the scripts.
See Bug Fixes in ReadyAPI 3.65.0 for the list of fixes included in this patch.

Important Notice for ReadyAPI Customers
Starting from ReadyAPI 3.62.0, VirtServer 3.29.0, and TestEngine 1.34.0, SmartBear Product Family has fully deprecated file-based licenses and transitioned to the ID-based SmartBear License Management (SLM) system. Any customers still using file-based licenses must complete their migration to SLM by September 30, 2025.
From October 1, 2025, existing and activated file-based licenses will continue to work for some time. However, SmartBear will no longer generate new file-based licenses or support activation and deactivation of file-based licenses in ReadyAPI, VirtServer, or TestEngine. All new and updated licenses are now issued in SLM only.
All technical support for file-based licenses has now ceased, and SmartBear no longer maintains the file-based licensing system. Any access or service issues will result in service disruptions that we will not be able to restore.
If you have not completed the process of migrating, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, log a request with our SmartBear Support, who are standing by to help.
For further information and timelines, refer to the File-Based License End-of-Life Policy page.
Join the ReadyAPI UX Beta Feedback Program
SmartBear invites ReadyAPI users and stakeholders to take part in the ReadyAPI UX Beta Feedback Program. Share your feedback on the UI refresh and new SmartBear AI-powered features in ReadyAPI.
To learn more or join a feedback session with our team, select Book a ReadyAPI UX Beta Feedback Session.
ReadyAPI 3.64.0 includes a few changes that we are excited to share with you. See Version History for changes in previous releases.
SmartBear AI-Assisted Test Generation [Beta]
- SmartBear AI-Assisted Generation of Assertion-Complete Test Cases: Added support for generating rich, assertion-complete test cases directly from an API definition (for example, OAS 3.0) using natural-language queries powered by large language models. For details on using this capability, see Generate Tests with SmartBear AI [Beta] and SmartBear AI in ReadyAPI.
Connectivity and Integration Enhancements
- Enhanced Swagger Studio Integration for API Version Awareness: ReadyAPI now checks Swagger Studio for API version updates when your project includes tests linked to Swagger Studio definitions. The Notification Center displays alerts when a newer API version is available, allowing you to import the updated definition and refactor tests efficiently. For details, see Notifications for Updated API Versions and Notifications for Updated API Versions.
Security Enhancements
- Stronger Governance for Weak Cipher Usage: ReadyAPI now includes a setting that blocks weak ciphers to enforce stronger security governance. Client endpoints that rely on weak ciphers cannot connect when this setting is active. ReadyAPI also disallows several weak ciphers by default. For details, see System Requirements and Java Virtual Machine Parameters.
Migration and Compatibility
- Defined an Upgrade Path for Older Versions: Users upgrading from versions earlier than 3.51.0 must first upgrade to 3.63.0 before moving to the latest release. Because previous updates (including the removal of file-based licensing) already required upgrades to later versions, this change affects only a small set of users. Contact SmartBear Support if you need assistance.
- Support for Adoptium JDK 21.0.9+10: ReadyAPI 3.64.0 now supports Adoptium JDK 21.0.9+10, ensuring compatibility with the latest Java runtime improvements and security updates. VirtServer and TestEngine adopt Java 21 in their Q1 releases.
General Updates
- Library Updates: ReadyAPI 3.64.0 includes newer versions of some libraries that version 3.63.0 used. If your scripts refer to classes from Libraries Updated in ReadyAPI 3.64.0, you may need to update the scripts.
See Bug Fixes in ReadyAPI 3.64.0 for the list of fixes included in this

Important Notice for ReadyAPI Customers
Starting from ReadyAPI 3.62.0, VirtServer 3.29.0, and TestEngine1.34.0, SmartBear Product Family has fully deprecated file-based licenses and transitioned to the ID-based SmartBear License Management (SLM) system. Any customers still using file-based licenses must complete their migration to SLM by September 30, 2025.
From October 1, 2025, existing and activated file-based licenses will continue to work for some time. However, SmartBear will no longer generate new file-based licenses or support activation and deactivation of file-based licenses in ReadyAPI, VirtServer, or TestEngine. All new and updated licenses are now issued in SLM only.
All technical support for file-based licenses has now ceased, and SmartBear no longer maintains the file-based licensing system. Any access or service issues will result in service disruptions that we will not be able to restore.
If you have not completed the process of migrating, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, log a request with our Customer Care Team, who are standing by to help.
For further information and timelines, refer to the File-Based License End-of-Life Policy page.
Upcoming Customer Spotlight Webinar - Sept 25
Drowning in API testing backlogs? See how Automated Financial Systems cut API testing bottlenecks by empowering business users. Register today to learn their proven approach!
ReadyAPI 3.62.0 includes a few changes which we’re excited to share with you. See Version History for changes in previous releases.
Licensing and Authentication Enhancements
- File-Based Licensing Support Removed: In line with the End-of-Life policy for file-based licensing, support for Protection LS and file-based license types has been removed. The licensing code has been refactored to support only SLM licenses. For details about how this change affects multiple licensing topics, see Important Notice for ReadyAPI Customers.
- SLM Offline Fingerprint: Enhanced the SLM offline license detach process. The checksum generated during uninstall now appears in the GUI and is stored in the ReadyAPI folder on the local machine, preventing loss if not immediately sent to your license administrator. For more information, see Free Offline Fixed-User License.
- Username/Password Credentials in Automated Runs No Longer Supported in SLM On-Premise: The combination of username/password works only on On-Prem servers with version 1.3.1 or earlier. SLM On-Prem servers with versions 2.0 or later do not support this combination. As part of our licensing cleanup, this set of credentials is no longer supported starting in ReadyAPI 3.62.0. Use access key, accessforeveryone, or client credentials (if OIDC is enabled) instead. For more details, see Connecting to the SmartBear Hosted License Server (Online).
User Interface Enhancements
- Consistent Design for Add Test Step: Standardized the look and feel of the Add Test Step user experience as part of the ongoing ReadyAPI UI restyle project, scheduled for release later in 2025 and early 2026. For more information, see Add Test Step.
- Accessibility Improvements: Introduced several accessibility improvements as part of an ongoing effort to comply with Web Content Accessibility Guidelines (WCAG).
Upcoming Updates
- TrustManager Enhancements (Coming in 3.63.0 and 3.64.0): ReadyAPI will add more granular TrustManager controls, requiring users to whitelist trusted certificates and providing a new UI to manage certificates safely in sandbox environments. For a full list of upcoming features and improvements, see Upcoming Updates.
General Updates
- Load Test Results: Updated the Load Test Graph and Table in the GUI. The test engine updates the chart and table approximately every second. The change converts TPS to an average for test steps and test cases once the test has ended, instead of a live per-second reading. The Graph a

Important Notice for ReadyAPI Customers
ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We are now moving into the final phase of the deprecation of file-based licenses. Customers still using file-based licensing must plan for migration to SLM before September 30, 2025.
If you are in the process of migrating or have not started yet, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, log a request with our Customer Care Team, who are standing by to help.
For further information and timelines, refer to the File-Based License End-of-Life Policy page.
ReadyAPI 3.61.0 includes a few changes which we’re excited to share with you. For information on the changes made to other versions, see Version History.
Conditional Match Enhancements
- Added new route option for Conditional Match: The virtual service now includes a Route and Record for the Conditional Match route option. This option routes all incoming requests and automatically creates virtual operations for requests without existing operations. It records both request and response data and creates the matching Conditional Match and Signature. For more details, see Route and Record for Conditional Match.
- Enabled Data Type Specification in Conditional Match: You can now specify data types in the Conditional Match Editor. This improvement helps resolve parsing and validation issues for tests that use strict typing. For more information, see Parameter Value Types in Conditional Match Editor.
OpenAPI 3.1 Enhancements
- Added Callback Support: You can now define callbacks under REST methods. Each callback is read-only, inherits its endpoint from the parent resource, and stays in sync with request parameters. Callbacks help you document and structure asynchronous behavior, such as webhook-style responses. For details, see Working with Callbacks.
- Support for MutualTLS Authentication: ReadyAPI now handles mutualTLS auth during OpenAPI 3.1 import and export. On import, it alerts you to configure SSL client certificates. On export, it adds mutualTLS schemes based on configured SSL keystores, generating separate schemes for multiple keystores.
- Support for Reusable Path Item Objects: ReadyAPI now supports Reusable Path Item Objects in OpenAPI 3.1. It correctly imports path objects defined with $ref, resolving them at the resource, method, and request levels.
- Added apiKey Security Scheme Support: The importer now supports apiKey security schemes, handling authentication automatically and securely during API import.
General Enhancements
- Updated JMS Support to Use Jakarta Namespace: We upgraded ReadyAPI to use the latest jakarta.jms-api library and replaced the related imports. This change extends support to JMS providers that use the jakarta.jms namespace. For details on how this change may affect your tests and what steps to take, see Important Note for JMS Users: Transition to Jakarta JMS API in ReadyAPI.
- Standardized ‘Add Test Step’ UI: To provide a consistent experience, we standardized the user interface for adding test steps across the application.
- Extended mockResult to include Routed Response Data: In Virtual Service scripting, the mockResult object—available in the afterRequest script—now includes response data even when the response comes from a routed endpoint. Previously, mockResult only contained response details if the response came from a mock in the virtual service. This update gives you full access to routed response data, improving visibility and control when you enable routing. See the mockResult object description for more information.
- Library Updates: ReadyAPI 3.61.0 includes newer versions of some libraries that version 3.60.0 used. If your scripts refer to classes from Libraries Updated in ReadyAPI 3.61.0, you might need to update the scripts.
See Bug Fixes in ReadyAPI 3.61.0 for the list of fixes included in this

Important Notice for ReadyAPI Customers
ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We are now moving into the final phase of deprecation of file-based licenses. Customers still using file-based licensing need to plan for migration to SLM before September 30, 2025.
If you are still in the process of migrating or have yet to start, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, please log a request with our Customer Care Team, who are standing by to help.
For further information and timelines, please refer to this page.
Welcome to the New ReadyAPI Documentation Experience
We have updated the ReadyAPI product documentation to provide a more streamlined and consistent user experience across our entire product portfolio. While retaining all essential information, the updated documentation features a fresh design that makes it easier to navigate, read, and utilize.
The new documentation experience offers several key benefits:
- Enhanced panel structure and navigation: A reorganized layout for quicker, more intuitive access to content.
- Improved search capabilities: Find information faster with a more powerful and precise search function.
- Better usability: Simplified viewing and expanding of sections, making it easier to locate and understand relevant details.
ReadyAPI 3.59.0 includes a few changes compared to the previous product version – ReadyAPI 3.58.0. For information on the changes made to other versions, see Version History.
Git and Collaboration Enhancements
- When performing git commit, if the user didn't make all the changes to the project, a notification is displayed saying that it is safe to commit because ReadyAPI modified all the files. This happens in the git commit and diff view panels.
- Added a navigation panel to the git diff preview window. Users can now navigate through the changes made to a file using the Next and Previous buttons.
- Improved the UX of the commit window, which now displays checkboxes to select which files to commit.
- Updated icons in the git commit window.
Other Enhancements
- Updated the mechanism for copying and moving virtual actions to compare conditional match contents when performing an action. Prior to this change, only item names were compared and treated as duplicates.
- You can configure Magic Strings using checkboxes to allow users to manage data types (boolean, empty strings, and numbers).
- Updated the Slack integration to work with the latest Slack API.
- Added the option to save the log created when copying or merging virtual actions to a file on the local machine.
- Updated attachment encoding. This addresses issues with non-standard characters in filenames.
- Users can log into SLM SaaS using a PKCE flow that uses the local system browser (instead of using the native ReadyAPI browser). This provides better support for the user's system and security configurations.
- Basic support for webhooks has been added. Webhook entities are read-only and cannot be edited. This is part of a work program to add OAS 3.1 support in ReadyAPI planned for Q2 2025.
General Enhancements
- Library Updates: ReadyAPI 3.59.0 includes newer versions of some libraries that version 3.58.0 used. If your scripts refer to classes from these libraries, you might need to update the scripts.
Please see here for a list of fixes included in this patch.

Important Notice for ReadyAPI Customers
ReadyAPI has fully transitioned to the ID-based SmartBear License Management (SLM) system. We are now moving into the final phase of deprecation of file-based licenses. Customers still using file-based licensing need to plan for migration to SLM before September 30, 2025.
If you are still in the process of migrating or have yet to start, contact your Account Manager or SmartBear representative today. Our teams are ready to assist with smooth transition strategies. For additional support, please log a request with our Customer Care Team, who are standing by to help.
For further information and timelines, please refer to this page.
Welcome to the New ReadyAPI Documentation Experience
We have updated the ReadyAPI product documentation to provide a more streamlined and consistent user experience across our entire product portfolio. While retaining all essential information, the updated documentation features a fresh design that makes it easier to navigate, read, and utilize.
The new documentation experience offers several key benefits:
- Enhanced panel structure and navigation: A reorganized layout for quicker, more intuitive access to content.
- Improved search capabilities: Find information faster with a more powerful and precise search function.
- Better usability: Simplified viewing and expanding of sections, making it easier to locate and understand relevant details.
ReadyAPI 3.58.0 includes a few changes compared to the previous product version – ReadyAPI 3.57.0. For information on the changes made to other versions, see Version History.
Git and Collaboration Enhancements
- New Force Pull Option for Git Integration: You can now use the Force Pull option in Git integration to override local changes and ensure the latest updates are pulled from the repository. For more information, visit this page.
Conditional Match Enhancements
- Enhanced Conditional Match Performance: The Conditional Match algorithm now processes requests faster, improving throughput for high-demand scenarios.
- Optimized Conditional Match with Improved Hashing: We updated the hashing mechanism within the Conditional Match algorithm to significantly enhance performance during request matching.
- Performance Boost with Optimized Conditional Match Array Management: We introduced the sizeOfConditionalMatchChildArray mechanism, which eliminates the need for a monitor lock, streamlining the performance of Conditional Match operations.
- Faster Signature Sorting with Caching Mechanism: We implemented a caching system to expedite the sorting of signatures within the Conditional Match algorithm, ensuring faster and more efficient processing.
General Enhancements
- Library Updates: ReadyAPI 3.58.0 includes newer versions of some libraries that version 3.57.0 used. If your scripts refer to classes from these libraries, you might need to update the scripts.
Please see here for a list of fixes included in this patch.