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
Marketo

Marketo Content API

The Content API from Marketo — 12 operation(s) for content.

Documentation Provider Profile APIs.io OpenAPI GitHub

Marketo Content API is one of 68 APIs that Marketo publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Content. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 14 operations across 12 paths, and defines 18 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://{munchkinId}.mktorest.com.

14 operations 12 paths 18 schemas 3 GET11 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://{munchkinId}.mktorest.com/rest
Contact
Adobe Developer Relations
License
API License Agreement
Terms of Service
View terms
Resource Areas
1

Paths & Operations 14

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

Content 14
POST
/rest/asset/v1/email/{id}/content/rearrange.json
Marketo Rearrange Email Modules
rearrangeModulesUsingPOST 1 param body → 200
POST
/rest/asset/v1/email/{id}/content/{htmlId}.json
Marketo Update Email Content Section
updateEmailComponentContentUsingPOST 2 params body → 200
POST
/rest/asset/v1/email/{id}/content/{moduleId}/add.json
Marketo Add Email Module
addModuleUsingPOST 4 params → 200
POST
/rest/asset/v1/email/{id}/content/{moduleId}/delete.json
Marketo Delete Module
deleteModuleUsingPOST 2 params → 200
POST
/rest/asset/v1/email/{id}/content/{moduleId}/duplicate.json
Marketo Duplicate Email Module
duplicateModuleUsingPOST 3 params → 200
POST
/rest/asset/v1/email/{id}/content/{moduleId}/rename.json
Marketo Rename Email Module
renameUsingPOST 3 params → 200
GET
/rest/asset/v1/email/{id}/dynamicContent/{contentId}.json
Marketo Get Email Dynamic Content
getEmailDynamicContentUsingGET 3 params → 200
POST
/rest/asset/v1/email/{id}/dynamicContent/{contentId}.json
Marketo Update Email Dynamic Content Section
updateEmailDynamicContentUsingPOST 2 params body → 200
GET
/rest/asset/v1/emailTemplate/{id}/content
Marketo Get Email Template Content by Id
getTemplateContentByIdUsingGET 2 params → 200
POST
/rest/asset/v1/landingPage/{id}/content/{contentId}.json
Marketo Update Landing Page Content Section
updateLandingPageContentUsingPOST 2 params body → 200
POST
/rest/asset/v1/landingPage/{id}/content/{contentId}/delete.json
Marketo Delete Landing Page Content Section
removeLandingPageContentUsingPOST 2 params → 200
GET
/rest/asset/v1/landingPage/{id}/dynamicContent/{contentId}.json
Marketo Get Landing Page Dynamic Content
getLandingPageDynamicContentsUsingGET 2 params → 200
POST
/rest/asset/v1/landingPage/{id}/dynamicContent/{contentId}.json
Marketo Update Landing Page Dynamic Content Section
updateLandingPageDynamicContentUsingPOST 2 params body → 200
POST
/rest/asset/v1/snippet/{id}/dynamicContent/{segmentId}.json
Marketo Update Snippet Dynamic Content
updateDynamicContentUsingPOST 2 params body → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are UpdateLandingPageContentRequest (17 properties), UpdateLandingPageDynamicContentRequest (17 properties), UpdateEmailComponentContentRequest (12 properties), UpdateEmailDynamicContentRequest (11 properties). Each schema is shown below with its type and property counts.

ResponseOfEmailDynamicContentResponse
object
5 properties
UpdateSnippetDynamicContentRequest
object
2 properties
EmailDynamicContentItem
object
5 properties
SegmentContent
object
6 properties 4 required
UpdateEmailComponentContentRequest
object
12 properties 2 required
UpdateLandingPageContentRequest
object
17 properties 1 required
EmailModuleResponse
object
1 property 1 required
LandingPageDynamicContentResponse
object
5 properties
ResponseOfEmailModuleResponse
object
5 properties
ResponseOfEmailTemplateContentResponse
object
5 properties
ResponseOfLandingPageDynamicContentResponse
object
5 properties
ResponseOfIdResponse
object
5 properties
Error
object
2 properties 2 required
EmailTemplateContentResponse
object
3 properties 3 required
EmailDynamicContentResponse
object
5 properties
IdResponse
object
1 property 1 required
UpdateEmailDynamicContentRequest
object
11 properties 2 required
UpdateLandingPageDynamicContentRequest
object
17 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

marketo-content-api-openapi.yml Raw ↑

Other APIs Marketo publishes across the network.

Marketo Approve API
AE Profile APIs.io
Marketo Assets API
AE Profile APIs.io
Marketo Campaigns API
AE Profile APIs.io
Marketo Cc API
AE Profile APIs.io
Marketo Channel API
AE Profile APIs.io
Marketo Channels API
AE Profile APIs.io
Marketo Clone.json API
AE Profile APIs.io
Marketo Content.json API
AE Profile APIs.io
Marketo Delete.json API
AE Profile APIs.io
Marketo Discard API
AE Profile APIs.io
Marketo Dynamic API
AE Profile APIs.io
Marketo Email API
AE Profile APIs.io
#Content
← Back to M APIs
API Details
ID
marketo:marketo-content-api
Base URL
https://{munchkinId}.mktorest.com/rest
Docs
https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api
Provider
Marketo
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=marketo-content-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/marketo-content-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 Marketo Content 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.