canonical: https://jentic.com/apis/api.pcloud.com/pcloud # pCloud API 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. ## For AI 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. ## Scope Does not handle document editing, version control diffs, or media transcoding - use for cloud file and folder management only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 your Jentic One instance - protecting the user's entire cloud drive from accidental exposure in agent prompts or logs. Example prompt: 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 | 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 | ## Key resources - **Folders** — Create, rename, list, and delete folders - **Files** — Upload, download, copy, and rename files - **User** — Inspect basic account information - **Auth** — Digest endpoint for password-derived flows ## Why Jentic - **Setup:** Wiring pCloud by hand means setting up its OAuth2 or access_token auth, choosing the right US or EU data center host, and assembling file and folder operations yourself. Through Jentic you install once, import pCloud from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** pCloud takes folder and file targets in query and body parameters rather than a fixed resource path, so scope the agent to the operations it needs, such as listing folders and uploading files, and leave out delete folder unless you add it. You choose the allowed operations, so the agent only calls what you list. - **Credential handling:** Your pCloud token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'upload a file to a folder' or 'list my pCloud folders', and Jentic returns the matching pCloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Dropbox API** — Mature consumer and team file storage platform - **Box API** — Enterprise-focused content cloud with governance features - **Google Drive API** — Google's cloud storage with deep Workspace integration ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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 your Jentic One instance 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 your Jentic One instance. ### 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. ### Can I limit what my agent is allowed to do with the pCloud API? Yes. Because Jentic One is self-hosted, you decide which pCloud operations your agent may call, so you can grant read-and-write actions like /listfolder and /uploadfile while leaving out /deletefolder and /renamefile unless you add them. Since pCloud takes folder and file targets in query and body parameters rather than a fixed resource path, scoping is done at the operation level, and the agent can only invoke the operations you have listed. Your OAuth or access token stays inside your own instance and is injected per request, so the agent never sees it.