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

DEV Community Comments API

Endpoints for retrieving comments on articles and podcast episodes, including threaded conversation views.

This API exposes 4 operations across 4 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://dev.to/api, https://dev.to.

4 operations 4 paths 4 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://dev.to/api
Authentication
API Key, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 3

DEV Community Comments API declares 3 security schemes for authenticating requests. An API key is passed in the header as api-key (apiKey). An API key is passed in the header as api-key (api-key). It accepts HTTP bearer tokens (JWT) (bearer_auth).

  • apiKey — API key obtained from the DEV.to settings page. Pass in the api-key header for authenticated requests.
  • api-key — API Key authentication. Authentication for some endpoints, like write operations on the Articles API require a DEV API key. All authenticated endpoints are COR…
  • bearer_auth — Short-lived RS256 RFC 9068 access token issued by the configured delegation service and verified against its configured JWKS. The issuer authorizes the client…

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

Comments 4

Endpoints for retrieving comments on articles and podcast episodes, including threaded conversation views.

GET
/comments
Comments
getCommentsByArticleId 2 params → 200
GET
/comments/{id}
Comment by id
getCommentById 1 param → 200404
GET
/api/comments
Comments
getApiComments 5 params → 200404
GET
/api/comments/{id}
Comment by id
getApiCommentsById 1 param → 200404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are User (11 properties), Comment_2 (6 properties), Comment (6 properties), Comment_3 (4 properties). Each schema is shown below with its type and property counts.

User
object
A user account on the DEV platform.
11 properties
Comment
object
A comment on an article or podcast episode, with nested children for threaded conversations.
6 properties
Comment_2
object
A Comment on an Article or Podcast Episode
6 properties
Comment_3
object
A Comment on an Article or Podcast Episode
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dev-to-comments-api-openapi.yml Raw ↑
Where this information came from

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