Skip to Main Content
Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Functionality already exists
Workspace SevOne
Created by Guest
Created on Jul 1, 2026

Expand functionality on /api/v3/data/topn endpoint to consider custom timespan like in NMS Web UI

The /api/v3/data/topn endpoint accepts a variety of parameters (aggregation unit, device filters, sorting, etc.), but it does not include a timespan selection. While the API response does include a label attribute (e.g., "Today") and a timeRanges object with start/end timestamps, these appear to be read-only and do not reflect user-defined intervals.

The endpoint should consider a parameter to define a custom time range (e.g., startTime and endTime, or a predefined interval like LAST_7_DAYS), proper handling of the timeZone parameter -or inference from it by the user preferences from the API key used- to ensure accurate reporting for users in different time zones.

This behavior can be evidenced by running a request and noticing the result from a simple query like in the example, will default using UTC 00:00 to ~3:44 in this example:

# /api/v3/data/topn?aggregationUnit=AGGREGATION_AUTO&capacityThreshold.operator=OPERATOR_NONE&devices.ids=25&deviceGroups.ids=542&deviceGroups.membership=MEMBERSHIP_ANY&objectGroups.membership=MEMBERSHIP_ANY&sort=SORT_DESCENDING&templateId=1&units.percentage=PERCENTAGE_ALL&units.preferred=PREFERRED_BYTES

{
  "partialResults": null,
  "rows": [],
  "timeRanges": [
    {
      "specificInterval": {
        "startTime": 1778284800,
        "endTime": 1778298293
      },
      "timeZone": "",
      "label": "Today"
    }
  ]
}
Idea priority High
  • Guest
    Jul 6, 2026

    I would like a working python example, please.

    I would add that when I pasted verbatim the body from the swagger docs and the body from https://developer.ibm.com/apis/catalog/sevonenpm--sevone-api-v8-1-0/api/API--sevonenpm--sevone-api#Data_TopN2 I get the same error:

    400
    {
    "error": "invalid TopNRequest.TemplateSelector: value is required"
    }


    This is essentially without altering ANY of the parameters. Even when I add strings / values for the attributes I know like templateId or objectGroups.ids I get the same "TemplateSelector" error.


    Thanks,
    Steve

  • Admin
    Matt Sweet
    Jul 2, 2026

    Hello, please consider using the corresponding POST endpoint for these data. Using this endpoint instead will allow you to use the timespans you need as well as other filtering. Some parameters have to be left out of the GET implementation because of the payload limit on that method, but you should have all the functionality you need on the POST endpoint.