The setup is very straightforward. The UI is good for looking up active mappings, but I prefer writing them as JSON mapping definitions and loading them that way. I also like using .hbs files so the code stays better organised.
Responses are quick, even with a lot of test data. We had no issues integrating it into our current setup. Routes simply point to the Traffic Parrot endpoint and it just works.
I even wrote an extension, which was easy once you know what you’re doing. Review collected by and hosted on G2.com.
When I write the mapping definitions by hand, I struggle to find clear documentation on what I can actually do there. As soon as I go off the beaten path, it turns into a lot of trial and error. Review collected by and hosted on G2.com.
