canonical: https://jentic.com/apis/fastmode.ai/fastmode

# FastMode API

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.

## For AI agents

List CMS collections, create and update items inside them, capture form submissions, and upload media assets to FastMode.

## Scope

Does not handle user authentication, e-commerce, or page-template rendering - use for CMS collection, form, and media operations only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Collections** — List collections and read collection metadata
- **Items** — Create, read, update, and delete items inside a given collection
- **Forms** — Submit form responses and retrieve historical submissions
- **Media** — Upload binary media assets used by collection items

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Notion** — General-purpose document and database platform used as a lightweight CMS
- **Airtable** — Spreadsheet-database hybrid often used as a CMS backend
- **Cloudinary Upload** — Specialist image and video processing for media assets referenced by FastMode items

## FAQ

### 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.
