How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Adobe Suite

Adobe Suite Content fragment API

The Content fragment API API from Adobe Suite — 5 operation(s) for content fragment api.

Documentation Provider Profile APIs.io OpenAPI GitHub

Adobe Suite Content fragment API is one of 482 APIs that Adobe Suite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Content fragment API. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, pricing, release notes, and a getting-started guide.

This API exposes 8 operations across 5 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against 2 base URLs: https://platform.adobe.io/ajo/content, https://platform-stage.adobe.io/ajo/content.

8 operations 5 paths 30 schemas 4 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://image.adobe.io
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Adobe Suite Content fragment API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (imsUserToken). It accepts HTTP bearer tokens (JWT) (imsServiceToken). By default, every request must be authenticated.

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 4 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Content fragment API 8
POST
/fragments
Create New Content Fragment.
createFragment 4 params body → 201400401403
GET
/fragments
List Content Fragments.
getFragments 8 params → 200400401403
GET
/fragments/{fragmentId}
Fetch Content Fragment By Id.
getFragment 6 params → 200400401403404
PUT
/fragments/{fragmentId}
Update Content Fragment By Id.
putFragment 7 params body → 204400401403404409
PATCH
/fragments/{fragmentId}
Patch Content Fragment By Id.
patchFragment 7 params body → 204400401403404
POST
/fragments/publications
Publish Content Fragment.
publishFragment 4 params body → 202400401403
GET
/fragments/{fragmentId}/liveFragment
Fetch content of fragment's last successful publication
getLiveFragment 5 params → 200400401403404
GET
/fragments/{fragmentId}/lastPublicationStatus
Fetch status of last publication
getLastPublicationStatus 5 params → 200400401403404

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are content-fragment-metadata (9 properties), content-fragment-with-audit (9 properties), errorResponse (7 properties), content-fragment (5 properties). Each schema is shown below with its type and property counts.

description
string
Description
content-fragment-with-audit
object
9 properties 3 required
expression-content
string
Expression Content
fragment-self-href
object
1 property
errorResponse
object
7 properties
olac-labels
array
entity-audit-fields
object
4 properties
fragment-list-link
object
2 properties 1 required
page
object
4 properties
content-fragment-metadata
object
9 properties 3 required
fragment-source
objectnull
2 properties 1 required
name
string
Content Name
publishing-job-status
object
2 properties
fragment-type
string
Fragment Type
patch-request
array
content-fragment
object
5 properties 3 required
fragment-status
string
Fragment Status
fragment-content
string
Html Fragment Content
published-html-fragment-content
object
Published HTML Fragment content
1 property 1 required
id
string
Content Template Id.
fragment-origin
string
Content Fragment Origin/Source system.
parent-folder-id
stringnull
Id of the folder in which the content is present.
live-fragment-content
object
2 properties 2 required
fragment-page-response
object
3 properties
href-link
object
1 property 1 required
publish-fragment-request
object
1 property 1 required
patch-document
object
A JSONPatch document as defined by RFC 6902
4 properties 2 required
fragment-channel-enum
string
Supported channels for Content Fragment.
published-expression-fragment-content
object
Published Expression Fragment content
1 property 1 required
content-fragment-listing-response
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

adobe-suite-content-fragment-api-api-openapi.yml Raw ↑

Other APIs Adobe Suite publishes across the network.

Adobe Sign API
AE Profile APIs.io
Adobe Experience Manager API
AE Profile APIs.io
Adobe Stock API
AE Profile APIs.io
Adobe Premiere Pro API
AE Profile APIs.io
Adobe After Effects API
AE Profile APIs.io
Adobe Target API
AE Profile APIs.io
Adobe Campaign API
AE Profile APIs.io
Adobe User Management API
AE Profile APIs.io
Adobe I/O Events API
AE Profile APIs.io
Adobe MCP Servers
AE Profile APIs.io
Adobe Suite Accelerated Queries API
AE Profile APIs.io
Adobe Suite Access Control Policies API
AE Profile APIs.io
#Content fragment API
← Back to A APIs
API Details
ID
adobe-suite:adobe-suite-content-fragment-api-api
Base URL
https://image.adobe.io
Docs
https://developer.adobe.com/photoshop/
Provider
Adobe Suite
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=adobe-suite-content-fragment-api-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/adobe-suite-content-fragment-api-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Adobe Suite Content fragment API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.