Get assets in a folder (not implemented)
Placeholder route — the handler is not implemented and responds `501 Not Implemented`. In addition, the route is gated by a `canGetFolderAssets` right that is not a registered permission, so the permission middleware currently rejects every request with `500 unknownError` before the handler runs. No query parameters are validated. Use `GET /projects/{projectId}/files/{visibility}/{path}` to list a folder's contents.
Deprecated
Placeholder route — the handler is not implemented and responds 501 Not Implemented. In addition, the route is gated by a canGetFolderAssets right that is not a registered permission, so the permission middleware currently rejects every request with 500 unknownError before the handler runs. No query parameters are validated. Use GET /projects/{projectId}/files/{visibility}/{path} to list a folder's contents.
OAuth 2.1 authorization code flow with PKCE (required of every client, public or confidential). Scopes are a ceiling on the credential, not a grant of access: a token also cannot exceed what the user who approved it may already do. A write scope does not imply its matching read — ask for both.
In: header
Scope: assets:read
Path Parameters
Unique identifier of the folder.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$uuidResponse Body
application/json
curl -X GET "https://example.com/folders/497f6eca-6276-4993-bfeb-53cbbbba6f08/assets"