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

SEDNA Comment API API

The Comment API API from SEDNA — 1 operation(s) for comment api.

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

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

This API exposes 1 operation across 1 path, and defines 9 schemas. It is described by OpenAPI 3.0.1, at version 2019-01-01.

Requests are made against a single base URL, https://{tenant}.sednanetwork.com/platform.

1 operations 1 paths 9 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2019-01-01
Base URL
https://example.sednanetwork.com/platform
Authentication
HTTP Basic, OAuth 2.0
Contact
Terms of Service
Resource Areas
1

Authentication & Security 2

SEDNA Comment API API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (Basic). It supports OAuth 2.0 (OAuth) using the clientCredentials flow, exposing 53 scopes. By default, every request must be authenticated.

  • Basic — The basic auth scheme only requires the API-Specific username/password to be set.
  • OAuth — This API prefers OAuth 2 with client credentials flow. You can create your credentials in the Api Credential Management page .

Paths & Operations 1

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

Comment API 1
GET
/2019-01-01/comment
Get comments across all messages. Required API Permissions: COMMENTREAD
getComments 7 params → default

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are CommentReadResource (4 properties), MessageRelData (2 properties), MessageRelLinks (2 properties), UserRelData (2 properties). Each schema is shown below with its type and property counts.

CommentAttributes
object
2 properties 2 required
CommentReadResource
object
4 properties 2 required
MessageRelData
object
2 properties
CommentRelationships
object
2 properties
MessageRelLinks
object
2 properties
UserRelToOne
object
1 property
MessageRelToOne
object
2 properties
UserRelData
object
2 properties
CommentCollection
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sedna-comment-api-api-openapi.yml Raw ↑

Other APIs SEDNA publishes across the network.

SEDNA Authentication API
SEDNA Category Tag API API
SEDNA Company API API
SEDNA Contact API API
SEDNA Document API API
SEDNA Download API API
SEDNA Event API API
SEDNA Job Reference API API
SEDNA Keyword API API
SEDNA Message API API
SEDNA Saved Search API API
SEDNA Team API API
Where this information came from

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