--- title: Device42 slug: connectors/device42 docTags: createdAt: 2026-06-09T16:29:42.014Z --- The Device42 connector facilitates seamless integration of Device42's robust IT asset management capabilities with Swimlane's automation platform. Device42 is a comprehensive data center and network management solution that provides IT asset management, IP address tracking, and dependency mapping. The Device42 connector for Swimlane Turbine enables users to automate the retrieval of server relationships, contact details, and server information directly within their security workflows. By integrating with Device42, Swimlane Turbine users can enhance infrastructure visibility, streamline asset management, and ensure that critical asset information is always at their fingertips for informed decision-making and rapid response to security incidents. ### Limitations None to date. ### Supported Versions This connector supports the latest version 1 of the Device42 API. ## Additional Docs - [Device42 API Docs](https://docs.aws.amazon.com/sns/latest/api/welcome.html) - [Device42 Authentication](https://api.device42.com/#API_Authentication) ### Configuration ## Prerequisites To effectively utilize the Device42 connector with Swimlane Turbine, ensure you have the following prerequisites: - HTTP Basic Authentication with these parameters: - URL: The endpoint URL for the Device42 instance. - Username: Your Device42 username with sufficient permissions. - Password: The corresponding password for your Device42 account. - Custom Authentication with these parameters: - URL: The endpoint URL for the Device42 instance. - Client Key: A unique identifier for the client application. - Secret Key: A secret key paired with the client key for authentication. ## Authentication Methods To effectively utilize the Device42 connector with Swimlane Turbine, ensure you have the following prerequisites: ### Custom Authentication: - Custom Authentication with the following parameters: - URL: The endpoint URL for the Device42 instance. - Client Key: he client key for the API. - Secret Key: The secret key for the API. ### HTTP Basic Authentication: - HTTP Basic Authentication with the following parameters: - URL: The endpoint URL for the Device42 instance. - Username: Your Device42 username credential. - Password: Your Device42 password credential. ## Capabilities This Connector provides the following capabilities: - Link Servers to Owners or POCs - Retrieve Contact Details - Retrieve Server Details ### Link Servers to Owners or POCs Retrieve relationships for a specific server, linking it to owners or POCs. Device42's Documentation for this action can be found [here](https://api.device42.com/#api_info). ### Retrieve Contact Details Fetch user contact information. Device42's Documentation for this action can be found \[here][https://api.device42.com/#api\_info](https://api.device42.com/#api_info)). ### Retrieve Server Details Fetch all servers with detailed information. Device42's Documentation for this action can be found [here](https://api.device42.com/#!/Devices/getDevices). # Configurations ## Device42 Custom Authentication Authenticates using Client Key and Secret Key. ### Configuration Parameters | **Parameter** | **Description** | **Type** | **Required** | | ------------- | ---------------------------------- | -------- | ------------ | | url | A URL to the target host. | string | Required | | client\_key | The client key for the API. | string | Required | | secret\_key | The secret key for the API. | string | Required | | verify\_ssl | Verify SSL certificate | boolean | Optional | | http\_proxy | A proxy to route requests through. | string | Optional | ## Device42 HTTP Basic Authentication Authenticates using username and password. ### Configuration Parameters | **Parameter** | **Description** | **Type** | **Required** | | ------------- | ---------------------------------- | -------- | ------------ | | url | A URL to the target host. | string | Required | | username | Username | string | Required | | password | Password | string | Required | | verify\_ssl | Verify SSL certificate | boolean | Optional | | http\_proxy | A proxy to route requests through. | string | Optional | # Actions ## Link Servers to Owners or POCs Retrieve and link server relationships to owners or points of contact in Device42 using the specified device ID. ### Endpoint - **URL:** `/api/1.0/device/relationships/{{device_id}}/` - **Method:** `GET` ### Input | **Argument Name** | **Type** | **Required** | **Description** | | --------------------------- | -------- | ------------ | --------------------------------------------------- | | `path_parameters.device_id` | number | Required | The ID of the device to retrieve relationships for. | ### Input Example `{"path_parameters":{"device_id":1234}}` ### Output | **Parameter** | **Type** | **Description** | | ----------------------------------------- | -------- | ------------------------------------------------------ | | `status_code` | number | HTTP status code of the response | | `reason` | string | Response reason phrase | | `relationships` | array | Output field: relationships | | `relationships.device_id` | number | Unique identifier | | `relationships.relationship_type` | string | Type of the resource | | `relationships.related_person` | object | Output field: relationships.related\_person | | `relationships.related_person.person_id` | number | Unique identifier | | `relationships.related_person.name` | string | Name of the resource | | `relationships.related_person.email` | string | Output field: relationships.related\_person.email | | `relationships.related_person.phone` | string | Output field: relationships.related\_person.phone | | `relationships.related_person.department` | string | Output field: relationships.related\_person.department | ### Output Example `{"status_code":200,"response_headers":{"content-length":"140","content-type":"application/json","Date":"Thu, 2 May 2024 20:37:23 GMT"},"reason":"OK","json_body":{"relationships":[{}]}}` ## Retrieve Contact Details Fetch user contact information from Device42, including names, phone numbers, and email addresses. ### Endpoint - **URL:** `/api/1.0/people/` - **Method:** `GET` ### Output | **Parameter** | **Type** | **Description** | | ------------------- | -------- | -------------------------------- | | `status_code` | number | HTTP status code of the response | | `reason` | string | Response reason phrase | | `people` | array | Output field: people | | `people.person_id` | number | Unique identifier | | `people.name` | string | Name of the resource | | `people.email` | string | Output field: people.email | | `people.phone` | string | Output field: people.phone | | `people.department` | string | Output field: people.department | ### Output Example `{"status_code":200,"response_headers":{"content-length":"140","content-type":"application/json","Date":"Thu, 2 May 2024 20:37:23 GMT"},"reason":"OK","json_body":{"people":[{}]}}` ## Retrieve Server Details Fetch detailed information for all servers within Device42, including hardware specs, installed software, and network data. ### Endpoint - **URL:** `/api/1.0/devices/` - **Method:** `GET` ### Input | **Argument Name** | **Type** | **Required** | **Description** | | ----------------- | -------- | ------------ | -------------------------------- | | `parameters.type` | string | Optional | The type of device to filter by. | ### Input Example `{"parameters":{"type":"server"}}` ### Output | **Parameter** | **Type** | **Description** | | ------------------------------------- | -------- | --------------------------------------------------- | | `status_code` | number | HTTP status code of the response | | `reason` | string | Response reason phrase | | `devices` | array | Output field: devices | | `devices.device_id` | number | Unique identifier | | `devices.name` | string | Name of the resource | | `devices.type` | string | Type of the resource | | `devices.asset_no` | string | Output field: devices.asset\_no | | `devices.serial_no` | string | Output field: devices.serial\_no | | `devices.primary_ip` | string | Output field: devices.primary\_ip | | `devices.os` | string | Output field: devices.os | | `devices.cpucount` | number | Count value | | `devices.ram` | string | Output field: devices.ram | | `devices.storage` | string | Output field: devices.storage | | `devices.custom_fields` | object | Output field: devices.custom\_fields | | `devices.custom_fields.rack_location` | string | Output field: devices.custom\_fields.rack\_location | | `devices.custom_fields.department` | string | Output field: devices.custom\_fields.department | ### Output Example `{"status_code":200,"response_headers":{"content-length":"140","content-type":"application/json","Date":"Thu, 2 May 2024 20:37:23 GMT"},"reason":"OK","json_body":{"devices":[{}]}}` # Response Headers | **Header** | **Description** | **Example** | | -------------- | ----------------------------------------------------- | ---------------------------- | | content-length | The length of the response body in bytes | 140 | | content-type | The media type of the resource | application/json | | Date | The date and time at which the message was originated | Thu, 2 May 2024 20:37:23 GMT |