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 Reports & Escalations API

The Reports & Escalations API from Vanilla Forums — 14 operation(s) for reports & escalations.

Vanilla Forums Reports & Escalations 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 Reports & Escalations. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 20 operations across 14 paths, and defines 14 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.

20 operations 14 paths 14 schemas 1 DELETE10 GET4 PATCH4 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 20

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

Reports & Escalations 20
POST
/escalations
Create an Escalation
body → 201
GET
/escalations
Get a list of escalations
20 params → 200
GET
/escalations/:escalationID
Get an escalation
2 params → 200
PATCH
/escalations/:escalationID
Update an escalation
1 param body → 200
GET
/escalations/log
Get a list of escalation Logs
12 params → 200
GET
/escalations/log/:escalationLogID
Get an escalation Log
3 params → 200
GET
/escalations/lookup-assignee
Search for users that could be assigned to an escalation by full or partial name matching.
5 params → 200
GET
/report-reasons
Get a list of report reasons for the current sessioned user. community.manage permission grants permission to all reasons.
2 params → 200
POST
/report-reasons
Create a report reason
body → 201409
GET
/report-reasons/:reportReasonID
Get a report reason if you have permission for it.
3 params → 200404
PATCH
/report-reasons/:reportReasonID
Update a report reason
1 param body → 201
DELETE
/report-reasons/:reportReasonID
Delete a report reason. If the report has already been used, the reason will be marked as deleted but still exist in the underyling system for usage when viewing existing reports.
1 param → 204
PUT
/report-reasons/sorts
Update the sort order of report reasons
body → 204
POST
/reports
Create a report
body → 201
GET
/reports
Get a list of reports
18 params → 200
GET
/reports/:reportID
Get a report
2 params → 200
PATCH
/reports/:reportID/approve-record
Approve a pending or removed post that was premoderated.
1 param body → 200
POST
/reports/:reportID/dismiss
Dismiss a user's report.
1 param → 204
PATCH
/reports/:reportID/reject-record
Reject a pending or live post that was premoderated and ensure it is deleted.
1 param → 200
GET
/reports/automation
List of Posts that where reported set number of times.
7 params → 200

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Report (31 properties), Escalation (27 properties), EscalationLog (13 properties), Appeal (13 properties). Each schema is shown below with its type and property counts.

ReportInsert
object
7 properties 5 required
Report
object
31 properties 19 required
ReportReason
object
12 properties 7 required
EscalationLog
object
13 properties 6 required
ReportReasonFragment
object
6 properties 5 required
Appeal
object
13 properties 9 required
UserFragment
Escalation
object
27 properties 17 required
ReportCounter
object
8 properties 8 required
ReportReasonPost
object
5 properties 4 required
Format
string
The format of the body used to convert it to HTML.
EscalationInsert
object
12 properties 3 required
RangeExpression
string
Specify a range or CSV of values.
EscalationPatch
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vanilla-forums-reports-escalations-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 Reports & Escalations 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.