CaaMTech Wp Block Editor/v1 API
The wp-block-editor/v1 API from CaaMTech — 4 operation(s) for wp-block-editor/v1.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/caamtech-wp-block-editor-v1-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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: CaaMTech WordPress REST Wp Block Editor/v1 API
version: wp/v2
summary: The public WordPress REST API served by caam.tech.
description: 'Machine-readable description of the REST API that caam.tech serves at /wp-json/. CaaMTech publishes no developer program and no product API; this is the standard WordPress REST API exposed by the company web site, which does make the company''s published research updates, pages, categories and media programmatically readable without credentials.
PROVENANCE: this document was DERIVED by API Evangelist from the discovery document the site itself publishes at https://caam.tech/wp-json/ (saved verbatim alongside as caamtech-wordpress-rest-routes-original.json). Every path, method, parameter name, type, enum and default below is copied from that document. CaaMTech did not author or publish this OpenAPI. Response schemas are not described in the WordPress discovery document and are therefore left open rather than invented.'
x-provenance:
method: derived
source: https://caam.tech/wp-json/
derived_from: openapi/caamtech-wordpress-rest-routes-original.json
derived_by: API Evangelist enrichment pipeline
generated: '2026-08-08'
provider_authored: false
servers:
- url: https://caam.tech/wp-json
description: WordPress REST API root on caam.tech
tags:
- name: wp-block-editor/v1
paths:
/wp-block-editor/v1:
get:
operationId: get_wp_block_editor_v1
summary: GET /wp-block-editor/v1
tags:
- wp-block-editor/v1
responses:
'200':
description: Successful response
content:
application/json:
schema: {}
'401':
description: Authentication required
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'404':
description: No route was found matching the URL and request method
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
parameters:
- name: namespace
in: query
required: false
schema:
default: wp-block-editor/v1
- name: context
in: query
required: false
schema:
default: view
/wp-block-editor/v1/url-details:
get:
operationId: get_wp_block_editor_v1_url_details
summary: GET /wp-block-editor/v1/url-details
tags:
- wp-block-editor/v1
responses:
'200':
description: Successful response
content:
application/json:
schema: {}
'401':
description: Authentication required
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'404':
description: No route was found matching the URL and request method
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
parameters:
- name: url
in: query
required: true
schema:
type: string
format: uri
description: The URL to process.
/wp-block-editor/v1/export:
get:
operationId: get_wp_block_editor_v1_export
summary: GET /wp-block-editor/v1/export
tags:
- wp-block-editor/v1
responses:
'200':
description: Successful response
content:
application/json:
schema: {}
'401':
description: Authentication required
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'404':
description: No route was found matching the URL and request method
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
/wp-block-editor/v1/navigation-fallback:
get:
operationId: get_wp_block_editor_v1_navigation_fallback
summary: GET /wp-block-editor/v1/navigation-fallback
tags:
- wp-block-editor/v1
responses:
'200':
description: Successful response
content:
application/json:
schema: {}
'401':
description: Authentication required
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
'404':
description: No route was found matching the URL and request method
content:
application/json:
schema:
$ref: '#/components/schemas/WPRestError'
components:
schemas:
WPRestError:
type: object
description: The WordPress REST API error envelope, observed live on this host.
properties:
code:
type: string
examples:
- rest_forbidden
- rest_no_route
message:
type: string
data:
type: object
properties:
status:
type: integer
securitySchemes:
applicationPassword:
type: http
scheme: basic
description: WordPress Application Passwords (HTTP Basic). The site advertises the authorization endpoint at https://caam.tech/wp-admin/authorize-application.php
cookieAuth:
type: apiKey
in: cookie
name: wordpress_logged_in
description: WordPress logged-in cookie plus an X-WP-Nonce header (first-party only).