Hey
ravienu,
Just a follow up to
KarelHusa's good advice.
If you do in fact have special chars (html encodes) in your payload, the Content-Type header needs to be x-www-form-urlencoded (or the multipart-form header) to support processing html encodes in your payload. Html encoding only works on the URI if the Content-Type header is application/json.
Oh yeah, whenever i get problems where stuff works in Postman but not ReadyAPI!, the first thing i do is compare the full RAW content of both requests. Not always, but quite often, the problem is a difference between the headers being submitted between the Postman request and the ReadyAPI! request. You can use a traffic sniffer (like Fiddler) or just manually compare from each app instead.
Cheers,
Rich
