Helper – Connect To Files

This API Fortress Helper utility allows you to access files via an API.
Configuration Deployment
Place the package in a machine that has access to the files that you wish to use, and could be reached by API Fortress as well via HTTP.
In the “docker-compose.yml” file customize the second volume to point to the directory you wish to share. The default is a local directory named “files”.
Access the files using the address:
The default configuration has a demo file called bypopulation.csv, therefore by running the docker-compose.yml file, you should be able to access the file by calling:
As easy as “sudo docker-compose up -d”.

Helper – Connect to Any Database

This API Fortress Helper utility allows you to access databases via an API.

Configuration Deployment :
Place the package in a machine that has access to the databases that you wish to use, and which could be reached by API Fortress via HTTP.  As a default, the system will connect to PostgreSQL, but you can configure it to run against any DB that can be accessed with JDBC.  Of course, this requires a bit more configuration located in apps/db-api-helper/db-api-helper.xml.
Next steps are pretty straight forward.
 Look for the following element: <db:generic-config name=”Generic_Database_Configuration” url=”jdbc:postgresql://;user=apipulse” driverClassName=”org.postgresql.Driver” doc:name=”Generic Database Configuration”>  If you plan to use another database, you will need to download the matching JDBC driver, place it in the apps/db-api-helper/lib directory, and configure the flow accordingly.  In our example, hitting the route like this… curl -H ‘content-type:text/plain’ -d ‘* from auser’ http://<machine_hostname>:8092/db/select  …will trigger a select query that will return the result as a JSON array payload.  INSERT, UPDATE, DELETE routes are also available and they work similarly.  

Running It’s as easy as “sudo docker-compose up -d”.

Single sign-on with SAML 2.0 (beta)

***On-Premises only*** If you are using an on-premises deployment and would like to set up single sign-on (SAML 2,.0) follow the below instructions.

Step 1: Activate it

Whether you’re using a docker-compose or a Kubernetes deployment, introduce the following environment variable: Name: samlEnabled Value: 'true'

Step 2: Configure it

The provided “saml/” file contains all the configuration keys necessary to the SAML functionality. onelogin.saml2.sp.entityid: identifies the SP onelogin.saml2.sp.assertion_consumer_service.url: where the response from idp is returned after an authentication request Onelogin.saml2.sp.single_logout_service.url: where the response from idp is returned after logout request onelogin.saml2.idp.single_sign_on_service.url: where the SP will send the Authentication Request  onelogin.saml2.idp.single_logout_service.url: where the SP will send the logout request onelogin.saml2.idp.x509cert: public x509 certificate of the IdP   Example: onelogin.saml2.sp.entityid = apifortress onelogin.saml2.sp.assertion_consumer_service.url = onelogin.saml2.sp.single_logout_service.url = onelogin.saml2.idp.entityid = Onelogin.saml2.idp.single_sign_on_service.url = onelogin.saml2.idp.single_logout_service.url = onelogin.saml2.idp.x509cert = —–BEGIN CERTIFICATE—–CERTIFICATE HASH—–END CERTIFICATE—– Further changes can be applied to the expected properties: apifortress.firstname=FIRSTNAME apifortress.lastname=LASTNAME apifortress.mail=MAIL #in IDP one of MANAGER,DEVELOPER,ANALYST apifortress.level=LEVEL By altering these configuration keys, you change the name of the property that’s being sent by the IDP. As a default, the required properties are: FIRSTNAME LASTNAME MAIL LEVEL represents the level of the user within API Fortress and can be one of the following values: MANAGER,DEVELOPER,ANALYST If the field is not provided, MANAGER is assumed. The admin status can only be set via the API Fortress configuration panel. Note: there may be other configuration keys to be altered based on the IDP requirements.

Step 3: Mount it

Mount the provided “saml” directory to the location: /usr/local/tomcat/webapps/app/WEB-INF/saml If Kubernetes is being used, ConfigMaps will achieve the same result.

Step 4: Restart API Fortress

Restart the API Fortress dashboard(s). The login screen will now look like this:  

Connectors – StatusPage

**To learn how to import a connector click here** This connector allows you to connect your API Fortress instance with your StatusPage instance. When a test fails the connector will open an incident in StatusPage, the next time that same test runs and passes the connector will resolve the incident in StatusPage. What you will need from your Status page account is the Page ID and the API key, both can be found by logging into your StatusPage account and going to the manage account page. Then click on the tab names “API”: Next we will configure the connector in API Fortress: Don’t forget to add the alert group the project you want the connector to work for:

Build from Axway

You can generate a test draft from an API managed in Axway.
  1. On the test interstitial page there is a “Build from Axway” button, click it
  2. Enter the Username, Password and Base URI for your Axway account (this is your base URI, not including the path eg., please note that the http/s is required)
  3. Then choose the API Project that contains the API you would like to generate a test from
  4. Then for the API you want to generate a test from, click on the lightning bolt on the right side
  5. You now have a high level test created from the API in your Axway account. Run the test as is, or modify it to add more logic!
Click here if you would like to learn what to do from here.

Integrate with Test Modeller (Curiosity Software)

We now have an integration built out with Curiosity Software’s Test Modeller. This integration allows you to power your API Fortress tests with modeled data that was generated in TDM. Below are the steps to integrate TDM with APIF: API Fortress:
  1. Create an API Fortress test that will be used with TDM data.
  2. Generate Webhook for project that will use TDM data:
  1. Test Modeller: 1. Go to Profile -> Connectors 2. Click “Add Connection” 3. Set up the API Fortress connector in Test Modeller 1. Connector Type: choose API Fortress 2. Profile Name: Give the profile a name (recommendation: this should match the API Fortress project name for organizational purposes) 3. Url: This is your API Fortress domain up to the “/app” part (example: 4. Username: This is your API Fortress login username 5. Password: This is your API Fortress login password 6. Project Hook: This is the API Fortress hook that we created earlier in API Fortress. (use the string at the end of the url, for example
4. Save the connector 5. Now that the connector has been configured, go to the “Submit Job” tab 6. Find the API Fortress job and execute it   Now you have your integration between TDM and API Fortress complete, create some models and run tests with multiple input sets easily! To watch a video on this process including how to create model and push data to APIF and run the test click here.

Connectors – PagerDuty

API Fortress + PagerDuty Integration Benefits:

  • Notify on-call responders based on failures in your API Fortress tests.
  • Send critical information on the failure as well as a link to the test report from the failed test.
  • Create high and low urgency incidents based on the severity of the failure via dynamic tags in the test.
Below is a quick guide to setting up and using the PagerDuty connector.

Note: this connector does not come pre-loaded out of the box, and will need to be loaded separately. To learn how to load the connector into your API Fortress instance click here.

This connector is built and supported by API Fortress. If you need any help with this connector please reach out to API Fortress support at

  1. Go to settings page
  2. Click on “Alert Groups”
  3. Create a new group or add a connector to an existing alert group
  4. Add a new connector
  5. Choose the PagerDuty connector
  6. Configure the connector
    1. routing_key is the integration key generated for a service in PagerDuty. The routing_key can be generated as such:
      1. click on the service you would like to alert, and click on the “Integrations tab”
      2. Use an existing integration or create a new one specifically for API Fortress. The integration key provided is the “routing_key”
    2. severity is the level the alert should be sent as. (critical, error, warning, and info)

    3. dedup_key is a key that will allow to you match a triggered alert with a response for that alert

    4. event_action is the action you would like the alert to take. (trigger, acknowledge, and resolve)

  7. Go into project settings for a project you would like PagerDuty alerts set up for
  8. Add the alert group that contains your PagerDuty connector to this project

Add New Connector

Here is a quick guide to load up a new connector into your API Fortress on-premises deployment. You can find all the connectors here:
  1. Go to admin panel
  2. Click on connectors
  3. Add new connector
  4. Follow the file for how to fill in the connector form
  5. Copy and Paste the code from the connector groovy file into the code section

Connectors – JIRA

API Fortress can absolutely integrate with your JIRA setup. However, because not all JIRA boards are created equal, if you would like a connector set up for your specific JIRA board please out to We will then gather the appropriate information and build you a custom connector for your JIRA setup.

Connectors – Hipchat

**To learn how to import a connector click here** Here is a quick guide to setting up a Hipchat integration. First generate your Hipchat personal access token. To do so go to https://[your_company] Then get the room id you would like to send the alerts to, it can be retrieved in the room details page “API ID” Next use these values to set up the connector in API Fortress: Finally, assign the alert group to the project for which you want alerts from: If you are migrating to Slack, we also have a connector for that! Click here to see how to set up that integration.