Filepass API

Name: Filepass API API
Brand: Filepass API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDocument Managementoauth210 EndpointsREST

For Agents

Manage Filepass projects, clients, comments, and webhooks via OAuth 2.0. Useful for agents automating media production review and approval flows.

Connect the Filepass API to your agent

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

List projects scoped to a specific client and create new projects under that client

Retrieve threaded comments attached to any file system object for review summaries

Look up the authenticated user profile via the /me endpoint to confirm OAuth scope

GET STARTED

Start building with Filepass API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Filepass API, keeping it validated and agent-ready.

The Filepass API lets clients programmatically manage projects, clients, comments, file system objects, payments, and webhook hooks for users authenticated via OAuth 2.0 authorization code flow. It exposes ten endpoints for listing and creating projects under specific clients, retrieving comments attached to file system objects, and registering webhooks for change notifications. The API is designed for media production teams that need to integrate Filepass file collaboration into review, billing, and approval workflows.

Use Cases

Patterns agents use Filepass API API for, with concrete tasks.

★ Automated Media Review Notifications

Production teams using Filepass can register webhooks against the /hooks endpoint so an agent is notified the moment a comment is added to a file system object. The agent can then summarise feedback and route it to the right reviewer. Setup takes one OAuth handshake and a single POST /hooks call.

Register a webhook on POST /hooks pointing at the agent endpoint, then on each event fetch GET /file_system_objects/{id}/comments and summarise.

Client-Scoped Project Provisioning

Agencies that onboard new clients can have an agent call POST /clients/{client_id}/projects to spin up a templated project structure when a new deal closes in CRM. Filepass returns the project record so the agent can post the project URL back into the deal record.

Call POST /clients/{client_id}/projects with the templated project payload and return the project id to the originating CRM record.

Cross-Project Comment Aggregation

Operations teams running weekly reviews can have an agent walk every project visible to the OAuth token, pull GET /comments, and produce a digest of unresolved feedback. This avoids manually opening each Filepass project and replaces a recurring 30 minute task with a sub-minute call.

Iterate GET /projects, then for each project call GET /comments and compose a digest of comments authored in the last 7 days.

AI Agent Filepass Integration via Jentic

An agent connected to Jentic can search by intent (for example process media review feedback) and Jentic returns the matching Filepass operations along with their input schemas. The agent then executes the call without the OAuth token ever entering its context. End-to-end integration time drops from a multi-day OAuth implementation to under an hour.

Search Jentic for list filepass projects, load the operation schema, and execute it with the user's vaulted Filepass OAuth token.

Key Endpoints

10 endpoints — the filepass api lets clients programmatically manage projects, clients, comments, file system objects, payments, and webhook hooks for users authenticated via oauth 2.

METHOD

PATH

DESCRIPTION

GET

/me

Return the authenticated user profile

GET

/clients

List clients accessible to the current token

GET

/clients/{client_id}/projects

List projects under a specific client

POST

/projects

Create a new project

GET

/comments

List comments across the workspace

GET

/file_system_objects/{file_system_object_id}/comments

List comments on a specific file system object

POST

/hooks

GET

/me

Return the authenticated user profile

GET

/clients

List clients accessible to the current token

GET

/clients/{client_id}/projects

List projects under a specific client

POST

/projects

Create a new project

GET

/comments

List comments across the workspace

Why though Jentic?

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

Credential isolation

Filepass OAuth client secrets and refresh tokens are stored encrypted in the Jentic vault. Agents receive scoped, short-lived bearer references; raw OAuth tokens never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (for example list filepass projects) and Jentic returns the matching Filepass operation with its input schema, so the agent can execute without browsing Swagger.

Time to first call

Direct Filepass integration: 2-4 days for OAuth, token refresh, and webhook signature handling. Through Jentic: under one hour - search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Dropbox API

General-purpose file storage and sharing API rather than media-review focused

Choose Dropbox when the workflow centres on raw file storage and sharing rather than threaded review comments tied to projects.

Alternative

Box API

Enterprise file collaboration with metadata, comments, and tasks

Choose Box when the user needs enterprise-grade compliance, granular permissions, and metadata templates rather than Filepass's lightweight project model.

Complementary

Filestack API

Pairs with Filepass for upload, transformation, and CDN delivery

Use Filestack alongside Filepass when files need ingestion, image transforms, or CDN delivery before review in Filepass projects.

FAQs

Specific to using Filepass API API through Jentic.

What authentication does the Filepass API use?

Filepass uses OAuth 2.0 authorization code flow with a single api scope, exchanging an authorization code at https://api.filepass.com/oauth/token for a bearer access token. Through Jentic, the OAuth tokens are stored in the encrypted vault and the agent only ever receives a scoped reference, never the raw secret.

Can I list comments on a specific file with the Filepass API?

Yes. Call GET /file_system_objects/{file_system_object_id}/comments with the file system object id to retrieve every comment attached to that file. There is also a global GET /comments endpoint when you want comments across the workspace.

What are the rate limits for the Filepass API?

The OpenAPI spec does not publish explicit per-minute rate limits. Filepass has historically applied per-token throttling, so agents should respect 429 responses with exponential backoff and refresh the OAuth token only when a 401 is returned.

How do I register a webhook with Filepass through Jentic?

Search Jentic for register filepass webhook, load the POST /hooks operation, and execute it with your callback URL and event filter. Jentic injects the OAuth bearer token from the vault so the agent never handles the credential directly.

Can I create a project under a specific client with the Filepass API?

Yes. Use POST /projects with the client id in the request body, or use the client-scoped GET /clients/{client_id}/projects collection to see existing projects for that client before creating a new one.

Is the Filepass API free to use?

API access is included with a paid Filepass workspace and is gated by the same plan limits as the Filepass web app. There is no separate API-only tier published in the spec.