canonical: https://jentic.com/apis/filerobot.com/filerobot # Filerobot DAM API 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. ## For AI 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. ## Scope Does not handle on-the-fly image transformations, video transcoding, or CDN cache control - use for asset library CRUD on Filerobot DAM only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Assets** — List, upload, fetch, and delete digital assets stored in the Filerobot DAM library ## Why Jentic - **Setup:** Wiring the Filerobot DAM API by hand means sending the token in the Authorization header, pointing at api.filerobot.com, and handling asset CRUD paging yourself. Through Jentic you install once, import the Filerobot DAM API from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Filerobot puts the asset id in the URL path (/assets/{id}), so a rule can pin your agent to the assets you allow. You choose the operations it may call, so a destructive action like deleting an asset is not included unless you add it to the read and create operations. - **Credential handling:** Your Filerobot API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. The raw Authorization header value never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'upload an asset to my dam' or 'list assets', and Jentic returns the matching Filerobot operation with its input schema, so the agent calls the right endpoint without reading the spec. ## Related APIs - **Cloudinary Upload API** — Image and video DAM with deeper transformation pipeline than Filerobot - **Filestack API** — File handling with upload, transform, and delivery primitives - **Shopify Admin API** — Shopify product and variant management that often pairs with a DAM ## FAQ ### 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. ### Can I limit what my agent is allowed to do with the Filerobot DAM API? Yes. Because you run Jentic One yourself, your own rules decide which Filerobot operations the agent may call, so you can allow it to list and read assets with GET /assets and GET /assets/{id} while withholding POST /assets or the destructive DELETE /assets/{id}. Since Filerobot puts the asset id in the URL path (/assets/{id}), a rule can also pin the agent to only the specific assets you permit. Your Filerobot API key is held by your own instance and injected at execution time, so the agent scopes what it touches without ever seeing the raw credential.