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

Lemmy Comment API

Creating and managing comments

Lemmy Comment API is one of 14 APIs that Lemmy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Comment. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a GitHub repository, rate-limit docs, and 3 JSON Schemas.

This API exposes 8 operations across 5 paths, and defines 8 schemas. It is described by OpenAPI 3.1.0, at version 4.0.0.

Requests are made against 2 base URLs: https://lemmy.world/api/v4, https://{instance}/api/v4.

8 operations 5 paths 8 schemas 1 DELETE2 GET3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
4.0.0
Base URL
https://lemmy.world/api/v4
Authentication
HTTP Bearer
License
Resource Areas
1

Authentication & Security 1

Lemmy Comment API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 8

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

Comment 8

Creating and managing comments

GET
/comment
Get a comment
getComment 1 param → 200
POST
/comment
Create a comment
createComment body → 200
PUT
/comment
Edit a comment
editComment body → 200
DELETE
/comment
Delete a comment
deleteComment body → 200
GET
/comment/list
List comments
listComments 9 params → 200
POST
/comment/like
Vote on a comment
likeComment body → 200
PUT
/comment/save
Save or unsave a comment
saveComment body → 200
POST
/comment/report
Report a comment
createCommentReport body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed is CommentResponse (2 properties). Each schema is shown below with its type and property counts.

CommunityId
integer
Unique identifier for a community
ListingType
string
LanguageId
integer
Unique identifier for a language
PersonId
integer
Unique identifier for a person/user
CommentResponse
object
2 properties
CommentId
integer
Unique identifier for a comment
CommentSortType
string
PostId
integer
Unique identifier for a post

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lemmy-comment-api-openapi.yml Raw ↑

Other APIs Lemmy publishes across the network.

Lemmy Account API
Lemmy Admin API
Lemmy Authentication API
Lemmy Community API
Lemmy Federation API
Lemmy Images API
Lemmy Notifications API
Lemmy Person API
Lemmy Post API
Lemmy Private Messages API
Lemmy Reports API
Lemmy Search API
Where this information came from

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