You're viewing legacy documentation for API Fortress (deployed via an on-premises container). To view documentation for the new SaaS version of API Fortress — now known as Sauce Labs API Testing and Monitoring (with Sauce Connect tunnels) — see API Testing on the Sauce Labs Cloud.
One of the main reason for the existence of Bloodhound is providing a good way to forward API conversations to other agents. This example demonstrates how this happens using the FortressForwarder module that can be found on GitHub.
While you can find an example of how to forward the API conversations to requestbin here and can certainly modify this to forward to many other locations including Elastic, Splunk, and many more. The example below will show you how to configure the side car to forward the calls to the API Fortress Logger.
Once you have downloaded the template on our Github, navigate to the "etc" directory and then to the "flows" directory. We will be modifying the "default.yml" file, there is a sidecar configured for requestbin you can replace that with the configuration below:
Let's walk through what needs to go into the values:
x-secret- can be generated in API Fortress in the "Company Settings -> API KEYS"
docker-compose comes with Bloodhound. In the default settings, Bloodhound will proxy a demo API.
Start the full package by issuing
docker-compose up -d
Access your API Fortress Logger by going to "Tools -> Logger" and click "Update"
Execute the following request:
curl -H 'key:ABC123' 127.0.0.1:8080/demo/retail/product
The output of the proxied API should appear on your screen
Click "Update" on your API Fortress Logger again and notice the forwarded API conversation