René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Query for cursor pagination support for V R12.","articleBody":"  ## Request: Add Cursor Pagination Support for NetBrain APIs\n\n  ### Current Implementation\n  The NetBrain integration currently uses **offset pagination** via the `beginIndex` parameter across multiple API endpoints.\n\n  ### Issue Description\n  While researching cursor-based pagination (using `afterId`), we discovered:\n  - No official documentation exists for `afterId` or cursor pagination support in NetBrain's API docs\n  - However, API error responses explicitly suggest using `AfterID` for pagination, indicating the feature may be available\n  - The current data response/extract does not include entity IDs, which are required to implement cursor-based pagination\n\n  ### APIs Affected\n  Querying this issue for the following NetBrain API endpoints::\n  1. `/CMDB/Topology/OneIPTable`\n  2. `/CMDB/Devices`\n  3. `/CMDB/Interfaces/Attributes`\n  4. `/CMDB/Topology/Devices/Neighbors`\n\n  ### Request\n  Is there any support around:\n  1. Whether cursor pagination using `afterId`/`AfterID` is officially supported?\n  2. How to retrieve entity IDs in API responses to enable cursor-based pagination?\n  3. Best practices for implementing cursor pagination across these endpoints?","author":{"url":"https://github.com/dixit-armis","@type":"Person","name":"dixit-armis"},"datePublished":"2025-12-25T10:15:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/2/NetBrain-REST-API-R12/issues/2"}