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

Cellarity Comments API

The Comments API from Cellarity — 2 operation(s) for comments.

Cellarity Comments API is one of 16 APIs that Cellarity publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Comments. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

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

7 operations 2 paths 1 schemas 1 DELETE2 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://cellarity.com/wp-json/wp/v2
Authentication
HTTP Basic
Contact
Resource Areas
1

Authentication & Security 1

Cellarity Comments API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (applicationPassword).

  • applicationPassword — WordPress Application Passwords, advertised by the site at https://cellarity.com/wp-json/ under authentication.application-passwords; authorization endpoint ht…

Paths & Operations 7

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

Comments 7
GET
/wp/v2/comments
GET /wp/v2/comments
listComments 20 params → 200400401403404
POST
/wp/v2/comments
POST /wp/v2/comments
createComment body → 200400401403404
GET
/wp/v2/comments/{id}
GET /wp/v2/comments/{id}
getComment 3 params → 200400401403404
POST
/wp/v2/comments/{id}
POST /wp/v2/comments/{id}
createCommentByComments 1 param body → 200400401403404
PUT
/wp/v2/comments/{id}
PUT /wp/v2/comments/{id}
replaceComment 1 param body → 200400401403404
PATCH
/wp/v2/comments/{id}
PATCH /wp/v2/comments/{id}
updateComment 1 param body → 200400401403404
DELETE
/wp/v2/comments/{id}
DELETE /wp/v2/comments/{id}
deleteComment 3 params → 200400401403404

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 API error envelope returned on every 4xx/5xx.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cellarity-comments-api-openapi.yml Raw ↑

Other APIs Cellarity publishes across the network.

Cellarity Case Studies API
Cellarity Discovery API
Cellarity Events API
Cellarity Media API
Cellarity News API
Cellarity Pages API
Cellarity People API
Cellarity Pipeline API
Cellarity Posts API
Cellarity Projects API
Cellarity Search API
Cellarity Settings API
Where this information came from

This is an independent, third-party profile of Cellarity Comments 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.