Raynet Connector

Overview

This connector integrates with Raynet to retrieve device inventory and operating system data for synchronizing Configuration Items into the Xurrent CMDB.

Prerequisites

To use this connector, you need:

• A Raynet tenant (e.g. your-tenant.raynetone.com)
• A Raynet API key with read access to the Devices and OperatingSystems endpoints

Authentication

Header-based. Each outbound request carries an ApiKey header populated from the connection's API key field. No OAuth flow is involved. Provide the Instance (e.g. your-tenant) so the connector can compose the base URL https://<instance>.raynetone.com/api/v1.

Triggers

None — this connector is outbound only.

Actions

Fetch devices

Retrieves devices from GET /api/v1/Devices/by-inventory with optional incremental-sync filter. Paginates internally using Raynet's lastId cursor — one page is emitted per iteration, and the action drains the full result set across successive iterations.

Use case: populate or refresh the device inventory in Xurrent's CMDB. Pass inventory_date_later_then (ISO 8601) to fetch only devices whose inventory was updated at or after a specific time for incremental sync; omit it for a full sync.

Input Parameters

Example Input

{
  "inventory_date_later_then": "2026-05-14T00:00:00Z",
  "count": 100
}

Output

Device fields

Example Output

{
  "has_next_page": true,
  "devices": [
    {
      "id": "019aee57-6d0f-7eef-9ca9-504d44b78630",
      "name": "srv_4cb1f",
      "creation_date": "2025-12-05T11:48:18.319Z",
      "model": "VMware Virtual Platform",
      "manufacturer": "VMware, Inc.",
      "number_of_logical_processors": 6,
      "number_of_processors": 6,
      "total_physical_memory": 17179869184,
      "physical_memory": 17179869184,
      "uuid": "2c983a42-2b40-4890-22b0-7fc24b314822",
      "detected_os_type": "Windows",
      "last_sucessful_inventory_run": "2025-12-04T00:02:17.639Z",
      "is_virtual": false,
      "source": "MECM,ActiveDirectory"
    }
  ]
}

Error Handling

Best Practices

• Pass inventory_date_later_then set to the start of the previous successful run for incremental sync — do not derive the watermark from per-device last_sucessful_inventory_run.
• Keep count at its documented maximum (1000) to minimize round-trips on large tenants.
• Let the action drain its internal pagination across iterations rather than slicing pages manually.

Fetch operating systems by device IDs

Retrieves operating system records in bulk for a batch of device IDs from POST /api/v1/OperatingSystems/ByManyDeviceIds. The action paginates internally — it emits one page per batch and drains the full device_ids list across successive iterations.

Use case: enrich device records with detailed OS information (caption, edition, version, architecture, install date) for CMDB synchronization. Feed device_ids from the output of Fetch devices.

Input Parameters

Example Input

{
  "device_ids": [
    "019aee57-6d0f-7eef-9ca9-504d44b78630",
    "019aee57-4e37-7857-bcea-77aa4dc83e8e"
  ],
  "count": 100
}

Output

OperatingSystem fields

Example Output

{
  "has_next_page": false,
  "operating_systems": [
    {
      "id": "019aee70-db5d-78a7-a392-9bcf2814a923",
      "device_id": "019aee57-6d0f-7eef-9ca9-504d44b78630",
      "name": "Windows Server 2016",
      "caption": "Windows Server 2016",
      "manufacturer": "Microsoft Corporation",
      "architecture": "64-bit",
      "edition": "Standard",
      "os_language": "1033",
      "version": "10.0.14393",
      "type": "Windows",
      "system_directory": "C:\\WINDOWS\\system32",
      "serial_number": "XXXXX-XXXXX-XXXXX-XXXXX"
    }
  ]
}

Error Handling

Best Practices

• count defaults to 100 and can go up to 1000 — set it near the max to minimize round-trips on large device lists.
• Feed device_ids from Fetch devices rather than maintaining a separate list.

Rate Limiting

Best Practices

• Run Fetch devices before Fetch operating systems by device IDs — the latter consumes the id field from the former.
• Use inventory_date_later_then for incremental syncs after the first full sync to keep page counts small.
• Treat last_sucessful_inventory_run as a per-device value, not a global high-watermark — persist the run's start timestamp for the next inventory_date_later_then value.
• Stub devices (devices with no model / manufacturer / uuid) are returned alongside fully-populated devices — the connector returns them as-is so the runbook can filter them out.

Common Use Cases

• Initial CMDB import → Fetch devices (without inventory_date_later_then) → Fetch operating systems by device IDs for all returned device ids.
• Incremental sync → Fetch devices with inventory_date_later_then set to the previous run's start timestamp → Fetch operating systems by device IDs for the changed subset.
• OS enrichment refresh → Fetch operating systems by device IDs with a known device id list.

References

• Raynet API documentation
• Endpoints used by this connector:
  • GET /api/v1/Devices/by-inventory — Fetch devices (cursor pagination via lastId, incremental filter via inventoryDateLaterThen)
  • POST /api/v1/OperatingSystems/ByManyDeviceIds — Fetch operating systems by device IDs