Recorded Future

introduction this guide tells you how to authenticate the recorded future connector in swimlane using api key authentication you will collect the required api token, identify the correct api endpoint, and configure the connector in swimlane prerequisites recorded future access requirements access to the recorded future platform permission to generate or retrieve a recorded future api token network access to the recorded future connect api required credentials api token api url authentication method api key authentication recorded future uses api key authentication for all api access during setup, you will need api urlapi token recorded future setup take the following steps to generate an api token log in to the recorded future web interface navigate to your user profile and go to api access settings generate a new api token or copy an existing token store the api token securely for use in swimlane connector configuration in swimlane log in to turbine from the left hand navigation pane, click orchestration and click assets asset homepage opens click the plus icon to open the configure your connector asset window select recorded future from the asset type list fill in the asset settings and asset input as shown field description required/optional url recorded future api endpoint url required apikey recorded future api token required verify ssl enable/disable ssl verification optional http proxy optional proxy configuration optional fields with marks are required click create troubleshooting if you encounter authentication issues ensure the api token is valid and active verify the api url is correct for your recorded future tenant confirm the api token has sufficient permissions check network connectivity and proxy configuration you have successfully authenticated the recorded future connector in swimlane