Features Added to ReadyAPI 3.60.0

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.

SmartBear Webinar: Breaking Down Silos – Aligning QA, Development, and DevOps for API Quality

Don’t miss this opportunity to learn more about approaches to modernizing your QA strategy and delivering more reliable APIs faster. Learn more about the webinar and reserve your spot today. Click here to register!

ReadyAPI 3.60.0 includes a few changes compared to the previous product version – ReadyAPI 3.59.0. For information on the changes made to other versions, see Version History.

Postman 3.1.0 Plugin Enhancements

  • Chai Assertions Support: ReadyAPI now supports the Chai library. This feature allows you to import assertions created with Chai in Postman Collections and convert them for use in ReadyAPI. For more details, see the Chai assertions support section.

  • Postman Authorization Profiles Mapping: ReadyAPI now maps Postman authorization profiles to the appropriate ReadyAPI levels. Supported types include Basic, Digest, NTLM, OAuth 1.0, OAuth 2.0, and AWS Signature. For more details, see the Import authorization profiles section.

  • Importing Postman Environments: You can now import Postman environments into ReadyAPI. The system converts variables into project properties, supporting secrets and dynamic variables. For more information, refer to the Import Postman environments section.

Condition Match Enhancements

  • Renaming the "Matches" Operator: We renamed the "Matches" operator to "RegEx" for better clarity in Conditional Match. The updated name is reflected in the Comparison Operators table.

  • Renaming UI Labels for Clarity: We renamed several labels in the Conditional Match dialog to improve alignment with terminology and enhance clarity. Specifically, “Request” is now referred to as “Conditional Match” in various UI elements. For more details on the specific changes, visit the Conditional Match Overview.

  • Relocation of Autoconvert Boolean and Numbers Checkbox: We moved the Autoconvert boolean and numbers checkbox from the Conditional Match section in Virtual Service to the Conditional Match Configuration dialog. This relocation makes the configuration more intuitive and service-specific. Learn more about configuring specific value treatment in Conditional Match.

General Enhancements

  • JDK Update: We updated the JDK to version 17.0.15.

  • Legacy Branding Removal: We removed the legacy branding from the Load Template Page and replaced "SOAPUI" with "ReadyAPI" in the Load Test SOAK Template.

  • Route to Live Process Security Enhancement: We updated the encryption in the Route to Live process for enhanced security.

  • Removal of Legacy Documentation Link: We removed a legacy documentation link to the RAML plugin.

  • Library Updates: ReadyAPI 3.60.0 includes newer versions of some libraries that version 3.59.0 used. If your scripts refer to classes from Libraries Updated in ReadyAPI 3.60.0, you might need to update the scripts.

See Bug Fixes in ReadyAPI 3.60.0 for the list of fixes included in this patch.

See Also

Version History

Publication date: