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

Vanilla Forums Discussion Statuses API

The Discussion Statuses API from Vanilla Forums — 3 operation(s) for discussion statuses.

Vanilla Forums Discussion Statuses API is one of 58 APIs that Vanilla Forums publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Discussion Statuses. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 2.0.

Requests are made against a single base URL, https://open.vanillaforums.com/api/v2.

6 operations 3 paths 6 schemas 1 DELETE2 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0
Base URL
https://open.vanillaforums.com/api/v2
Resource Areas
1

Paths & Operations 6

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

Discussion Statuses 6
GET
/discussions/statuses
Get known discussion statuses.
5 params → 200400
POST
/discussions/statuses
Create a new discussion status.
body → 201400403404
GET
/discussions/statuses/{id}
Get a discussion status by its ID.
2 params → 200404
PATCH
/discussions/statuses/{id}
Update a discussion status.
1 param body → 200400403404
DELETE
/discussions/statuses/{id}
Delete a discussion status.
1 param → 204400403404
PUT
/discussions/toggle-scoped-statuses
Toggle scoped statuses on or off.
body → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are RecordStatus (10 properties), RecordStatusPost (7 properties), RecordStatusPatch (7 properties), Scope (3 properties). Each schema is shown below with its type and property counts.

RecordStatus
object
10 properties
RecordStatusPatch
object
7 properties
RecordStatusPost
object
7 properties 1 required
Scope
object
Scoping information for a record.
3 properties
ScopeType
string
Scope type for a record.
BasicError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vanilla-forums-discussion-statuses-api-openapi.yml Raw ↑

Other APIs Vanilla Forums publishes across the network.

Vanilla Forums Addons API
Vanilla Forums AI Processing Preferences API
Vanilla Forums AI Settings API
Vanilla Forums Analytics API
Vanilla Forums Appeals API
Vanilla Forums Assets API
Vanilla Forums Audit Logs API
Vanilla Forums Authenticators API
Vanilla Forums Automation Rules API
Vanilla Forums Calls API
Vanilla Forums Categories API
Vanilla Forums Collections API
Where this information came from

This is an independent, third-party profile of Vanilla Forums Discussion Statuses 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.