ExaVault
Community OpenAPI document · agent-readyStorageObject StorageapiKey59 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Move files in and out of ExaVault, manage shares and users, and audit account activity through one REST API.
Use for: I need to upload a vendor invoice PDF to the /invoices folder, Create a share link for the Q4 financials folder that expires in 7 days, List all active users on this ExaVault account, Find every share link that expires in the next 14 days
Not supported: Does not handle document editing, collaboration, or e-signature - use for managed file transfer, sharing, user, and account administration only.
ExaVault is a managed file-transfer and secure cloud-storage platform that exposes its file, share, and user-management features through a REST API. The 59-endpoint surface covers folders and resources, share links, notifications, SSH keys, recipient and email lists, activity logs, account configuration, and webhook setup. Agents use it to move files in and out of the platform, control who has access, and audit activity across the account.
Install Jentic One Beta
Connect the ExaVault to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ExaVault, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fexavault.com%2Fexavault" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fexavault.com%2Fexavault" | 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 ExaVault API.
Upload, download, and organise files and folders within an ExaVault account
Create and manage share links with expiry and recipient controls
Add, update, and deactivate user accounts and their permissions
Configure email notifications and notification rules for account activity
Manage SSH keys for secure file-transfer access
Pull session and webhook activity logs for auditing and integration
Use Cases
Patterns agents use ExaVault API for, with concrete tasks.
★ Vendor file ingestion pipeline
A finance agent watches a shared inbox, downloads incoming vendor invoices, and uploads them into a structured ExaVault folder by month. Webhooks then notify the downstream AP system that new files are ready for processing, removing the manual download-and-rename step.
Upload a vendor invoice PDF to /invoices/2026-06 in ExaVault, then verify a webhook fires to notify the AP system.
Time-bound share-link generation
A sales agent needs to share a contract pack with a prospect for a limited window. The integration agent calls ExaVault's share endpoints to create a new share with an expiry date and recipient email list, then returns the URL to embed in the outbound email.
Create an ExaVault share for /contracts/acme-q3.zip that expires in 7 days and includes prospect@example.com on the recipient list, then return the share URL.
User and SSH key provisioning
An IT ops agent provisions new automation accounts: it creates a user, attaches an SSH public key, and grants access to specific folders. ExaVault's user, SSH key, and resource endpoints make this a single scripted flow per new account.
Create a new ExaVault user 'svc-etl', attach an SSH public key, and grant read/write access to /etl/inbox.
AI agent file orchestration via Jentic
An AI assistant integrated through Jentic moves files between ExaVault folders and downstream systems on natural-language prompts. Jentic isolates the API key and resolves intent to specific ExaVault operations, so the assistant can upload, share, and audit files without ever holding the raw credentials.
Use Jentic to search for 'create an exavault share', load the operation, and generate a 7-day share link for a named folder on behalf of the user.
Key Endpoints
59 endpoints — exavault is a managed file-transfer and secure cloud-storage platform that exposes its file, share, and user-management features through a rest api.
METHOD
PATH
DESCRIPTION
GET
/account
Retrieve account configuration
GET
/activity/session
List session activity
GET
/activity/webhooks
List webhook activity
GET
/email-lists
List email recipient lists
POST
/email-lists
Create an email recipient list
POST
/email/welcome/{username}
Send a welcome email to a user
GET
/account
Retrieve account configuration
GET
/activity/session
List session activity
GET
/activity/webhooks
List webhook activity
GET
/email-lists
List email recipient lists
POST
/email-lists
Create an email recipient list
POST
/email/welcome/{username}
Send a welcome email to a user
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ExaVault by hand means learning its API key auth, pointing at your own accountname.exavault.com host, and tracking dozens of file, share, and account endpoints yourself. Through Jentic you install once, import ExaVault from the API Directory, store the API key once, and your agent calls it.
Permission scoping
ExaVault carries most targets in the request body or query, so scope the agent to the operations it needs, such as listing account activity or managing email lists. Destructive account and user administration operations stay out of the allowed set unless you add them.
Credential isolation
Your ExaVault API key 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.
Intent-based discovery
Agents search Jentic by intent such as 'upload a file to exavault' or 'create a share link', and Jentic returns the matching ExaVault operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using ExaVault API through Jentic.
What authentication does the ExaVault API use?
ExaVault uses API key authentication. Through Jentic, the API key is stored encrypted in your Jentic One instance and replaced with a scoped token at call time, so the raw key never enters the agent's context.
Can I create share links programmatically with the ExaVault API?
Yes. The /shares endpoints let an agent create new share links with recipients, expiry dates, and access controls, and the email-lists endpoints let you reuse curated recipient groups across shares.
How do I get notified when a file lands in ExaVault?
Configure a webhook through the activity/webhooks resource. ExaVault will then POST to your endpoint when matching activity occurs, and an agent can subscribe to those events to drive downstream pipelines.
What are the rate limits for the ExaVault API?
The OpenAPI spec does not publish explicit rate limits. ExaVault enforces account-level throttling at the platform layer, so agents should handle 429 responses with exponential backoff and respect Retry-After headers.
How do I upload a file through Jentic?
Run pip install jentic, search for 'upload a file to exavault', load the resources upload operation, and execute it with the target path and file payload. Jentic returns the response so the agent can confirm the upload succeeded.
Does ExaVault provide SSH/SFTP key management through the API?
Yes. The SSH Keys endpoints let an agent attach, list, and revoke SSH public keys for users. This is how automation accounts get programmatic SFTP-style access without manual key handling in the UI.
Can I limit what my agent is allowed to do with the ExaVault API?
Yes. Because Jentic One is self-hosted, your own rules decide which ExaVault operations and credentials the agent may use. You can allow only the endpoints it needs, such as listing account activity or managing email recipient lists, while keeping destructive account and user administration operations out of the allowed set unless you add them. Since ExaVault carries most targets in the request body or query, the operator controls exactly which calls the agent can make against the account.
GET STARTED