FastMode API
Official vendor OpenAPI document · agent-readyMarketingContent ManagementapiKey10 EndpointsREST
For Agents
List CMS collections, create and update items inside them, capture form submissions, and upload media assets to FastMode.
Use for: List all collections in this FastMode workspace, Get the items in the blog-posts collection, Create a new item in a FastMode collection, Update an existing item with revised content
Not supported: Does not handle user authentication, e-commerce, or page-template rendering - use for CMS collection, form, and media operations only.
The FastMode API gives programmatic access to a headless CMS organised around collections, items, forms, and media. Agents can list collection schemas, read and write items inside a collection, capture form submissions, and upload media assets. The 10-endpoint surface is designed for site builders and content-driven applications that want to automate publishing workflows rather than click through the FastMode UI.
Install Jentic One Beta
Connect the FastMode API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the FastMode 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffastmode.ai%2Ffastmode" | 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%2Ffastmode.ai%2Ffastmode" | 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 FastMode API.
List all collections configured in the FastMode workspace via GET /collections
Read collection items with pagination via GET /collections/{collectionSlug}/items
Create or update items inside a collection via POST and PUT on /collections/{collectionSlug}/items
Submit responses to a published form via POST /forms/{formName}/submit
Retrieve historical form submissions via GET /forms/submissions for analytics or follow-up
Upload media assets such as images and documents via POST /media/upload
Use Cases
Patterns agents use FastMode API for, with concrete tasks.
★ Programmatic Content Publishing
Editorial teams use FastMode as the headless backend for marketing sites and use the API to publish posts from external workflows. The agent reads the target collection schema, then POSTs an item to /collections/{collectionSlug}/items with the body, slug, and metadata. Replaces manual entry in the CMS UI for every published post.
POST a new blog item to /collections/blog-posts/items with title, body, and slug in the request payload
Form Submission Capture and Routing
Marketing landing pages route lead-capture form submissions into FastMode via /forms/{formName}/submit, then read them back through /forms/submissions for downstream workflows. Lets the team treat FastMode as the system of record for inbound form data without standing up a separate forms tool.
POST a form submission to /forms/contact-us/submit with the user-supplied fields, then GET /forms/submissions to confirm the entry was stored
Bulk Media Upload Pipeline
Teams migrating into FastMode use POST /media/upload to load image and document assets from another CMS or local archive. Combined with collection writes, the workflow rebuilds a content library programmatically. Saves weeks of manual upload effort during platform switches.
For each file in an export directory, POST to /media/upload with the binary, then reference the returned asset id when creating items via /collections/{collectionSlug}/items
AI Content Assistant via Jentic
Editorial agents use Jentic to call FastMode operations from natural-language prompts. The agent searches 'create a CMS item' and Jentic returns the right collection-write endpoint with its schema. The X-API-Key credential lives in your Jentic One instance, so the agent never sees the raw key and the writer can ship a working integration in under an hour.
Through Jentic, search 'create an item in a CMS collection', load POST /collections/{collectionSlug}/items, and execute with the user-drafted item payload
Key Endpoints
10 endpoints — the fastmode api gives programmatic access to a headless cms organised around collections, items, forms, and media.
METHOD
PATH
DESCRIPTION
GET
/collections
List all collections
GET
/collections/{collectionSlug}/items
List items in a collection
POST
/collections/{collectionSlug}/items
Create an item in a collection
PUT
/collections/{collectionSlug}/items/{itemSlug}
Update an existing item
POST
/forms/{formName}/submit
Submit a form response
GET
/forms/submissions
Retrieve form submissions
POST
/media/upload
Upload a media asset
GET
/collections
List all collections
GET
/collections/{collectionSlug}/items
List items in a collection
POST
/collections/{collectionSlug}/items
Create an item in a collection
PUT
/collections/{collectionSlug}/items/{itemSlug}
Update an existing item
POST
/forms/{formName}/submit
Submit a form response
GET
/forms/submissions
Retrieve form submissions
POST
/media/upload
Upload a media asset
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the FastMode API by hand means setting the API-key request header and threading the collection slug and item slug through nested item paths yourself. Through Jentic you install once, import FastMode from the API Directory, store the key once, and your agent calls it.
Permission scoping
FastMode puts the collection slug in the URL path (/collections/{collectionSlug}/items), so a rule can pin your agent to one collection. You choose the operations it may call, so writes like creating or updating an item are included only when you add them, while collection and submission reads can stay read-only.
Credential isolation
Your FastMode API-key request header 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 'create an item in a CMS collection', and Jentic returns the POST /collections/{collectionSlug}/items operation with its input schema so the agent calls the right endpoint without browsing the FastMode docs site.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using FastMode API through Jentic.
What authentication does the FastMode API use?
FastMode uses an API key in the X-API-Key header. Through Jentic the X-API-Key is stored encrypted in the vault and injected at execution time, so the raw key never enters the agent's prompt context.
Can I create collection items with the FastMode API?
Yes. POST to /collections/{collectionSlug}/items with the item payload to create a new entry, and PUT to /collections/{collectionSlug}/items/{itemSlug} to update an existing one. The collectionSlug is whatever you defined in the FastMode workspace.
What are the rate limits for the FastMode API?
FastMode does not publish explicit rate limits in the OpenAPI spec. Treat content writes as a moderate-volume workflow, throttle bulk media uploads, and back off on 429 responses.
How do I capture a form submission through Jentic?
Install with pip install jentic, search 'submit a form response', load POST /forms/{formName}/submit, and execute with the user-supplied form fields. Get started with Jentic One, the self-hosted execution layer.
Does the FastMode API support uploading binary media?
Yes. POST /media/upload accepts a binary asset and returns an identifier you can reference from item fields. Use it for images, documents, and other media that collection items need to embed.
Can I limit what my agent is allowed to do with the FastMode API?
Yes. Because you self-host Jentic One, your own rules decide which FastMode operations and credentials the agent may use. Since the collection slug lives in the URL path, such as /collections/{collectionSlug}/items, you can pin the agent to a single collection, and you choose which operations it may call, so item writes like POST and PUT on /collections/{collectionSlug}/items are included only when you add them. You can keep collection and submission reads such as GET /collections and GET /forms/submissions read-only, and leave POST /media/upload out entirely if the agent should not upload assets.
GET STARTED