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

Virtual Incision Events API

The `event` custom post type and `event-type` taxonomy — conferences and clinical events.

Virtual Incision Events 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 Events and Content. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 12 operations across 4 paths, and defines 3 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.

12 operations 4 paths 3 schemas 2 DELETE4 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
Resource Areas
1

Authentication & Security 2

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

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

Events 12

The event custom post type and its event-type taxonomy — conferences and clinical events Virtual Incision attends.

GET
/wp/v2/event
GET /wp/v2/event
getEvent 20 params → 200400401404
POST
/wp/v2/event
POST /wp/v2/event
createEvent body → 200400401404
GET
/wp/v2/event/{id}
GET /wp/v2/event/{id}
getEventById 3 params → 200400401404
POST
/wp/v2/event/{id}
POST /wp/v2/event/{id}
createEventById 1 param body → 200400401404
PATCH
/wp/v2/event/{id}
PATCH /wp/v2/event/{id}
updateEventById 1 param body → 200400401404
DELETE
/wp/v2/event/{id}
DELETE /wp/v2/event/{id}
deleteEventById 2 params → 200400401404
GET
/wp/v2/event-type
GET /wp/v2/event-type
getEventType 12 params → 200400401404
POST
/wp/v2/event-type
POST /wp/v2/event-type
createEventType body → 200400401404
GET
/wp/v2/event-type/{id}
GET /wp/v2/event-type/{id}
getEventTypeById 2 params → 200400401404
POST
/wp/v2/event-type/{id}
POST /wp/v2/event-type/{id}
createEventTypeById 1 param body → 200400401404
PATCH
/wp/v2/event-type/{id}
PATCH /wp/v2/event-type/{id}
updateEventTypeById 1 param body → 200400401404
DELETE
/wp/v2/event-type/{id}
DELETE /wp/v2/event-type/{id}
deleteEventTypeById 2 params → 200400401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Event (20 properties), EventType (10 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
Event
object
20 properties
EventType
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Virtual Incision publishes across the network.

Virtual Incision News Posts API
Virtual Incision Pages API
Virtual Incision Media API
Virtual Incision Careers API
Virtual Incision Taxonomy API
Virtual Incision People API
Virtual Incision Search API
Virtual Incision Discovery API
Virtual Incision MCP Server (WordPress MCP Adapter)
Where this information came from

This is an independent, third-party profile of Virtual Incision Events 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.