Filerobot DAM API
✓ Official Vendor SpecMediaImage ProcessingapiKey4 EndpointsREST
For Agents
List, upload, retrieve, and delete assets in a Filerobot DAM library via API key auth. Useful for agents managing product imagery and media catalogues.
Use for: Upload a new product image to Filerobot DAM, List all assets in my Filerobot library, Retrieve the metadata for a specific Filerobot asset, Delete a discontinued product image from Filerobot
Not supported: Does not handle on-the-fly image transformations, video transcoding, or CDN cache control - use for asset library CRUD on Filerobot DAM only.
The Filerobot DAM API exposes core digital asset management operations for the Filerobot platform - listing, uploading, retrieving, and deleting assets stored under a Filerobot account. Authentication is performed by sending a static API key in the Authorization header against the api.filerobot.com host. The API is intended for product catalogues, e-commerce sites, and marketing teams that need machine-driven control over image and file libraries that Filerobot then transforms and serves through its CDN.
Install Jentic One Beta
Connect the Filerobot DAM API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Filerobot DAM 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 Filerobot DAM API.
List assets in a Filerobot DAM library with filtering and pagination
Upload a new asset record into the Filerobot library via POST /assets
Fetch a specific asset by id to read its metadata before serving via CDN
Delete an asset by id when a product is retired from the catalogue
Drive bulk asset reconciliation between a PIM and Filerobot from an agent loop
Use Cases
Patterns agents use Filerobot DAM API for, with concrete tasks.
★ Product Image Catalogue Sync
E-commerce teams can run an agent that walks their product information manager and calls POST /assets for every new SKU image, then DELETE /assets/{id} when SKUs are discontinued. Filerobot then handles transformation and CDN delivery downstream. The sync turns a manual upload chore into a scheduled job that completes in seconds per SKU.
For each new SKU in the PIM, call POST /assets with the image binary and metadata, then store the returned asset id back on the SKU record.
Marketing Asset Audit
Marketing operations can ask an agent to call GET /assets and produce a report of orphaned or stale assets - those not referenced by any active campaign. The agent can then call DELETE /assets/{id} on confirmed candidates to keep the library lean and the storage bill predictable.
Call GET /assets, cross-reference the ids with the live campaign manifest, and call DELETE /assets/{id} for any asset older than 12 months that has no references.
Asset Metadata Lookup for Personalisation
A personalisation engine can call GET /assets/{id} on the fly when rendering a product page so the agent has the freshest title, alt text, and tags before generating a recommendation block. Because Filerobot returns metadata structured for DAM consumers, the agent can route different asset types to different rendering rules.
On personalisation request, call GET /assets/{id} for each candidate image and pick the asset whose tags best match the user's segment.
AI Agent Filerobot Integration via Jentic
An agent connected to Jentic can search by intent (for example upload a product image to my dam), receive the Filerobot POST /assets schema, and execute the call without ever holding the API key. The vendor's static API key never enters the agent's context, and integration drops from days of glue code to a single search-load-execute call.
Search Jentic for upload an asset to filerobot, load the POST /assets schema, and execute with the file payload while Jentic injects the API key from the vault.
Key Endpoints
4 endpoints — the filerobot dam api exposes core digital asset management operations for the filerobot platform - listing, uploading, retrieving, and deleting assets stored under a filerobot account.
METHOD
PATH
DESCRIPTION
GET
/assets
List assets in the Filerobot DAM library
POST
/assets
Upload a new asset
GET
/assets/{id}
Retrieve a specific asset and its metadata
DELETE
/assets/{id}
Delete an asset by id
GET
/assets
List assets in the Filerobot DAM library
POST
/assets
Upload a new asset
GET
/assets/{id}
Retrieve a specific asset and its metadata
DELETE
/assets/{id}
Delete an asset by id
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Filerobot API keys are stored encrypted in the Jentic vault. Agents receive scoped vault references; the raw Authorization header value never enters the agent's context.
Intent-based discovery
Agents search Jentic by intent (for example upload an asset to my dam) and Jentic returns the matching Filerobot operation with its input schema, so the agent calls the right endpoint without reading the spec.
Time to first call
Direct Filerobot integration: 1-2 days for auth setup, multipart upload handling, and error retries. Through Jentic: under one hour - search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Filerobot DAM API through Jentic.
What authentication does the Filerobot DAM API use?
Filerobot DAM uses an API key passed in the Authorization header on every request. Through Jentic, that key lives in the encrypted vault and is injected into requests at execution time, so the agent only sees a vault reference.
Can I upload an asset directly with the Filerobot DAM API?
Yes. Call POST /assets with the asset payload to create a new asset record in the library. The response includes the asset id you then use with GET /assets/{id} or DELETE /assets/{id}.
What are the rate limits for the Filerobot DAM API?
The OpenAPI spec does not declare explicit per-second limits. Filerobot enforces account-tier throttling at the gateway, so agents should respect 429 responses with exponential backoff and avoid bursting on the POST /assets endpoint.
How do I delete a specific asset from Filerobot via Jentic?
Search Jentic for delete a filerobot asset, load the DELETE /assets/{id} operation, and execute with the asset id. Jentic injects the API key from the vault so the credential never enters the agent's context.
Can I list every asset in my Filerobot library at once?
Use GET /assets to page through assets. The endpoint is the only listing operation in the spec, so for very large libraries an agent should iterate using pagination tokens rather than requesting everything in one shot.
Is the Filerobot DAM API free to use?
API access is bundled with a paid Filerobot subscription. There is no separate developer-only tier, and CDN egress is metered by the same plan that gates the DAM web UI.
GET STARTED