List containers by parent lane | API reference

Description

Lists the containers the caller can reach through direct grants or managed-principal membership, one bounded page for each of up to four requested parent lanes, each with its own watermark. Clients use it to discover and incrementally refresh the folder tree. Any signed-in user may call it; access is checked per container.

Authentication

Requires a signed-in session: the client sends its session token as a bearer token in the Authorization header.

Request body

application/jsonListContainerParentLanesRequest

Up to four parent lanes to list, each with its own watermark and page size.

1 field

laneslist of objectrequired
- 1 to 4 items
4 fields
- laneIdstringrequired
  - 1 to 64 characters
- limitintegeroptional
  - 1 to 500
- parentIdstringrequirednullable
  - lowercase UUID v4
- watermarkobjectrequirednullable
  2 fields
  - idstringrequired
    not empty
  - updatedAtstringrequired
    not empty

Responses

200 OK

application/jsonListContainerParentLanesResponse

One page per requested parent lane, in request order.

1 field

resultslist of objectrequired
- 1 to 4 items
2 fields
- laneIdstringrequired
  - 1 to 64 characters
- pageListContainersResponserequired

Other responses

Status	Meaning	Body
400	Bad Request	`application/json`ErrorResponse
401	Unauthorized	`application/json`SessionFailureResponse
500	Internal Server Error	`application/json`ErrorResponse
503	Service Unavailable	`application/json`ErrorResponse

Additional rules

The server also enforces these rules, which the schema above cannot express.

Container parent-lane request lane ids must be unique.
Container parent-lane request page limits must total at most 500.
Container parent-lane response lane ids must be unique.