We are currently integrating with the pCloud API and noticed that the folder and file path information is missing from the API responses. While other metadata such as file ID, name, parent folder, and size are correctly returned, the complete path is not included in the response.
This causes issues when we need to display or manage files/folders hierarchically in our application.
Expected Behavior:
The API should return the full path for each folder and file (e.g., /root/documents/project1/file.txt) as part of the response.
Actual Behavior:
The API returns metadata without the path field, which makes it difficult to reconstruct the directory structure on the client side.
Example Response (Current):
{
"metadata": {
"name": "file.txt",
"fileid": 12345,
"parentfolderid": 67890
}
}
Expected Response:
{
"metadata": {
"name": "file.txt",
"fileid": 12345,
"parentfolderid": 67890,
"path": "/root/documents/project1/file.txt"
}
}
Steps to Reproduce:
Call the /listfolder or /listfiles endpoint.
Observe that the response does not include the path attribute.
Impact:
Without the full path:
It’s difficult to resolve folder hierarchy on the client side.
We need to make multiple additional calls to reconstruct paths, which increases latency and complexity.
Request:
Please include the path field (full folder/file path) in the API response for all relevant endpoints, especially /listfolder.
Environment:
API: pCloud REST API
Endpoint: /listfolder, /listfiles
Language: Node.js (NestJS backend)
We are currently integrating with the pCloud API and noticed that the folder and file path information is missing from the API responses. While other metadata such as file ID, name, parent folder, and size are correctly returned, the complete path is not included in the response.
This causes issues when we need to display or manage files/folders hierarchically in our application.
Expected Behavior:
The API should return the full path for each folder and file (e.g., /root/documents/project1/file.txt) as part of the response.
Actual Behavior:
The API returns metadata without the path field, which makes it difficult to reconstruct the directory structure on the client side.
Example Response (Current):
{
"metadata": {
"name": "file.txt",
"fileid": 12345,
"parentfolderid": 67890
}
}
Expected Response:
{
"metadata": {
"name": "file.txt",
"fileid": 12345,
"parentfolderid": 67890,
"path": "/root/documents/project1/file.txt"
}
}
Steps to Reproduce:
Call the /listfolder or /listfiles endpoint.
Observe that the response does not include the path attribute.
Impact:
Without the full path:
It’s difficult to resolve folder hierarchy on the client side.
We need to make multiple additional calls to reconstruct paths, which increases latency and complexity.
Request:
Please include the path field (full folder/file path) in the API response for all relevant endpoints, especially /listfolder.
Environment:
API: pCloud REST API
Endpoint: /listfolder, /listfiles
Language: Node.js (NestJS backend)