Configure Connection
Incident IQ guide
Arrange Incident IQ API access, configure credentials and identifiers in NIM, and validate user and asset data for your process.
Before you beginDirect link to Before you begin
Follow the existing Incident IQ access and API keys documentation to arrange API access. Work with your Incident IQ administrator to obtain the credentials and identifiers for your environment.
NIM requires Hostname, API Key, Site ID, and User ID.
Obtain credentials and identifiersDirect link to Obtain credentials and identifiers
- Arrange an API key using the vendor's access and API key instructions.
- Obtain the Hostname, Site ID, and User ID to use with the integration from your Incident IQ administrator.
- Confirm access to the user and asset data required by your process, including permission to perform intended user updates.
- Store the API key securely for the NIM connection.
Enter the connection settingsDirect link to Enter the connection settings
- In NIM Studio, open Systems > Overview and add an Incident IQ system, or select the existing system.
- Open Connection, enter the following settings, and save.
| NIM setting | Value |
|---|---|
| Hostname | The Incident IQ host for the intended environment, using the format expected by the Connection screen. |
| API Key | The key supplied for API access. |
| Site ID | The site identifier supplied for the integration. |
| User ID | The user identifier supplied for the integration. |
Test user retrievalDirect link to Test user retrieval
-
Select Test Connection. NIM attempts to retrieve users using:
GET /services/users?$p=0&$s=10 -
If the test fails, verify the Hostname, API Key, Site ID, User ID, network access, and API permissions.
-
Collect the users and assets required by your process, and confirm that the expected records are present.
-
Validate user matching and asset mappings before using the collected data for audit or downstream provisioning.
-
Test intended user updates with safe records before enabling automation.
The connection test checks user retrieval. Validate asset collection and user write permissions separately. The connector currently lists Read and Update for users; configure provisioning actions around those supported operations.