Why not using API Recording tools like VRest or JMeter

The Limitation of Recording Tools

Tools that "record" API calls (similar to UI record-and-playback tools) capture a fixed sequence of requests, but tend to produce brittle scripts that break easily when data, authentication tokens, or endpoint responses change.

Why Coded/Scripted Approaches Are Preferred

• Recorded scripts are hard to maintain and adapt to dynamic data (like a fresh session token on every run).
• Recording tools often generate large amounts of unnecessary or duplicate calls.
• Scripted approaches (Rest Assured, Postman scripts) allow proper parameterization, chaining, and assertions tailored to the actual test logic.

Where JMeter Still Fits

JMeter remains a strong choice specifically for performance/load testing of APIs, even though it is not the preferred approach for detailed functional API test automation.