Contentful Images API

Name: Contentful Images API
Brand: Contentful Images API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage Processingnone1 EndpointsREST

For Agents

Resize, crop, and reformat images stored in Contentful via signed CDN URLs. Supports format conversion (WebP, AVIF, JPEG, PNG), quality controls, and focal-point cropping.

Install Jentic One Beta

Connect the Contentful Images API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Contentful Images 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.

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

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 instance

Jentic 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 Contentful Images API.

Resize Contentful-hosted images to a target width and height through URL parameters

Convert between JPEG, PNG, WebP, AVIF, and GIF formats on-the-fly

Apply smart focal-point cropping using face or feature detection

GET STARTED

Start building with Contentful Images API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Contentful Images API for, with concrete tasks.

★ Responsive Image Delivery

Front-end teams use the Contentful Images API to generate responsive variants of a single source asset, picking width, format, and quality at request time rather than uploading multiple renditions. The CDN handles the transformation and caches the result, so build pipelines do not need to pre-render every breakpoint. Integration is a few minutes because the transformation is just URL parameters appended to the existing asset URL.

Build a srcset for a Contentful asset with widths 400, 800, and 1600, format=webp, and quality=75

Format Modernisation Without Re-upload

Teams migrating to AVIF or WebP can convert legacy JPEG or PNG assets in Contentful by appending fm=avif or fm=webp to existing URLs, with optional quality (q) and fit parameters. No re-upload or workflow change is needed in the headless CMS, and old URLs continue to work for clients that do not request the new format. This avoids a bulk asset migration project.

Generate the URL to fetch a Contentful asset as AVIF at quality 70 and fit=thumb with face-aware focus area

Programmatic Thumbnail Generation

Editorial and e-commerce platforms generate consistent thumbnails for content lists by requesting fixed dimensions with smart focus cropping. The fit=thumb and f=face parameters keep faces or product features centred without manual crop work. Because the CDN caches the transformed result, repeated requests for the same variant are served instantly.

Request a 300x300 thumbnail of a Contentful product image with fit=thumb and f=face for a category page tile

AI Agent Asset Optimisation via Jentic

An AI agent embedded in a content workflow uses Jentic to discover the Contentful Images URL grammar and produce optimised variants when given a source asset. The agent reads the operation schema, builds the URL with the right query parameters, and returns the transformed URL to downstream tooling. No credentials are required because Contentful asset URLs already include their own signing token.

Search Jentic for 'transform a contentful image', load the schema, and return a URL that serves the asset at 1200px wide as WebP with quality 80

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for contentful images api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/{space_id}/{asset_id}/{token}/{filename}

Retrieve and transform a Contentful image asset using URL query parameters

GET

/{space_id}/{asset_id}/{token}/{filename}

Retrieve and transform a Contentful image asset using URL query parameters

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Contentful Images API needs no stored token, since the per-asset signed token travels as a path parameter, and Jentic One still records each call in its audit trail. No secret enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'transform a Contentful image', and Jentic returns the single transform operation with its query-parameter schema so the agent calls it correctly without memorising the Contentful Images URL grammar.

Time to first call

FAQs

Specific to using Contentful Images API through Jentic.

Why is there no official OpenAPI spec for Contentful Images API?

Contentful does not publish an OpenAPI specification for the Images CDN. Jentic generates and maintains this spec so that AI agents and developers can call Contentful Images API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Contentful Images API use?

The Images API does not require an API token. Each asset URL already contains a signed token between the asset_id and filename, which gates access to private assets. Through Jentic the URL is constructed with the user-supplied token in the path and no additional credential is held in the vault.

Can I resize and convert images with the Contentful Images API?

Yes. Append URL query parameters to GET /{space_id}/{asset_id}/{token}/{filename} - for example w=800&h=600&fit=fill&fm=webp&q=80 to resize and convert format. Smart cropping uses f=face or f=center.

What are the rate limits for the Contentful Images API?

Contentful applies CDN-level rate limits per signed URL and per source IP, with cached variants served without counting toward origin transformation quotas. Through Jentic, retries are handled at the SDK level so transient 429 responses do not surface to agent code.

How do I generate a transformed image URL with the Contentful Images API through Jentic?

Run `jentic.search('transform a contentful image')`, load the operation, and execute with space_id, asset_id, token, filename, and the desired width, height, format, and quality parameters. Jentic returns the transformed CDN URL ready to embed in HTML or pass to the next step.

Does the Contentful Images API support AVIF and WebP?

Yes. Set fm=avif or fm=webp in the query string to convert any source asset on the fly, with q controlling output quality. The transformed result is cached by the CDN so repeated requests are served instantly.

Can I limit what my agent is allowed to do with the Contentful Images API?

Yes. Because Jentic One is self-hosted, you decide which operations your agent may call, and your own rules govern its access. The Contentful Images API exposes only a single read-and-transform operation over existing image assets, so an agent scoped to it can resize, crop, and reformat assets but cannot modify, upload, or delete anything. You choose whether to expose even that one transform operation to a given agent.