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
Advantage Solutions

MRKT Blog Content API (WordPress REST)

The publicly readable content API of MRKT, described by its own discovery document as "MRKT | An Advantage Solutions Publication". mrktblog.com runs WordPress on WP Engine behind Cloudflare and serves the standard REST API at /wp-json/ with 178 advertised routes, returning posts, categories, tags and media anonymously. It is the machine-readable counterpart to the RSS feed the company already publishes, and carries the retail and consumer-goods commentary Advantage Solutions produces for brands and retailers.

Documentation Provider Profile APIs.io OpenAPI GitHub

MRKT Blog Content API (WordPress REST) is one of 2 APIs that Advantage Solutions publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 55 operations across 28 paths, organized into 12 resource areas, and defines 1 schema. It is described by OpenAPI 3.1.0, at version wp/v2.

Requests are made against a single base URL, https://mrktblog.com/wp-json.

55 operations 28 paths 1 schemas 10 DELETE26 GET19 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
wp/v2
Base URL
https://mrktblog.com/wp-json
Authentication
HTTP Basic
Contact
Advantage Solutions
Resource Areas
12

Authentication & Security 1

MRKT Blog Content API (WordPress REST) declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (applicationPassword).

  • applicationPassword — WordPress Application Passwords (HTTP Basic). The discovery document advertises the authorization endpoint at https://mrktblog.com/wp-admin/authorize-applicati…

Paths & Operations 55

Across 28 paths, the API surfaces 55 operations — 10 DELETE, 26 GET, 19 POST. They span 12 resource areas, including oembed, categories, comments, media, pages, posts, search, statuses, and 4 more. Each is listed below with its method, path, parameters, and response codes.

oembed 1
GET
/oembed/1.0/embed
GET /oembed/1.0/embed
getOembed10Embed 3 params → 200401404
categories 5
GET
/wp/v2/categories
GET /wp/v2/categories
getWpV2Categories 12 params → 200401404
POST
/wp/v2/categories
POST /wp/v2/categories
createWpV2Categories body → 200401404
GET
/wp/v2/categories/{id}
GET /wp/v2/categories/{id}
getWpV2CategoriesByid 2 params → 200401404
POST
/wp/v2/categories/{id}
POST /wp/v2/categories/{id}
createWpV2CategoriesByid 1 param body → 200401404
DELETE
/wp/v2/categories/{id}
DELETE /wp/v2/categories/{id}
deleteWpV2CategoriesByid 2 params → 200401404
comments 5
GET
/wp/v2/comments
GET /wp/v2/comments
getWpV2Comments 20 params → 200401404
POST
/wp/v2/comments
POST /wp/v2/comments
createWpV2Comments body → 200401404
GET
/wp/v2/comments/{id}
GET /wp/v2/comments/{id}
getWpV2CommentsByid 3 params → 200401404
POST
/wp/v2/comments/{id}
POST /wp/v2/comments/{id}
createWpV2CommentsByid 1 param body → 200401404
DELETE
/wp/v2/comments/{id}
DELETE /wp/v2/comments/{id}
deleteWpV2CommentsByid 3 params → 200401404
media 7
GET
/wp/v2/media
GET /wp/v2/media
getWpV2Media 23 params → 200401404
POST
/wp/v2/media
POST /wp/v2/media
createWpV2Media body → 200401404
GET
/wp/v2/media/{id}
GET /wp/v2/media/{id}
getWpV2MediaByid 2 params → 200401404
POST
/wp/v2/media/{id}
POST /wp/v2/media/{id}
createWpV2MediaByid 1 param body → 200401404
DELETE
/wp/v2/media/{id}
DELETE /wp/v2/media/{id}
deleteWpV2MediaByid 2 params → 200401404
POST
/wp/v2/media/{id}/edit
POST /wp/v2/media/{id}/edit
createWpV2MediaByidEdit 1 param body → 200401404
POST
/wp/v2/media/{id}/post-process
POST /wp/v2/media/{id}/post-process
createWpV2MediaByidPostprocess 1 param body → 200401404
pages 5
GET
/wp/v2/pages
GET /wp/v2/pages
getWpV2Pages 23 params → 200401404
POST
/wp/v2/pages
POST /wp/v2/pages
createWpV2Pages body → 200401404
GET
/wp/v2/pages/{id}
GET /wp/v2/pages/{id}
getWpV2PagesByid 4 params → 200401404
POST
/wp/v2/pages/{id}
POST /wp/v2/pages/{id}
createWpV2PagesByid 1 param body → 200401404
DELETE
/wp/v2/pages/{id}
DELETE /wp/v2/pages/{id}
deleteWpV2PagesByid 2 params → 200401404
posts 5
GET
/wp/v2/posts
GET /wp/v2/posts
getWpV2Posts 27 params → 200401404
POST
/wp/v2/posts
POST /wp/v2/posts
createWpV2Posts body → 200401404
GET
/wp/v2/posts/{id}
GET /wp/v2/posts/{id}
getWpV2PostsByid 4 params → 200401404
POST
/wp/v2/posts/{id}
POST /wp/v2/posts/{id}
createWpV2PostsByid 1 param body → 200401404
DELETE
/wp/v2/posts/{id}
DELETE /wp/v2/posts/{id}
deleteWpV2PostsByid 2 params → 200401404
search 1
GET
/wp/v2/search
GET /wp/v2/search
getWpV2Search 8 params → 200401404
statuses 2
GET
/wp/v2/statuses
GET /wp/v2/statuses
getWpV2Statuses 1 param → 200401404
GET
/wp/v2/statuses/{status}
GET /wp/v2/statuses/{status}
getWpV2StatusesBystatus 2 params → 200401404
tags 5
GET
/wp/v2/tags
GET /wp/v2/tags
getWpV2Tags 12 params → 200401404
POST
/wp/v2/tags
POST /wp/v2/tags
createWpV2Tags body → 200401404
GET
/wp/v2/tags/{id}
GET /wp/v2/tags/{id}
getWpV2TagsByid 2 params → 200401404
POST
/wp/v2/tags/{id}
POST /wp/v2/tags/{id}
createWpV2TagsByid 1 param body → 200401404
DELETE
/wp/v2/tags/{id}
DELETE /wp/v2/tags/{id}
deleteWpV2TagsByid 2 params → 200401404
taxonomies 2
GET
/wp/v2/taxonomies
GET /wp/v2/taxonomies
getWpV2Taxonomies 2 params → 200401404
GET
/wp/v2/taxonomies/{taxonomy}
GET /wp/v2/taxonomies/{taxonomy}
getWpV2TaxonomiesBytaxonomy 2 params → 200401404
types 2
GET
/wp/v2/types
GET /wp/v2/types
getWpV2Types 1 param → 200401404
GET
/wp/v2/types/{type}
GET /wp/v2/types/{type}
getWpV2TypesBytype 2 params → 200401404
users 15
GET
/wp/v2/users
GET /wp/v2/users
getWpV2Users 15 params → 200401404
POST
/wp/v2/users
POST /wp/v2/users
createWpV2Users body → 200401404
GET
/wp/v2/users/me
GET /wp/v2/users/me
getWpV2UsersMe 1 param → 200401404
POST
/wp/v2/users/me
POST /wp/v2/users/me
createWpV2UsersMe body → 200401404
DELETE
/wp/v2/users/me
DELETE /wp/v2/users/me
deleteWpV2UsersMe 2 params → 200401404
GET
/wp/v2/users/{id}
GET /wp/v2/users/{id}
getWpV2UsersByid 2 params → 200401404
POST
/wp/v2/users/{id}
POST /wp/v2/users/{id}
createWpV2UsersByid 1 param body → 200401404
DELETE
/wp/v2/users/{id}
DELETE /wp/v2/users/{id}
deleteWpV2UsersByid 3 params → 200401404
GET
/wp/v2/users/{user_id})/application-passwords
GET /wp/v2/users/{userid})/application-passwords
getWpV2UsersByuseridApplicationpasswords 2 params → 200401404
POST
/wp/v2/users/{user_id})/application-passwords
POST /wp/v2/users/{userid})/application-passwords
createWpV2UsersByuseridApplicationpasswords 1 param body → 200401404
DELETE
/wp/v2/users/{user_id})/application-passwords
DELETE /wp/v2/users/{userid})/application-passwords
deleteWpV2UsersByuseridApplicationpasswords 1 param → 200401404
GET
/wp/v2/users/{user_id})/application-passwords/introspect
GET /wp/v2/users/{userid})/application-passwords/introspect
getWpV2UsersByuseridApplicationpasswordsIntrospect 2 params → 200401404
GET
/wp/v2/users/{user_id})/application-passwords/{uuid}
GET /wp/v2/users/{userid})/application-passwords/{uuid}
getWpV2UsersByuseridApplicationpasswordsByuuid 3 params → 200401404
POST
/wp/v2/users/{user_id})/application-passwords/{uuid}
POST /wp/v2/users/{userid})/application-passwords/{uuid}
createWpV2UsersByuseridApplicationpasswordsByuuid 2 params body → 200401404
DELETE
/wp/v2/users/{user_id})/application-passwords/{uuid}
DELETE /wp/v2/users/{userid})/application-passwords/{uuid}
deleteWpV2UsersByuseridApplicationpasswordsByuuid 2 params → 200401404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is WPError (3 properties). Each schema is shown below with its type and property counts.

WPError
object
The WordPress REST error envelope, observed live on this host.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

advantage-solutions-mrktblog-content-openapi.yml Raw ↑

Other APIs Advantage Solutions publishes across the network.

Advantage Solutions Corporate Content API (WordPress REST)
AE Profile APIs.io
#Content#WordPress#REST#Blog#Retail
← Back to M APIs
API Details
ID
advantage-solutions:mrktblog-content
Base URL
https://mrktblog.com/wp-json
Docs
https://mrktblog.com/
Provider
Advantage Solutions
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=mrktblog-content&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mrktblog-content"

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 MRKT Blog Content API (WordPress REST), 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.