List and traverse files and folders in a OneDrive or SharePoint drive using drive discovery, children listing, path-based addressing, and pagination.

Documented steps

1. Resolve the target drive first: GET /me/drive for the signed-in user's OneDrive, GET /users/{idOrUserPrincipalName}/drive for another user, GET /groups/{groupId}/drive for a group's document library, GET /sites/{siteId}/drive for a SharePoint site's default library, or GET /drives/{driveId} if you already have the drive ID.
2. The drive-get response includes id, driveType (e.g. "business"), owner, and a quota object with deleted/remaining/state/total byte counts.
3. List items at the root: GET /me/drive/root/children (or GET /drives/{drive-id}/items/{item-id}/children, /groups/{group-id}/drive/items/{item-id}/children, /sites/{site-id}/drive/items/{item-id}/children, /users/{user-id}/drive/items/{item-id}/children).
4. For path-based addressing instead of item IDs: GET https://graph.microsoft.com/v1.0/drives/{drive-id}/root:/{path-relative-to-root}:/children (colon-delimited path segment before /children).
5. The children response is {"value": [ ...driveItem objects... ], "@odata.nextLink": "https://..."}; each driveItem carries a folder facet (e.g. {"folder": {"childCount": 4}}) or a file facet plus size — use these to distinguish folders from files.
6. Server-side paging: the default page size for children listings is 200 items. If the collection exceeds that, the response includes @odata.nextLink with the full URL for the next page — keep calling it until no @odata.nextLink is returned.
7. Use $top, $skipToken, $select, $expand and $orderby (documented as supported on list-children) to control page size and shape the response.
8. Docs: https://learn.microsoft.com/en-us/graph/api/driveitem-list-children?view=graph-rest-1.0 ; https://learn.microsoft.com/en-us/graph/api/drive-get?view=graph-rest-1.0 ; https://learn.microsoft.com/en-us/graph/paging