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

Marketo Fragments (New) API

API endpoints for managing fragments created with the new Email Designer in Marketo Engage.

Marketo Fragments (New) API is one of 45 APIs that Marketo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Fragments (New). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 11 operations across 11 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://localhost:8080/.

11 operations 11 paths 32 schemas 2 GET9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{munchkinId}.mktorest.com/rest
Terms of Service
Resource Areas
1

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 2 GET, 9 POST. Each is listed below with its method, path, parameters, and response codes.

Fragments (New) 11

API endpoints for managing fragments created with the new Email Designer in Marketo Engage.

POST
/rest/asset/v2/fragment
Create Fragment
createContentUsingPOST_fragment 2 params body → 200default
POST
/rest/asset/v2/fragment/clone
Clone Fragment
cloneContentUsingPOST_fragment 2 params body → 200default
GET
/rest/asset/v2/fragment/filter
List Fragments
filterContentUsingGET_fragment 21 params → 200default
POST
/rest/asset/v2/fragment/state/transition
Update Fragment Status
stateTransitionUsingPOST_fragment 2 params body → 200default
POST
/rest/asset/v2/fragment/usedby
Get Fragment Used By
getContentUsedByUsingPOST_fragment 2 params body → 200default
GET
/rest/asset/v2/fragment/{id}
Get Fragment by Id
getContentUsingGET_fragment 3 params → 200default
POST
/rest/asset/v2/fragment/{id}/delete
Delete Fragment
deleteContentUsingPOST_fragment 3 params → 200default
POST
/rest/asset/v2/fragment/{id}/update
Update Fragment
updateContentUsingPOST_fragment 3 params body → 200default
POST
/rest/asset/v2/fragment/bulk/get
Bulk Get Fragments
bulkGetUsingPOST_fragment 2 params body → 200default
POST
/rest/asset/v2/fragment/bulk/delete
Bulk Delete Fragments
bulkDeleteUsingPOST_fragment 2 params body → 200default
POST
/rest/asset/v2/fragment/bulk/usedby
Bulk Get Fragments Used By
bulkUsedByUsingPOST_fragment 2 params body → 200default

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are FragmentContentDTO (16 properties), ContentMetadataDTO (8 properties), ContentWaveErrorDTO (8 properties), UsedByItemDTO (6 properties). Each schema is shown below with its type and property counts.

DataDTO
object
2 properties
FragmentSettingsDTO
object
3 properties 2 required
DeleteResponse
object
2 properties
BulkUsedByRequest
object
1 property 1 required
UsedByItemDTO
object
6 properties
AssociatedStateDTO
object
A version/state of the asset (e.g. draft or approved).
3 properties
UpdateFragmentRequest
object
Request body for updating a fragment.
5 properties
AppDataDTO
object
3 properties
FragmentContentDTO
object
16 properties
FragmentFilterResult
ThumbnailDTO
object
1 property
BulkUsedByItemDTO
object
4 properties
HtmlDataDTO
object
1 property
CreateFragmentRequest
object
Request body for creating a fragment. appData must include at least one of: folderId or workspaceId. settings must include fragmentType and supportedChannels.
6 properties 3 required
BulkUsedByResponse
object
3 properties
StateTransitionRequest
object
2 properties 2 required
CloneNewAsset
object
2 properties 1 required
ErrorResponse
object
3 properties
UsedByRequestDto
object
4 properties 1 required
UsedByResponse
object
4 properties
ContentWaveErrorDTO
object
An entry in the errors array. The type field marks it as info, warning, or error — there is no separate warnings array; warnings appear here with type "warning…
8 properties
ContentMetadataDTO
object
Audit information for the asset.
8 properties
EditorContextDto
object
1 property
TextDataDTO
object
2 properties
FragmentDetailDTO
PageDetailsDTO
object
3 properties
FragmentNewResponse
object
3 properties
FragmentFilterResponse
object
3 properties
BulkDeleteRequest
object
2 properties 1 required
UpdateFragmentSettingsDTO
object
3 properties
BulkGetRequest
object
1 property 1 required
CloneAssetRequest
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

marketo-fragments-new-api-openapi.yml Raw ↑

Other APIs Marketo publishes across the network.

Marketo Campaigns API
Marketo Channels API
Marketo Email Templates API
Marketo Emails API
Marketo File Contents API
Marketo Files API
Marketo Folders API
Marketo Form Fields API
Marketo Forms API
Marketo Landing Page Content API
Marketo Landing Page Redirect Rules API
Marketo Landing Page Templates API
Where this information came from

This is an independent, third-party profile of Marketo Fragments (New) 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.