Adobe Suite

Adobe Suite Content fragment API

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

GitHub OpenAPI
Business capability
Content Marketing Management BC-400.70

Operations 8

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /fragments Create a content fragment · Create New Content Fragment #
Ask an LLM
“How do I create a new reusable content fragment of a given type?”
“Can I put a new fragment straight into a specific folder?”
Tell an agent
Create a {type} fragment named {name}.
Create fragment {name} of type {type} in folder {parentFolderId} described as {description}.
GET /fragments List content fragments · List Content Fragments #
Ask an LLM
“Which content fragments exist in my sandbox?”
“Can I filter fragments by name or type and sort the list?”
Tell an agent
List the content fragments in my sandbox.
List fragments filtered by {property}, sorted by {orderBy}.
GET /fragments/{fragmentId} Get a content fragment's details · Fetch Content Fragment By Id #
Ask an LLM
“What's in a content fragment, including its current draft content?”
“Can I fetch one fragment's detail by its ID?”
Tell an agent
Get content fragment {fragmentId}.
Show me the working details of fragment {fragmentId}.
PUT /fragments/{fragmentId} Replace a content fragment · Update Content Fragment By Id #
Ask an LLM
“How do I overwrite a fragment's name, type and content in full?”
“Why does a full fragment update need the current etag in If-Match?”
Tell an agent
Replace fragment {fragmentId} with name {name} and type {type}.
Fully update fragment {fragmentId} at etag {etag}, moving it to folder {parentFolderId}.
PATCH /fragments/{fragmentId} Patch a fragment's name, description or folder · Patch Content Fragment By Id #
Ask an LLM
“Can I change just a fragment's name without resending its content?”
“Which fields can a JSON Patch on a fragment touch?”
Tell an agent
Patch fragment {fragmentId} to rename it to the name I give you.
Move fragment {fragmentId} to another folder with a JSON Patch at etag {etag}.
POST /fragments/publications Publish a content fragment · Publish Content Fragment #
Ask an LLM
“How do I publish a fragment so campaigns and journeys can use it?”
“Does publishing a fragment freeze its content?”
Tell an agent
Publish content fragment {fragmentId}.
Start a publication of fragment {fragmentId} before I activate the campaign.
GET /fragments/{fragmentId}/liveFragment Get a fragment's last published content · Fetch content of fragment's last successful publication #
Ask an LLM
“What content is live for a fragment from its last successful publication?”
“Can I see the published version rather than the draft of a fragment?”
Tell an agent
Get the live published content of fragment {fragmentId}.
Show what fragment {fragmentId} looked like at its last successful publish.
GET /fragments/{fragmentId}/lastPublicationStatus Check a fragment's last publication status · Fetch status of last publication #
Ask an LLM
“Did my last fragment publication succeed, fail or is it still in progress?”
“Can I poll the status of a fragment's most recent publish request?”
Tell an agent
Check the last publication status of fragment {fragmentId}.
Tell me whether fragment {fragmentId} finished publishing.

Documentation

📖
Documentation
https://developer.adobe.com/photoshop/api/docs/
📖
Authentication
https://developer.adobe.com/developer-console/docs/guides/authentication/
📖
Documentation
https://developer.adobe.com/lightroom/api/docs/
📖
Documentation
https://developer.adobe.com/illustrator/api/docs/
📖
Documentation
https://developer.adobe.com/indesign/docs/
📖
Documentation
https://developer.adobe.com/document-services/docs/overview/pdf-services-api/
📖
Documentation
https://developer.adobe.com/document-services/docs/overview/pdf-extract-api/
📖
GettingStarted
https://developer.adobe.com/document-services/docs/overview/pdf-extract-api/gettingstarted/
📖
Documentation
https://developer.adobe.com/document-services/docs/overview/pdf-accessibility-auto-tag-api/
📖
Documentation
https://developer.adobe.com/analytics-apis/docs/
📖
APIReference
https://developer.adobe.com/analytics-apis/docs/2.0/
📖
Documentation
https://developer.adobe.com/firefly-services/docs/
📖
APIReference
https://developer.adobe.com/firefly-services/docs/api/
📖
Documentation
https://developer.adobe.com/audio-video-firefly-services/
📖
GettingStarted
https://developer.adobe.com/audio-video-firefly-services/getting-started/
📖
Documentation
https://developer.adobe.com/creative-cloud-libraries/docs/
📖
APIReference
https://developer.adobe.com/creative-cloud-libraries/docs/api/
📖
Documentation
https://developer.adobe.com/express/embed-sdk/docs/guides/
📖
APIReference
https://developer.adobe.com/express/embed-sdk/docs/v4/
📖
GettingStarted
https://developer.adobe.com/express/embed-sdk/docs/guides/quickstart/
📖
Documentation
https://developer.adobe.com/experience-platform-apis/
📖
GettingStarted
https://experienceleague.adobe.com/en/docs/experience-platform/landing/platform-apis/api-guide
📖
Documentation
https://developer.adobe.com/marketo-apis/
📖
Authentication
https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication
📖
Documentation
https://developer.adobe.com/commerce/docs/
📖
GettingStarted
https://developer.adobe.com/commerce/webapi/get-started/
📖
Documentation
https://developer.adobe.com/experience-cloud/cloud-manager/
📖
Documentation
https://developer.adobe.com/journey-optimizer-apis/
📖
Documentation
https://developer.adobe.com/workfront-apis/
📖
Documentation
https://developer.adobe.com/firefly-services/docs/substance3d/
📖
Documentation
https://developer.adobe.com/data-collection-apis/
📖
Documentation
https://developer.adobe.com/adobe-status/
📖
Documentation
https://developer.adobe.com/vip-marketplace/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/adobe-suite/refs/heads/main/openapi/adobe-suite-content-fragment-api-api-openapi.yml

Other Resources

🔗
Pricing
https://developer.adobe.com/document-services/pricing/
🔗
SDKs
https://developer.adobe.com/document-services/docs/overview/pdf-services-api/sdks/
🔗
ReleaseNotes
https://developer.adobe.com/document-services/docs/overview/pdf-services-api/releasenotes
🔗
Guides
https://developer.adobe.com/analytics-apis/docs/2.0/guides/
🔗
Guides
https://developer.adobe.com/firefly-services/docs/guides/
🔗
Usage Notes
https://developer.adobe.com/audio-video-firefly-services/getting_started/usage/
🔗
Overview
https://developer.adobe.com/creative-cloud-libraries/docs/overview/
🔗
Integration Guide
https://developer.adobe.com/creative-cloud-libraries/docs/integrate/
🔗
API Fundamentals
https://experienceleague.adobe.com/en/docs/experience-platform/landing/platform-apis/api-fundamentals
🔗
Developer Guide
https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/home
🔗
REST API
https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api
🔗
REST API
https://developer.adobe.com/commerce/webapi/rest/
🔗
GraphQL API
https://developer.adobe.com/commerce/webapi/graphql-api/
🔗
REST API Reference
https://developer.adobe.com/commerce/webapi/reference/rest/paas/
🔗
GraphQL
https://raw.githubusercontent.com/api-evangelist/adobe-suite/refs/heads/main/graphql/adobe-suite-graphql.md
🔗
Webhooks
https://developer.adobe.com/experience-cloud/cloud-manager/guides/getting-started/create-event-integration/
🔗
StatusPage
https://status.adobe.com/

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/adobe-suite:adobe-suite-content-fragment-api-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

adobe-suite-content-fragment-api-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  description: Using this REST API, you can create and manage content templates and fragments, which are entities that allow you to easily reuse custom content across Journey Optimizer campaigns and journeys. To learn more about content templates and fragments, refer to Journey Optimizer documentation.
  version: 0.0.1
  title: Content API. Content fragment API
servers:
- url: https://platform.adobe.io/ajo/content
- url: https://platform-stage.adobe.io/ajo/content
security:
- imsUserToken: []
tags:
- name: Content fragment API
paths:
  /fragments:
    parameters:
    - $ref: '#/components/parameters/APIKeyParam'
    - $ref: '#/components/parameters/ImsOrgIdParam'
    - $ref: '#/components/parameters/SandboxNameParam'
    - $ref: '#/components/parameters/RequestIdParam'
    post:
      operationId: createFragment
      summary: Create New Content Fragment
      description: This API could be used for creating a new content fragment
      tags:
      - Content fragment API
      requestBody:
        description: new fragment
        content:
          application/vnd.adobe.ajo.fragment.v1.0+json:
            schema:
              $ref: '#/components/schemas/content-fragment'
        required: true
      responses:
        201:
          $ref: '#/components/responses/201'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
    get:
      parameters:
      - $ref: '#/components/parameters/orderBy'
      - $ref: '#/components/parameters/limit'
      - $ref: '#/components/parameters/start'
      - $ref: '#/components/parameters/property'
      operationId: getFragments
      summary: List Content Fragments
      description: 'Content Fragment Listing API. There are few attributes which are filterable.

        id - Supported operations are equals and not equals.


        name - Supports operations are regex and contains.


        type - Supported operations are equal and not equals, and allowed values are [ "html"]


        channels - Supported operations are equals and not equals.


        createdAt - Supported operations are less-than, less-than-equal-to, greater-than, greater-than-equal-to, equals-to.


        createdBy - Supported operations are equals, not equals and regex.


        modifiedAt - Supported operations are less-than, less-than-equal-to, greater-than, greater-than-equal-to, equals-to.


        modifiedBy - Supported operations are equals, not equals and regex.


        origin - Supported operations are equals and not equals.'
      tags:
      - Content fragment API
      responses:
        200:
          description: Content Fragment Listing API response.
          content:
            application/vnd.adobe.ajo.fragment-list.v1.0+json:
              schema:
                $ref: '#/components/schemas/fragment-page-response'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
  /fragments/{fragmentId}:
    parameters:
    - name: fragmentId
      in: path
      description: Content fragment id
      required: true
      schema:
        type: string
    - name: Accept
      in: header
      required: true
      schema:
        type: string
        enum:
        - application/vnd.adobe.ajo.fragment.v1.0+json
    - $ref: '#/components/parameters/APIKeyParam'
    - $ref: '#/components/parameters/ImsOrgIdParam'
    - $ref: '#/components/parameters/SandboxNameParam'
    - $ref: '#/components/parameters/RequestIdParam'
    get:
      operationId: getFragment
      summary: Fetch Content Fragment By Id
      description: Fetch Content Fragment detail by Id.
      tags:
      - Content fragment API
      responses:
        200:
          description: Successful operation
          content:
            application/vnd.adobe.ajo.fragment.v1.0+json:
              schema:
                $ref: '#/components/schemas/content-fragment-with-audit'
          headers:
            etag:
              $ref: '#/components/headers/etag'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
        404:
          $ref: '#/components/responses/404'
    put:
      operationId: putFragment
      summary: Update Content Fragment By Id
      description: API to update Content Fragment By Id.
      tags:
      - Content fragment API
      parameters:
      - $ref: '#/components/parameters/IfMatchParam'
      requestBody:
        description: New/Updated Content Fragment Payload.
        content:
          application/vnd.adobe.ajo.fragment.v1.0+json:
            schema:
              $ref: '#/components/schemas/content-fragment'
        required: true
      responses:
        204:
          $ref: '#/components/responses/204'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
        404:
          $ref: '#/components/responses/404'
        409:
          $ref: '#/components/responses/409'
    patch:
      operationId: patchFragment
      summary: Patch Content Fragment By Id
      description: 'Patch fragment with given id. Expects Patch request in JSON-patch format (RFC 6902)

        Path supported: "/name", "/description", "/parentFolderId"'
      tags:
      - Content fragment API
      parameters:
      - $ref: '#/components/parameters/IfMatchParam'
      requestBody:
        content:
          application/json-patch+json:
            schema:
              $ref: '#/components/schemas/patch-request'
        required: true
      responses:
        204:
          $ref: '#/components/responses/204'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
        404:
          $ref: '#/components/responses/404'
  /fragments/publications:
    parameters:
    - $ref: '#/components/parameters/APIKeyParam'
    - $ref: '#/components/parameters/ImsOrgIdParam'
    - $ref: '#/components/parameters/SandboxNameParam'
    - $ref: '#/components/parameters/RequestIdParam'
    post:
      operationId: publishFragment
      summary: Publish Content Fragment
      description: 'API to publish fragment.

        Publishing a content fragment will freeze the content of the fragment. Notably, it is a pre-requisite to publish a fragment before activating / publishing a campaign / journey. Fragment Publication is an async process under the hood which can take a few seconds. The status of the fragment publication can be fetched by lastPublicationStatus API whereas the content of the last successful publication of a fragment can be fetched by the liveFragment API.'
      tags:
      - Content fragment API
      requestBody:
        description: publish request body
        content:
          application/vnd.adobe.ajo.fragment.publication.request.v1.0+json:
            schema:
              $ref: '#/components/schemas/publish-fragment-request'
        required: true
      responses:
        202:
          $ref: '#/components/responses/202'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
  /fragments/{fragmentId}/liveFragment:
    parameters:
    - name: fragmentId
      in: path
      description: Content fragment id
      required: true
      schema:
        type: string
    - $ref: '#/components/parameters/APIKeyParam'
    - $ref: '#/components/parameters/ImsOrgIdParam'
    - $ref: '#/components/parameters/SandboxNameParam'
    - $ref: '#/components/parameters/RequestIdParam'
    get:
      operationId: getLiveFragment
      summary: Fetch content of fragment's last successful publication
      description: Fetch content of fragment's last successful publication. A fragment can have multiple publications. A publication can either be successful, in progress or can error out. This API will be responsible for fetching the content of the last successful publication for a fragment.
      tags:
      - Content fragment API
      responses:
        200:
          description: Successful operation
          content:
            application/vnd.adobe.ajo.fragment.publication.v1.0+json:
              schema:
                $ref: '#/components/schemas/live-fragment-content'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
        404:
          $ref: '#/components/responses/404'
  /fragments/{fragmentId}/lastPublicationStatus:
    parameters:
    - name: fragmentId
      in: path
      description: Content fragment id
      required: true
      schema:
        type: string
    - $ref: '#/components/parameters/APIKeyParam'
    - $ref: '#/components/parameters/ImsOrgIdParam'
    - $ref: '#/components/parameters/SandboxNameParam'
    - $ref: '#/components/parameters/RequestIdParam'
    get:
      operationId: getLastPublicationStatus
      summary: Fetch status of last publication
      description: Fetch the status of last publication request for a content fragment by Id. A fragment can have multiple publications. A publication can either be successful, in progress or can error out. This API will be responsible for fetching the status of the last issued publication request for a fragment.
      tags:
      - Content fragment API
      responses:
        200:
          description: Successful operation
          content:
            application/vnd.adobe.ajo.fragment.publication.v1.0+json:
              schema:
                $ref: '#/components/schemas/publishing-job-status'
        400:
          $ref: '#/components/responses/400'
        401:
          $ref: '#/components/responses/401'
        403:
          $ref: '#/components/responses/403'
        404:
          $ref: '#/components/responses/404'
components:
  schemas:
    patch-document:
      title: Patch Document
      description: A JSONPatch document as defined by RFC 6902
      required:
      - op
      - path
      properties:
        op:
          type: string
          description: The operation to be performed
          enum:
          - add
          - remove
          - replace
        path:
          type: string
          description: A JSON-Pointer
        value:
          type: object
          description: The value to be used within the operations.
        from:
          type: string
          description: A string containing a JSON Pointer value.
    expression-content:
      type: string
      title: Expression Content
      description: Expression Content
      example: Hi {{profile.person.name}} its a great day to shop !!
    olac-labels:
      title: OLAC Label Details
      type: array
      items:
        type: string
        example: custom/sensitive-data
    description:
      type: string
      title: Description
      description: Description
      example: Cyber Monday Sale - Header Banner!!
    fragment-list-link:
      title: Content Fragment List Link.
      type: object
      required:
      - self
      properties:
        next:
          $ref: '#/components/schemas/href-link'
        page:
          $ref: '#/components/schemas/href-link'
      example:
        next:
          href: /fragments?start=eyJtb2RpZmllZEF0IjoxNjA2OTc2NzI3NTQ5fQ==&limit=20&orderBy=%2BmodifiedAt
        page:
          href: /fragments?orderBy={orderBy}&start={start}&limit={limit}
    errorResponse:
      title: Error Response
      type: object
      properties:
        path:
          type: string
          title: Path
          example: /templates
          description: API path
        request-id:
          type: array
          title: Request ID
          items:
            type: string
            example: 9db4dd09-455f-44eb-a0e3-aca3342745d2
          description: Request ID
        type:
          type: string
          title: Type
          example: https://ns.adobe.com/aep/errors/CJMMAS-*
          description: Error type
        title:
          type: string
          title: Title
          example: Error Title
          description: Title of Error
        status:
          type: integer
          title: Status
          description: HTTP status
        report:
          type: object
          title: report
          description: Error Report
          properties:
            tenantInfo:
              type: object
              example:
                sandboxName: cjm-team
                sandboxId: 70f58060-5d47-11ea-bdff-a5384333ff34
                imsOrgId: 745F37C35E4B776E0A49421B@AdobeOrg
            additionalContext:
              type: object
              example:
                detailedMessage: templates
              description: Additional Context of Error
        error-chain:
          type: array
          title: Error Chain
          description: Error Chain
          items:
            type: object
            example:
              serviceId: contentservice
              errorCode: CJMMAS-*
              invokingServiceId: cjm-content-service
              unixTimeStampMs: 1610446917396
    fragment-page-response:
      title: Content Fragment Page Response
      type: object
      properties:
        _page:
          $ref: '#/components/schemas/page'
        items:
          type: array
          items:
            $ref: '#/components/schemas/content-fragment-listing-response'
        _links:
          $ref: '#/components/schemas/fragment-list-link'
    name:
      type: string
      title: Content Name
      description: Content Name
      example: Cyber Monday Sale - Header !!
      minLength: 1
    href-link:
      title: Href-link
      type: object
      required:
      - href
      properties:
        href:
          type: string
    page:
      title: Page
      type: object
      properties:
        orderBy:
          type: string
          enum:
          - modifiedAt
          - createdAt
          - name
          example: -modifiedAt
        start:
          type: string
          format: byte
          example: eyJtb2RpZmllZEF0IjoxNjA2OTc2NzI3NTQ5fQ==
        next:
          type: string
          format: byte
          example: eyJtb2RpZmllZEF0IjoxNjA2OTc2NzI3NTQ5fQ==
        count:
          type: integer
          example: 10
    parent-folder-id:
      type:
      - string
      - 'null'
      title: Folder Id
      description: Id of the folder in which the content is present.
      example: a49dbe03-34e6-4231-aba0-0c255a9f08a1
    fragment-source:
      title: Fragment Source.
      type:
      - object
      - 'null'
      required:
      - origin
      properties:
        origin:
          $ref: '#/components/schemas/fragment-origin'
        metadata:
          title: MetaData
          description: Map containing custom properties(key-value pair).
          additionalProperties: true
    fragment-self-href:
      title: Self-Href
      type: object
      properties:
        self:
          type: object
          properties:
            href:
              type: string
              example: /fragments/b6d70a45-a149-453b-85ba-809a5d40066d
    content-fragment-metadata:
      title: Content Fragment metadata.
      type: object
      required:
      - name
      - type
      - channels
      properties:
        id:
          $ref: '#/components/schemas/id'
        name:
          $ref: '#/components/schemas/name'
        description:
          $ref: '#/components/schemas/description'
        type:
          $ref: '#/components/schemas/fragment-type'
        status:
          $ref: '#/components/schemas/fragment-status'
        channels:
          $ref: '#/components/schemas/fragment-channel-enum'
        labels:
          $ref: '#/components/schemas/olac-labels'
        source:
          $ref: '#/components/schemas/fragment-source'
        parentFolderId:
          $ref: '#/components/schemas/parent-folder-id'
    entity-audit-fields:
      title: Entity Audit Fields.
      type: object
      properties:
        createdAt:
          type: string
          format: date-time
          example: '2016-08-29T09:12:33.001Z'
        createdBy:
          type: string
          example: 4c0190e5d702748f0931@AdobeId
        modifiedAt:
          type: string
          format: date-time
          example: '2016-08-29T09:12:33.001Z'
        modifiedBy:
          type: string
          example: 4c0190e5d702748f0931@AdobeId
    content-fragment-listing-response:
      title: Content Fragment
      type: object
      allOf:
      - $ref: '#/components/schemas/content-fragment-metadata'
      - $ref: '#/components/schemas/entity-audit-fields'
      - $ref: '#/components/schemas/fragment-self-href'
    content-fragment:
      title: Content Fragment
      type: object
      discriminator:
        propertyName: type
        mapping:
          html: '#/components/schemas/email-html-fragment'
          expression: '#/components/schemas/expression-fragment'
      required:
      - name
      - type
      - channels
      properties:
        name:
          $ref: '#/components/schemas/name'
        description:
          $ref: '#/components/schemas/description'
        type:
          $ref: '#/components/schemas/fragment-type'
        source:
          $ref: '#/components/schemas/fragment-source'
        parentFolderId:
          $ref: '#/components/schemas/parent-folder-id'
    fragment-origin:
      type: string
      title: Origin
      description: Content Fragment Origin/Source system.
      enum:
      - ajo
      - external
    id:
      type: string
      title: Content Template Id.
      description: Content Template Id.
      example: b6d70a45-a149-453b-85ba-809a5d40066d
    fragment-status:
      type: string
      title: Fragment Status
      description: Fragment Status
      example: DRAFT
      enum:
      - DRAFT
      - PUBLISHING
      - PUBLISHED
    fragment-channel-enum:
      type: string
      title: channel
      description: Supported channels for Content Fragment.
      example: email
      enum:
      - email
      - shared
    published-expression-fragment-content:
      description: Published Expression Fragment content
      title: Published Expression Fragment content.
      type: object
      required:
      - expression
      properties:
        expression:
          $ref: '#/components/schemas/expression-content'
    publish-fragment-request:
      type: object
      properties:
        fragmentId:
          $ref: '#/components/schemas/id'
      required:
      - fragmentId
    fragment-content:
      type: string
      title: Html Fragment Content
      description: Html Fragment Content
      example: <div> Hi {{profile.person.name}} its a great day to shop !! </div>
    publishing-job-status:
      type: object
      properties:
        status:
          type: string
          enum:
          - complete
          - inProgress
          - error
        errors:
          type: array
          items:
            $ref: '#/components/schemas/errorResponse'
    live-fragment-content:
      title: Published Content Fragment
      type: object
      required:
      - type
      - fragment
      properties:
        type:
          $ref: '#/components/schemas/fragment-type'
        fragment:
          oneOf:
          - $ref: '#/components/schemas/published-html-fragment-content'
          - $ref: '#/components/schemas/published-expression-fragment-content'
    content-fragment-with-audit:
      title: Content Fragment with audit fields.
      type: object
      discriminator:
        propertyName: type
        mapping:
          html: '#/components/schemas/html-fragment-with-audit'
          expression: '#/components/schemas/expression-fragment-with-audit'
      required:
      - name
      - type
      - channels
      properties:
        id:
          $ref: '#/components/schemas/id'
        name:
          $ref: '#/components/schemas/name'
        description:
          $ref: '#/components/schemas/description'
        type:
          $ref: '#/components/schemas/fragment-type'
        status:
          $ref: '#/components/schemas/fragment-status'
        channels:
          $ref: '#/components/schemas/fragment-channel-enum'
        labels:
          $ref: '#/components/schemas/olac-labels'
        source:
          $ref: '#/components/schemas/fragment-source'
        parentFolderId:
          $ref: '#/components/schemas/parent-folder-id'
    patch-request:
      title: Patch Request
      type: array
      items:
        $ref: '#/components/schemas/patch-document'
    published-html-fragment-content:
      description: Published HTML Fragment content
      title: Published HTML Fragment content.
      type: object
      required:
      - content
      properties:
        content:
          $ref: '#/components/schemas/fragment-content'
    fragment-type:
      type: string
      title: Fragment Type
      description: Fragment Type
      example: html
      enum:
      - html
      - expression
  parameters:
    property:
      name: property
      description: '<p>Optional property filters.  Filtering is supported on following properties: id, name, status, description, fragmentType, templateType, modifiedAt, createdAt, createdBy and modifiedBy Ex. property=id==31e62feb-69b7-4e7b-8065-a921455c2c15&property=name~^test</p>'
      in: query
      schema:
        items:
          type: string
        type: array
      required: false
      example: property=name~^test
    start:
      name: start
      description: Used for pagination. Specifies the criteria for next page with respect to the property specified in orderBy.
      in: query
      schema:
        type: string
        format: byte
      required: false
      example: start=eyJtb2RpZmllZEF0IjoxNjA2OTc2NzI3NTQ5fQ==
    ImsOrgIdParam:
      name: x-gw-ims-org-id
      in: header
      description: Your Identity Management Services (IMS) Organization id
      required: true
      schema:
        type: string
    RequestIdParam:
      in: header
      name: x-request-id
      description: A unique string to identify the request, MUST be unique for each request
      required: false
      schema:
        type: string
    orderBy:
      name: orderBy
      description: Sort parameter and direction for sorting the response. Add the prefix as -/+ for desc/asc. If unspecified, the response will be sorted in desc order.
      in: query
      schema:
        type: string
        default: -modifiedAt
      required: false
      example: orderBy=%2BmodifiedAt.
    APIKeyParam:
      name: x-api-key
      in: header
      description: API Key
      required: true
      schema:
        type: string
        x-example: cjm client
    SandboxNameParam:
      name: x-sandbox-name
      in: header
      description: Filter on platform sandbox name
      required: true
      schema:
        type: string
    limit:
      name: limit
      description: Limit response to a specified positive number of objects. Ex. limit=10
      in: query
      schema:
        type: integer
        default: 20
        minimum: 1
        maximum: 1000
      required: false
    IfMatchParam:
      name: If-Match
      in: header
      required: true
      description: etag of resource to match before update of resource.
      schema:
        type: string
  headers:
    etag:
      schema:
        type: string
      description: etag of resource
  securitySchemes:
    imsUserToken:
      type: http
      scheme: bearer
      bearerFormat: JWT
    imsServiceToken:
      type: http
      scheme: bearer
      bearerFormat: JWT