Retrieve computer names and last-reporting dates using the REST API

Products

• IT Management Suite

Issue/Introduction

You need computer names and their last reporting (last modified) dates for computers that reported within the past 30 days, and you were asked whether this is achievable through the REST API alone or requires Altiris Workflow Solution.

Environment

IT Management Suite (ITMS) 8.x

ASDK REST API

Pre-installed report: "Computer last information update time" (GUID b30198eb-4fa5-47e1-a334-aac2ed79161d)

Resolution

The ASDK REST API alone returns computer names and last-reporting (last modified) dates for computers filtered by a time window — Altiris Workflow Solution and Data Connector are not required.

ITMS exposes REST functionality through two distinct mechanisms. The ASDK REST API is a set of built-in endpoints, browsable through Swagger, that call existing platform operations directly, including running an existing report and returning its results as JSON. Data Connector (REST Schema) is a separate XML schema framework for pulling from or pushing to external third-party REST APIs, converting their JSON responses into internal Data Tables for use in Rule items. This article uses the ASDK REST API, because the request only needs data ITMS already has — computer names and last-reporting dates from a built-in report.

NOTE:
The following instructions and code samples are provided strictly as examples. Technical Support and Engineering do not provide guidance or custom troubleshooting for implementing API requests.

A note on which REST mechanism this uses

ITMS exposes REST functionality through two distinct mechanisms:

• ASDK REST API — a set of built-in endpoints (browsable through Swagger) that let you call existing platform operations directly, including running an existing report and getting its results back as JSON. This is the mechanism used below.

• Data Connector (REST Schema) — an XML schema framework used to define custom "pull" or "push" integrations with external third-party REST APIs, converting their JSON responses into internal Data Tables (or vice versa) for use in Rule items. This is a separate, more involved configuration intended for connecting ITMS to outside systems, not for querying ITMS's own report data. See Data Connector's REST Schema documentation

Because this request only needs data ITMS already has (computer names and last-reporting dates from a built-in report), the direct ASDK call below is the simpler path. The Data Connector/REST Schema framework isn't needed here.

STEPS

1. Confirm the source report in the console. Navigate to:
   Reports > Notification Server Management > Agent > Computer last information update time
   
   
   This report returns Name, Description, OS Name, and Primary DNS Suffix for computers filtered by a "Hours since last modified" parameter.
   
   
2. Note the report's GUID. This report is pre-installed with ITMS and its GUID is:
   b30198eb-4fa5-47e1-a334-aac2ed79161d
   
   
3. Open the ASDK REST API endpoint for running a report.
   
   /api/v1/ns/ReportManagement/reports/{report_id}/run
   
   This endpoint is browsable through Swagger at:
   
   https://<SMP_FQDN>/Altiris/ASDK.REST/swagger/ui/index#!/ReportManagement/ReportManagement_RunReport
   
   
   
4. Set the name_value_pairs query parameter.
   This report accepts a parameter named Last_Modified_At_Least_N_Hours, expressed in hours. For a 30-day window, use 720 hours (30 × 24).
   
5. Call the endpoint.
   
   CURL code:
   

   curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' 'https://ns_machine/Altiris/ASDK.REST/api/v1/ns/ReportManagement/reports/b30198eb-4fa5-47e1-a334-aac2ed79161d/run?name_value_pairs=Last_Modified_At_Least_N_Hours%3D720'

   
   Replace ns_machine with the target SMP Server's hostname.
   
   
6. Read the JSON response.
   Each result row includes the computer name and its last-modified date:
   
   [
{
"Name": "test-main-dev4",
"Description": "My Secondary PC",
"OS Name": "Windows 10 Pro (22H2)",
"Primary DNS Suffix": "lab.est.example.net",
"Date Created": "2026-08-18T08:11:16.577",
"Date Modified": "2026-08-18T09:00:33.39",
"Hours Since Last Modified": 2
},
{
"Name": "test-main-vm23",
"Description": "",
"OS Name": "Windows Server 2022 Standard (21H2)",
"Primary DNS Suffix": "lab.est.example.net",
"Date Created": "2026-08-18T11:17:26.583",
"Date Modified": "2026-08-18T11:18:05.08",
"Hours Since Last Modified": 0
}
]
   
   Note:
   Name gives the computer name.
   Date Modified gives the last reporting date.
   Hours Since Last Modified confirms the row falls inside the requested window.
   

Creating a custom report for different data

If the pre-installed report doesn't return the exact fields needed, build a new report in the console (for example, using "Save As" from an existing report, or a new SQL/dynamic report), then run it through the same /ReportManagement/reports/{report_id}/run endpoint using its own GUID.

Authentication and access requirements

Per the ITMS ASDK REST Tutorial documentation:

• The calling account must belong to a role with the Use ASDK privilege.
• The account also needs read access to the CMDB items and resource model involved in the request — for report execution, this means read access to the report item and its underlying data source.
• ASDK REST calls support either Windows Integrated Authentication or, starting in ITMS 8.8, an NS access token passed as an Authorization: Bearer header.
  

Verification

Run the call in Step 5 and confirm:

• The returned computer names match what's expected to have reported in the last 30 days.
• Hours Since Last Modified values are all ≤ 720.
• Row count is consistent with the count shown for the same filter in the console report.

Related information

For integrations that need to pull data from, or push data to, an external third-party REST API (rather than querying ITMS's own reports), see See Data Connector's REST Schema documentation
That framework uses XML schema definitions with <api>, <column>, <request> and <transform> elements to convert JSON to and from internal Data Tables, and is a separate configuration path from the direct ASDK call described in this article.

Additional Information

Data Connector's REST Schema documentation