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

Merge subpackage_comments API

The subpackage_comments API from Merge — 3 operation(s) for subpackage_comments.

Merge subpackage_comments API is one of 118 APIs that Merge publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 21 JSON Schema definitions.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, a support channel, and 21 JSON Schemas.

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

Requests are made against 3 base URLs: https://api.merge.dev/api, https://api-eu.merge.dev/api, https://api-ap.merge.dev/api.

4 operations 3 paths 16 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.merge.dev/api/hris/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Merge subpackage_comments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (tokenAuth).

  • tokenAuth — Token-based authentication with required prefix "Bearer"

Paths & Operations 4

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

subpackage_comments 4
GET
/ticketing/v1/comments
List
list 15 params → 200
POST
/ticketing/v1/comments
Create
create 4 params body → 201
GET
/ticketing/v1/comments/{id}
Retrieve
retrieve 6 params → 200
GET
/ticketing/v1/comments/meta/post
Meta Post Retrieve
meta-post-retrieve 2 params → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Comment (14 properties), CommentRequest (8 properties), ErrorValidationProblem (7 properties), WarningValidationProblem (7 properties). Each schema is shown below with its type and property counts.

DebugModelLogSummary
object
3 properties 3 required
Comment
object
The Comment Object Description The Comment object is used to represent a comment on a ticket. Usage Example TODO
14 properties
CommentFieldMappings
object
2 properties
CommentsGetParametersExpandSchemaItems
string
CommentsIdGetParametersExpandSchemaItems
string
CommentResponse
object
4 properties 3 required
CommentEndpointRequest
object
1 property 1 required
DebugModeLog
object
3 properties 3 required
RemoteData
object
The RemoteData Object Description The RemoteData object is used to represent the full data pulled from the third-party API for an object. Usage Example TODO
2 properties 1 required
ValidationProblemSource
object
1 property 1 required
CommentRequest
object
The Comment Object Description The Comment object is used to represent a comment on a ticket. Usage Example TODO
8 properties
LinkedAccountStatus
object
2 properties 2 required
PaginatedCommentList
object
3 properties
WarningValidationProblem
object
7 properties 3 required
ErrorValidationProblem
object
7 properties 3 required
MetaResponse
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-subpackage-comments-api-openapi.yml Raw ↑

Other APIs Merge publishes across the network.

Merge Default API
Merge subpackage_accessKeys API
Merge subpackage_accountDetails API
Merge subpackage_accountingPeriods API
Merge subpackage_accounts API
Merge subpackage_accountToken API
Merge subpackage_activities API
Merge subpackage_addresses API
Merge subpackage_applicationCredentials API
Merge subpackage_applications API
Merge subpackage_articles API
Where this information came from

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