pCloud API
★ Only Publicly Available OpenAPI DocumentStorageObject Storageoauth2, apiKey13 EndpointsREST
For Agents
Read and modify files and folders on a pCloud account — list, upload, download, copy, rename, and delete — using OAuth 2.0 or an access token.
Use for: List the contents of my pCloud root folder, Upload a file to a specific pCloud folder, Download a file from pCloud by id, Create a new folder named 'invoices' in pCloud
Not supported: Does not handle document editing, version control diffs, or media transcoding — use for cloud file and folder management only.
Jentic publishes the only available OpenAPI specification for pCloud API, keeping it validated and agent-ready. pCloud is a consumer and SMB cloud storage platform, and the API exposes the operations needed to manage files, folders, and user accounts. Callers can list folder contents, create or rename folders, upload and download files, copy and rename files, and inspect basic user information. Authentication is supported via OAuth 2.0 or a static access token, and a digest endpoint helps with secure password-derived flows used by older client SDKs.
Install Jentic One Beta
Connect the pCloud API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the pCloud API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with pCloud API.
List the contents of a folder via /listfolder for navigation and search
Create, rename, and delete folders with /createfolder, /renamefolder, and /deletefolder
Upload files via /uploadfile and download them with /downloadfile
Copy and rename files using /copyfile and /renamefile
Inspect basic account information through /userinfo
Obtain a digest for password-derived authentication flows via /getdigest
Use Cases
Patterns agents use pCloud API for, with concrete tasks.
★ Cloud File Backup Automation
Build a backup job that uploads local files to a designated pCloud folder by calling /createfolder to ensure the destination exists, then /uploadfile for each file. Listings via /listfolder confirm successful uploads, and /renamefile or /copyfile can reorganise files after they arrive. Ideal for nightly backups of small filesystems where pCloud's storage tier is the destination of record.
Ensure /createfolder for path '/backups/2026-06-09' succeeds, then POST each local file to /uploadfile under that folder and confirm via /listfolder.
Document Synchronisation
Keep a folder of documents in sync with a pCloud account by listing remote contents through /listfolder, comparing against a local manifest, and using /uploadfile, /downloadfile, /renamefile, and /deletefolder to reconcile differences. Suitable for content pipelines that publish generated reports to a shared cloud space without operating a full sync client.
Call GET /listfolder for the target path, diff against local files, then upload missing entries via /uploadfile and remove obsolete ones with /deletefolder.
Credentialed File Retrieval for Agents
Allow an autonomous workflow to pull a configuration or asset file from pCloud at runtime without baking the access token into the application. /downloadfile retrieves the file by id once /listfolder has resolved its path. This is useful for templated artefacts or shared reference data that lives in pCloud but is consumed by automation elsewhere.
Call GET /listfolder to resolve the file's id by name, then GET /downloadfile with that id to retrieve the bytes.
AI Agent Storage Assistant via Jentic
Have an agent answer requests like 'put this report in my pCloud invoices folder' by calling pCloud through Jentic. Jentic returns the right operation per intent, the agent uploads the file, and the OAuth access token stays in the Jentic vault — protecting the user's entire cloud drive from accidental exposure in agent prompts or logs.
Search Jentic for 'upload a file to pCloud', load the POST /uploadfile schema, and execute with the target folder id and file payload.
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for pcloud api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/listfolder
List contents of a folder
POST
/createfolder
Create a new folder
POST
/uploadfile
Upload a file
GET
/downloadfile
Download a file
POST
/copyfile
Copy a file
POST
/renamefile
Rename a file
POST
/deletefolder
Delete a folder
GET
/userinfo
Retrieve user account information
GET
/listfolder
List contents of a folder
POST
/createfolder
Create a new folder
POST
/uploadfile
Upload a file
GET
/downloadfile
Download a file
POST
/copyfile
Copy a file
POST
/renamefile
Rename a file
POST
/deletefolder
Delete a folder
GET
/userinfo
Retrieve user account information
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
pCloud OAuth 2.0 tokens and static access tokens are stored encrypted in the Jentic vault. Agents call pCloud operations through Jentic and never see raw credentials — important because a leaked token grants access to the user's entire cloud drive.
Intent-based discovery
Agents search Jentic with intents like 'upload a file to pCloud' or 'list folder contents', and Jentic returns the matching pCloud operation with its input schema.
Time to first call
Direct pCloud integration: 1-2 days for OAuth, token refresh, and file upload streaming. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using pCloud API through Jentic.
Why is there no official OpenAPI spec for pCloud API?
pCloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call pCloud API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the pCloud API use?
The pCloud API supports two schemes — OAuth 2.0 for delegated user access and a static access token (apiKey) for service accounts. /getdigest is also exposed for password-derived flows used by some legacy clients. Through Jentic, both credential types are stored encrypted in the Jentic vault and injected per request.
Can I upload and download files with the pCloud API?
Yes. POST /uploadfile uploads a file to a specified folder, and GET /downloadfile retrieves it by id. Use /listfolder first to resolve folder ids and confirm filenames. /copyfile and /renamefile let you reorganise files after upload.
What are the rate limits for the pCloud API?
Rate limits are not declared in the spec. Treat /listfolder and /downloadfile as the highest-volume calls and avoid recursive directory walks without pagination guards. On HTTP 429 or platform-specific error codes, retry with exponential backoff.
How do I upload a file to pCloud through Jentic?
Search Jentic for 'upload a file to pCloud', load the POST /uploadfile schema, and execute with the destination folder id and file content. With `pip install jentic` the call is a single execute() invocation; the OAuth or access token stays in the Jentic vault.
Is the pCloud API free?
API access is included with a pCloud account. Free accounts have limited storage; paid plans extend capacity. The API itself does not impose separate fees, but downloads and uploads are bound by the storage and bandwidth limits attached to the user's plan.
GET STARTED