Pydio Cells API
✓ Official Vendor SpecProductivityCollaborationbearer, oauth243 EndpointsREST
For Agents
Programmatically get node metadata, create file or folder. Covers 43 operations with bearer, oauth2 authentication.
Use for: I need to node metadata, I want to file or folder, Search for files or folders, Find all restore deleted files or folders
Not supported: Does not handle payments, communications, or crm — use for productivity only.
REST API for Pydio Cells, the open-source file sharing and collaboration platform. Provides 248+ endpoints covering tree/file operations, user management, ACLs, roles, workspaces, sharing, activity streams, configuration, search, jobs/scheduler, authentication, frontend, and meta services. The API exposes 43 endpoints secured with bearer, oauth2 authentication.
Install Jentic One Beta
Connect the Pydio Cells API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pydio Cells 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 Pydio Cells API.
Get node metadata
Create file or folder
Delete files or folders
Restore deleted files or folders
Bulk stat nodes
Admin list nodes
Use Cases
Patterns agents use Pydio Cells API for, with concrete tasks.
★ Productivity Operations
Use the Pydio Cells API to perform productivity operations programmatically. The API provides 43 endpoints covering core functionality including get node metadata, create file or folder, delete files or folders.
Call GET /a/tree/stat/{Node} to get node metadata
Automated A Management
Automate a operations by combining multiple Pydio Cells API endpoints. Agents can create file or folder and then delete files or folders in a single workflow.
Call POST /a/tree/create to create file or folder, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Pydio Cells API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.
Search Jentic for 'get node metadata', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
43 endpoints — rest api for pydio cells, the open-source file sharing and collaboration platform.
METHOD
PATH
DESCRIPTION
GET
/a/tree/stat/{Node}
Get node metadata
POST
/a/tree/create
Create file or folder
POST
/a/tree/delete
Delete files or folders
POST
/a/tree/restore
Restore deleted files or folders
POST
/a/tree/selection
Create a temporary selection of nodes
POST
/a/tree/stats
Bulk stat nodes
POST
/a/tree/admin/list
Admin list nodes
GET
/a/user/{Login}
Get user by login
GET
/a/tree/stat/{Node}
Get node metadata
POST
/a/tree/create
Create file or folder
POST
/a/tree/delete
Delete files or folders
POST
/a/tree/restore
Restore deleted files or folders
POST
/a/tree/selection
Create a temporary selection of nodes
POST
/a/tree/stats
Bulk stat nodes
POST
/a/tree/admin/list
Admin list nodes
GET
/a/user/{Login}
Get user by login
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Pydio Cells API bearer, oauth2 credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get node metadata') and Jentic returns the matching Pydio Cells API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Pydio Cells API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Pydio Cells API through Jentic.
What authentication does the Pydio Cells API use?
The Pydio Cells API uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I get node metadata with the Pydio Cells API?
Yes. Use the GET /a/tree/stat/{Node} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Pydio Cells API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get node metadata through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get node metadata'. Jentic returns the matching Pydio Cells API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Pydio Cells API have?
The Pydio Cells API exposes 43 endpoints covering a operations.
GET STARTED