Importing an API Job

After you successfully completed Metadata Mapping for API Jobs, you can now import your organization’s SaaS data using the SaaS vendor’s API. The SaaS data needs to be in a .txt file.

API jobs configured using the Advanced Auth Info tab in Enabling the Bearer Token can be imported for copy auth information for a new API job.

Complete the following steps to import an API job in the FSM Data Ingestion Utility.

To import an API Job:

1.

Go to the API Jobs page (API Jobs > API Jobs).

2.

Select the Jobs Scheduled tab.

3.

Click the Import button, which opens the Import API Configuration dialog box.

4.

Click Select File Path to open Windows Explorer.

5.

Select the appropriate .txt file and click Open.

In the Import API Configuration dialog box, the Input File Path field is populated with the file path of the selected .txt file. The API data displays in the text box underneath.

The following import process applies to API jobs configured using the Advanced Auth Info tab in Enabling the Bearer Token. After the API job is imported, it is decrypted and displays the data using the proper JSON format in the Import API Configuration text box. For details, see the following screenshot.

6.

Click Import. The selected .txt file is imported into the FSM Data Ingestion Utility and displays an added row in the Jobs Scheduled tab of the API Jobs page. The Schedule column will not be populated.

7.

For scheduling the newly imported API job, click Edit In the Actions column and go to Adding a New API Job.

Note: If you try to run the imported API job without a schedule, an error message displays: Please update mandatory fields in the job. 

8.

If required, complete the authorization for the newly imported API job. For details, see Configuring the Headers Tab.