canonical: https://jentic.com/apis/flotiq.com/flotiq

# Flotiq User API

The Flotiq User API is a headless CMS surface that serves the structured content objects, media, and tags defined in a Flotiq account. It reads and writes each content object individually or in batches, applies partial updates by patching selected fields, and keeps a full version history so an earlier state of an object can be fetched or audited. It also lists the identifiers of removed objects, so a downstream index can reconcile deletions rather than re-reading everything.

## For AI agents

Read and write the structured content objects, media, and tags in a Flotiq account, one at a time or in batches, with partial patches, full version history, and removed-object identifiers.

## Scope

Does not handle page rendering, user authentication, or payment. Use for managing structured content objects and media in a Flotiq account only.

## Capabilities

- Retrieve the structured content objects defined in a Flotiq account
- Add a content object or update selected fields with a patch
- Apply batch create, update, and delete across many objects in one request
- Upload and organise media objects
- Tag content and list objects by tag
- List every version of an object and fetch a specific one
- Find the identifiers of recently removed objects

## Use cases

### Agent content retrieval and publishing

An AI agent connected through Jentic reads the structured content objects in a Flotiq account to answer a question, then creates or patches an object to publish an update, so a site or app stays current without the developer hand-wiring the auth token or the per-type request shapes.

Example prompt: Create a new content object in a Flotiq account and patch a selected field on an existing one

### Bulk content migration

A migration tool moves a large set of records into Flotiq by posting them through the batch create endpoint and applies corrections with batch update, so thousands of objects land in a few calls instead of one request per record.

Example prompt: Create a batch of content objects in one request and apply a batch update to fix a field across them

### Content versioning and audit

A governance workflow lists every version of a content object and fetches an earlier one to compare, and reads the removed-object identifiers to reconcile deletions, so an external search index mirrors the Flotiq account accurately.

Example prompt: List the versions of a content object, fetch an earlier version, and read the removed-object identifiers to reconcile an index

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/content/_media` | List media objects |
| POST | `/api/v1/content/_media` | Create a media object |
| GET | `/api/v1/content/_media/{id}` | Get a media object by id |
| PUT | `/api/v1/content/_media/{id}` | Update a media object |
| GET | `/api/v1/content/_tag` | List tag objects |
| POST | `/api/v1/content/project/batch` | Create a batch of objects |
| GET | `/api/v1/content/project/{id}/version` | List every version of an object |
| GET | `/api/v1/content/_media/removed` | Get removed object identifiers |

## Key resources

- **Content objects** — Read and write content objects individually, in batches, and by version
- **Media** — Upload, read, and organise media objects
- **Tags** — Create tags and list content by tag
- **Versions** — List every version of an object and fetch a specific one

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 47 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 23 / 100
  - Agent Usability: 91 / 100
  - Security: 50 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/flotiq.com/flotiq/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Flotiq by hand means handling its X-AUTH-TOKEN header, learning the per-type content paths, and choosing between single-object and batch write flows yourself. Through Jentic you install once, import Flotiq from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Flotiq puts the content type and object id in the URL path (`/api/v1/content/{type}/{id}`), so a rule can pin your agent to read-only access on one content type. You choose the operations it may call, so write operations like batch delete or patching an object are not included unless you add them.
- **Credential handling:** Your Flotiq token 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 a content object' or 'list every version of an object', and Jentic returns the matching Flotiq operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Contentful** — Established headless CMS with a comparable content-object model
- **Sanity** — Structured-content platform with a query-first API rather than per-type REST endpoints
- **Airtable** — Spreadsheet-style structured records that can feed or mirror Flotiq content

## FAQ

### What authentication does the Flotiq User API use?

The Flotiq User API reads a personal auth token from the `X-AUTH-TOKEN` header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's context.

### Is there a Flotiq MCP server?

You don't need an MCP server to give your agent Flotiq. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the content read, write, and batch operations on demand, without a separate server's tool definitions loaded into its context.

### Can I limit what my agent is allowed to do with the Flotiq User API?

Yes. Flotiq puts the content type and object id in the URL path, so a rule can pin your agent to read-only access on one content type, letting it fetch objects but not patch them, run a batch delete, or touch media, with every call logged.

### Can I update content in batches with the Flotiq User API?

Yes. Each content type exposes batch create, batch update, and batch delete endpoints, so you can write or remove many objects in a single request rather than one call per record.

### What are the rate limits for the Flotiq User API?

The OpenAPI spec does not specify rate limits. Check the vendor documentation at https://flotiq.com for current limits before running large batch imports.

### How do I publish a content object through Jentic?

Search Jentic for 'create a content object', which returns the Flotiq create operation with its input schema, then post the object and patch any field you need to change. To run it on your own infrastructure, install Jentic One from its GitHub repo.