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
Virtual Incision

Virtual Incision Taxonomy API

Post categories, tags and the taxonomy registry behind the newsroom.

Documentation Provider Profile APIs.io OpenAPI GitHub

Virtual Incision Taxonomy API is one of 10 APIs that Virtual Incision publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Taxonomy and Content. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 14 operations across 6 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version wp/v2.

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

14 operations 6 paths 4 schemas 2 DELETE6 GET2 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://virtualincision.com/wp-json
Authentication
HTTP Basic, API Key
Contact
Virtual Incision
Resource Areas
1

Authentication & Security 2

Virtual Incision Taxonomy API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (applicationPassword). An API key is passed in the header as X-WP-Nonce (cookieNonce). By default, every request must be authenticated, though some operations may also be called without credentials.

  • applicationPassword — WordPress Application Passwords over HTTP Basic. Issued at https://virtualincision.com/wp-admin/authorize-application.php (advertised by the wp-json root authe…
  • cookieNonce — Logged-in WordPress cookie plus an X-WP-Nonce header — first-party browser context only.

Paths & Operations 14

Across 6 paths, the API surfaces 14 operations — 2 DELETE, 6 GET, 2 PATCH, 4 POST. Each is listed below with its method, path, parameters, and response codes.

Taxonomy 14

Post categories, tags and the taxonomy registry.

GET
/wp/v2/categories
GET /wp/v2/categories
getCategories 12 params → 200400401404
POST
/wp/v2/categories
POST /wp/v2/categories
createCategories body → 200400401404
GET
/wp/v2/categories/{id}
GET /wp/v2/categories/{id}
getCategoriesById 2 params → 200400401404
POST
/wp/v2/categories/{id}
POST /wp/v2/categories/{id}
createCategoriesById 1 param body → 200400401404
PATCH
/wp/v2/categories/{id}
PATCH /wp/v2/categories/{id}
updateCategoriesById 1 param body → 200400401404
DELETE
/wp/v2/categories/{id}
DELETE /wp/v2/categories/{id}
deleteCategoriesById 2 params → 200400401404
GET
/wp/v2/tags
GET /wp/v2/tags
getTags 12 params → 200400401404
POST
/wp/v2/tags
POST /wp/v2/tags
createTags body → 200400401404
GET
/wp/v2/tags/{id}
GET /wp/v2/tags/{id}
getTagsById 2 params → 200400401404
POST
/wp/v2/tags/{id}
POST /wp/v2/tags/{id}
createTagsById 1 param body → 200400401404
PATCH
/wp/v2/tags/{id}
PATCH /wp/v2/tags/{id}
updateTagsById 1 param body → 200400401404
DELETE
/wp/v2/tags/{id}
DELETE /wp/v2/tags/{id}
deleteTagsById 2 params → 200400401404
GET
/wp/v2/taxonomies
GET /wp/v2/taxonomies
getTaxonomies 2 params → 200400401404
GET
/wp/v2/taxonomies/{taxonomy}
GET /wp/v2/taxonomies/{taxonomy}
getTaxonomiesByTaxonomy 2 params → 200400401404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Taxonomies (11 properties), Categories (10 properties), Tags (8 properties), WPError (3 properties). Each schema is shown below with its type and property counts.

WPError
object
The WordPress REST API error envelope, returned on every 4xx/5xx.
3 properties 3 required
Categories
object
10 properties
Tags
object
8 properties
Taxonomies
object
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

virtual-incision-taxonomy-api-openapi.yml Raw ↑

Other APIs Virtual Incision publishes across the network.

Virtual Incision News Posts API
AE Profile APIs.io
Virtual Incision Pages API
AE Profile APIs.io
Virtual Incision Media API
AE Profile APIs.io
Virtual Incision Events API
AE Profile APIs.io
Virtual Incision Careers API
AE Profile APIs.io
Virtual Incision People API
AE Profile APIs.io
Virtual Incision Search API
AE Profile APIs.io
Virtual Incision Discovery API
AE Profile APIs.io
Virtual Incision MCP Server (WordPress MCP Adapter)
AE Profile APIs.io
#Taxonomy#Content
← Back to V APIs
API Details
ID
virtual-incision:virtual-incision-taxonomy-api
Base URL
https://virtualincision.com/wp-json
Docs
https://virtualincision.com/news/
Provider
Virtual Incision
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=virtual-incision-taxonomy-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/virtual-incision-taxonomy-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 Virtual Incision Taxonomy 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.