Continuation Token for Endpoints

[smpa01]

The list_lakehouse  documentation shows a query parameters of continuationToken.

Is the first call to the GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/lakehouses endpoint supposed to return a continuationToken that needs to be utilized in a while loop for making subsequent calls?

I currently seee this as I don't have that many lakehouses in my dev workspace and it probably dos not return a continuationToken in the response body due to that. I see the following.

I am trying to determine how can I get hold of the continuationToken.

{
    "value": [
        {
            "id": "id1",
            "type": "Lakehouse",
            "displayName": "StagingLakehouse",
            "description": "",
            "workspaceId": "ws_id",
            "properties": {
                "oneLakeTablesPath": "tbl_path",
                "oneLakeFilesPath": "file_path",
                "sqlEndpointProperties": {
                    "connectionString": "sql_enp_1",
                    "id": "id_1",
                    "provisioningStatus": "Success"
                }
            }
        },
        {
            "id": "id2",
            "type": "Lakehouse",
            "displayName": "prd_lakehouse",
            "description": "",
            "workspaceId": "ws_id",
            "properties": {
                "oneLakeTablesPath": "tbl_path",
                "oneLakeFilesPath": "file_path",
                "sqlEndpointProperties": {
                    "connectionString": "sql_enp_2",
                    "id": "id_2",
                    "provisioningStatus": "Success"
                }
            }
        }
    ]
}

[Anonymous · Accepted solution]

HI @smpa01,

AS the document said, the continuation token appear with continuation URL, I think you can check the result URL and token part to confirm if they has the next page to invoke and loading data:

Items - List Lakehouses - REST API (Lakehouse) | Microsoft Learn
Regards,

Xiaoxin Sheng