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 Discussions API

The Discussions API from Vanilla Forums — 28 operation(s) for discussions.

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

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

This API exposes 34 operations across 28 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

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

34 operations 28 paths 23 schemas 4 DELETE9 GET7 PATCH7 POST7 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Paths & Operations 34

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

Discussions 34
DELETE
/comments/list
Delete a list of comments
deleteCommentsList body → 202204403408
GET
/discussions
List discussions
getDiscussions 37 params → 200
POST
/discussions
Add a discussion
postDiscussions body → 201202
GET
/discussions/bookmarked
Get a list of the current user's bookmarked discussions
getDiscussionsBookmarked 4 params → 200
PATCH
/discussions/close
Close/open a list of discussions
patchDiscussionsClose body → 200202403408
POST
/discussions/idea
Add an idea
postDiscussionsIdea body → 201202
DELETE
/discussions/list
Delete a list of discussions
deleteDiscussionsList body → 202204403408
PATCH
/discussions/merge
Merge discussions
patchDiscussionsMerge body → 200202403408
PATCH
/discussions/move
Move a list of discussions
patchDiscussionsMove body → 200202403408
GET
/discussions/muted
Get a list of the current user's muted discussions
getDiscussionsMuted 4 params → 200
POST
/discussions/poll
Add a poll
postDiscussionsPoll body → 201202
POST
/discussions/question
Add a discussion
postDiscussionsQuestion body → 201202
POST
/discussions/resolve-bulk
Mark all discussions you can triage as resolved
postDiscussionsResolveBulk → 201
GET
/discussions/search
Search discussions
getDiscussionsSearch 7 params → 200
POST
/discussions/split
Split comments out into a discussion
postDiscussionsSplit body → 200202403408
DELETE
/discussions/{id}
Delete a discussion
deleteDiscussionsById 2 params → 202204403408
GET
/discussions/{id}
Get a discussion
getDiscussionsById 3 params → 200
PATCH
/discussions/{id}
Update a discussion
patchDiscussionsById 1 param body → 200202
PUT
/discussions/{id}/bookmark
Bookmark a discussion
putDiscussionsByIdBookmark 1 param body → 200
PATCH
/discussions/{id}/bump
Bump a discussion higher in the list by updating the DateLastComment field
patchDiscussionsByIdBump 1 param → 200404400
PUT
/discussions/{id}/canonical-url
Set custom canonical url for a discussion
putDiscussionsByIdCanonicalUrl 1 param body → 200404400
DELETE
/discussions/{id}/canonical-url
Remove custom canonical url for a discussion
deleteDiscussionsByIdCanonicalUrl 1 param → 204404
PUT
/discussions/{id}/dismiss
Dismiss an announcement
putDiscussionsByIdDismiss 1 param body → 200
GET
/discussions/{id}/edit
Get a discussion for editing
getDiscussionsByIdEdit 3 params → 200
PATCH
/discussions/{id}/idea
Update idea metadata on a discussion
patchDiscussionsByIdIdea 1 param body → 200
PUT
/discussions/{id}/mute
Replace discussions by id mute
putDiscussionsByIdMute 1 param body → 200
GET
/discussions/{id}/poll
Get a poll
getDiscussionsByIdPoll 2 params → 200
PATCH
/discussions/{id}/poll
Update a poll
patchDiscussionsByIdPoll 1 param body → 200
GET
/discussions/{id}/quote
Get discussions by id quote
getDiscussionsByIdQuote 3 params → 200
PUT
/discussions/{id}/status
Change a discussion status
putDiscussionsByIdStatus 1 param body → 200
GET
/discussions/{id}/status-log
List of status changes for a discussion
getDiscussionsByIdStatusLog 4 params → 200
PUT
/discussions/{id}/tags
Set the tags on a discussion
putDiscussionsByIdTags 1 param body → 200401404
POST
/discussions/{id}/tags
Add tags to a discussion
postDiscussionsByIdTags 1 param body → 200401404
PUT
/discussions/{id}/type
Change a discussion type
putDiscussionsByIdType 1 param body → 200

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are Discussion (41 properties), DiscussionPost (13 properties), DiscussionGetEdit (12 properties), DiscussionPatch (11 properties). Each schema is shown below with its type and property counts.

DiscussionPatch
object
11 properties
DiscussionPost
object
13 properties 3 required
LongRunnerProgress
object
Progress of the task.
4 properties 3 required
Image
object
An image, pulled from content.
3 properties
PostMeta
object
Custom post fields. This is an object keyed by postFieldID.
DiscussionPermissions
object
Permissions for the current user related to discussions. Applied when expanded..
SrcSet
object
An image's srcset for various sizes.
4 properties
PostFragment
object
8 properties 4 required
TagReference
object
A reference to a tag for assignment to other items.
2 properties
DiscussionGetEdit
object
12 properties 9 required
Discussion
object
41 properties 18 required
RangeExpression
string
Specify a range or CSV of values.
CategoryFragment
object
3 properties 3 required
ReportReasonFragment
object
6 properties 5 required
ReportMeta
object
7 properties
Format
string
The format of the body used to convert it to HTML.
StatusLog
object
6 properties 5 required
LongRunnerResult
object
Endpoints will return this if they may time out and require the client to progress the task with additional requests.
2 properties 2 required
PostPremoderation
object
4 properties
TagFragment
object
A tag that can be applied to content.
4 properties 3 required
StatusFragment
object
Describes a status currently applied to a discussion. Expandable with status and status.log expands.
7 properties 4 required
UserFragment
TrackingSlipData
object
Represents a scheduled server-side job.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vanilla-forums-discussions-api-openapi.yml Raw ↑

Other APIs Vanilla Forums publishes across the network.

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
Vanilla Forums Comments API
Where this information came from

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