Files.com API

Name: Files.com API API
Brand: Files.com API
Availability: InStock

✓ Official Vendor SpecStorageObject StorageapiKey260 EndpointsREST

For Agents

Drive Files.com managed file transfer end to end - users, folders, automations, action notifications, and API keys - via a single X-FilesAPI-Key header.

Connect the Files.com API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Files.com 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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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 Files.com API API.

Provision API keys with scoped lifetimes for downstream automations and bots

Set up action notification exports so an agent gets a webhook when a file lands

Manage users, groups, and folder permissions to enforce least-privilege access

Orchestrate folder-level automations such as move, copy, and remote sync rules

GET STARTED

Start building with Files.com API API

Explore with Jentic

View OpenAPI Document

The Files.com API exposes 260 REST operations covering managed file transfer, secure cloud storage, and the orchestration features that wrap them - users, groups, permissions, automations, behaviors, action notifications, API keys, and bundles. Authentication is performed by sending an X-FilesAPI-Key header containing a user-scoped or site-wide API key. The API is the programmatic surface behind Files.com's enterprise MFT product, used by IT and operations teams that need to move sensitive files between partners, legacy SFTP systems, and cloud destinations.

Use Cases

Patterns agents use Files.com API API for, with concrete tasks.

★ Partner File Exchange Bundles

Operations teams that exchange large files with external partners can have an agent call POST /bundles to create a password-protected, time-limited share link, then deliver that link plus credentials to the partner over a secondary channel. The bundle is auto-revoked at expiry, removing the manual revocation step that often gets forgotten and avoiding stale share URLs.

Call POST /bundles with the source paths, an expiry of 7 days, and a generated password, then return the bundle URL and password to the workflow that requested the share.

Compliance Audit Reporting

Compliance teams subject to SOC 2 or HIPAA reviews can have an agent walk Files.com history endpoints, pull every action against a sensitive folder over the audit window, and emit a structured report. Files.com keeps the action history server-side, so the agent does not need to maintain its own log shipping pipeline to produce the artifact.

Call the relevant history list endpoint with a date range and folder filter, group by user, and write a CSV of every read, write, and delete action.

Inbound File Trigger to Workflow

Data engineering teams that drop CSVs into a Files.com folder for downstream ETL can have an agent register an action notification export so that every new file fires a webhook. The agent then fetches metadata, validates the schema, and dispatches the file to the correct ETL job - without polling.

Call POST /action_notification_exports with the folder path and target webhook URL, then handle each delivered event by validating and forwarding the file path to the ETL queue.

User and Permission Lifecycle

When a partner organization onboards or offboards, an agent can call into Files.com user, group, and permission endpoints to provision the user, place them in the correct group, and grant scoped folder access. On offboard, the same agent revokes API keys and removes group membership in a single sequence, closing the access loop.

Create the user, add them to the partner group, grant folder permissions, then on offboard delete the user, revoke their API keys, and remove group membership.

AI Agent Files.com Integration via Jentic

An agent connected to Jentic can search by intent across Files.com's 260 operations - for example create a secure share link - and Jentic returns only the relevant operations with their schemas. The X-FilesAPI-Key never enters the agent's context, and integration time drops from a multi-week MFT project to under an hour.

Search Jentic for create a files.com share bundle, load the POST /bundles schema, and execute with Jentic injecting the X-FilesAPI-Key from the vault.

Key Endpoints

260 endpoints — the files.

METHOD

PATH

DESCRIPTION

GET

/api_keys

List API keys for the site or user

POST

/api_keys

Create a new API key

POST

/action_notification_exports

Configure a webhook export for file events

GET

/action_notification_export_results

List delivery results for action notifications

GET

/api_key

Retrieve the current API key in use

PATCH

/api_key

Update the current API key

DELETE

/api_key

Revoke the current API key

GET

/api_keys

List API keys for the site or user

POST

/api_keys

Create a new API key

POST

/action_notification_exports

Configure a webhook export for file events

GET

/action_notification_export_results

List delivery results for action notifications

GET

/api_key

Retrieve the current API key in use

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Files.com API keys (X-FilesAPI-Key) are stored encrypted in the Jentic vault. Agents receive scoped vault references; the raw key never enters the agent's context, and rotations are transparent to the agent.

Intent-based discovery

Agents search Jentic by intent (for example create a share link) and Jentic returns the matching Files.com operation from across 260 paths with its input schema, so the agent does not have to navigate the full spec.

Time to first call

Direct Files.com integration: 1-2 weeks across auth, automations, and webhook signature verification. Through Jentic: under one hour - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Dropbox API

Consumer-friendly cloud storage rather than enterprise managed file transfer

Choose Dropbox when the workflow is end-user file sharing rather than partner-to-partner MFT with audit and compliance controls.

Alternative

Box API

Enterprise content cloud with collaboration and governance features

Choose Box when the workflow needs heavy collaboration features (comments, tasks, metadata templates) rather than scheduled MFT automations.

Complementary

Dropbox API

Sync files between Dropbox and Files.com remote mounts

Use Dropbox alongside Files.com when an agent needs to bridge consumer storage drops into the enterprise MFT pipeline.

FAQs

Specific to using Files.com API API through Jentic.

What authentication does the Files.com API use?

Files.com uses a static API key sent in the X-FilesAPI-Key header. The key can be user-scoped or site-wide. Through Jentic, the key lives in the encrypted vault and is injected at execution; the agent only ever sees a vault reference.

Can I create a password-protected share link with the Files.com API?

Yes. Use the bundles endpoints to create a bundle with an expiration and an optional password. The response returns the share URL, which an agent can then deliver to the recipient out of band.

What are the rate limits for the Files.com API?

Files.com applies per-site throttling at the gateway and the spec does not publish a single fixed limit. Agents should respect 429 responses with exponential backoff and prefer paginated listing endpoints over polling /history.

How do I trigger a workflow when a file is uploaded through Jentic?

Search Jentic for create a files.com action notification, load the POST /action_notification_exports operation, and execute it with your folder path and webhook URL. Jentic injects the X-FilesAPI-Key from the vault, so the credential never reaches the agent.

Can I rotate or revoke a Files.com API key programmatically?

Yes. The API exposes /api_keys for listing and creating, and /api_key for managing the current credential. An agent can mint a new key, swap it into downstream consumers, and then DELETE the old one to complete a rotation.

Is the Files.com API free to use?

API access is included with every paid Files.com plan. There is no separate API tier - the same plan limits that govern user count and storage also apply to API consumption.