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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Merge

Merge subpackage_tickets API

The subpackage_tickets API from Merge — 7 operation(s) for subpackage_tickets.

Documentation Provider Profile APIs.io OpenAPI GitHub

Merge subpackage_tickets 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 9 operations across 7 paths, and defines 44 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.

9 operations 7 paths 44 schemas 7 GET1 PATCH1 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_tickets API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (tokenAuth).

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

Paths & Operations 9

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

subpackage_tickets 9
GET
/ticketing/v1/tickets
List
list 38 params → 200
POST
/ticketing/v1/tickets
Create
create 4 params body → 201
GET
/ticketing/v1/tickets/{id}
Retrieve
retrieve 9 params → 200
PATCH
/ticketing/v1/tickets/{id}
Partial Update
partial-update 5 params body → 200
GET
/ticketing/v1/tickets/{ticket_id}/viewers
Viewers List
viewers-list 9 params → 200
GET
/ticketing/v1/tickets/live-search
Live Search List
live-search-list 15 params → 200
GET
/ticketing/v1/tickets/meta/patch/{id}
Meta Patch Retrieve
meta-patch-retrieve 3 params → 200
GET
/ticketing/v1/tickets/meta/post
Meta Post Retrieve
meta-post-retrieve 4 params → 200
GET
/ticketing/v1/tickets/remote-field-classes
Remote Field Classes List
remote-field-classes-list 10 params → 200

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are Ticket (30 properties), TicketRequest (22 properties), PatchedTicketRequest (21 properties), Permission (12 properties). Each schema is shown below with its type and property counts.

PatchedTicketRequest
object
The Ticket Object Description The Ticket object is used to represent a ticket, issue, task or case. Usage Example TODO
21 properties
ValidationProblemSource
object
1 property 1 required
WarningValidationProblem
object
7 properties 3 required
TicketsIdGetParametersRemoteFields
string
ItemTypeEnum
string
TicketsTicketIdViewersGetParametersExpandSchemaItems
string
TicketsLiveSearchGetParametersRemoteFields
string
DebugModelLogSummary
object
3 properties 3 required
PatchedTicketEndpointRequest
object
1 property 1 required
TicketsGetParametersPriority
string
PermissionFieldMappings
object
2 properties
PaginatedTicketList
object
3 properties
LinkedAccountStatus
object
2 properties 2 required
Viewer
object
The Viewer Object Description The Viewer object is used to represent a User or Team within a company. Usage Example TODO
6 properties
FieldFormatEnum
string
TicketsLiveSearchGetParametersShowEnumOrigins
string
Permission
object
The Permission Object Description The Permission object is used to represent permissions that can be applied to users, roles, teams, collections, and tickets.…
12 properties
ItemFormatEnum
string
Ticket
object
The Ticket Object Description The Ticket object is used to represent a ticket, issue, task or case. Usage Example TODO
30 properties
TicketsGetParametersShowEnumOrigins
string
MetaResponse
object
5 properties 3 required
RemoteField
object
2 properties 1 required
TicketsGetParametersRemoteFields
string
TicketsIdGetParametersShowEnumOrigins
string
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
TicketFieldMappings
object
2 properties
TicketsIdGetParametersExpandSchemaItems
string
ActionsEnum
string
RemoteFieldClass
object
11 properties
ItemSchema
object
3 properties
EffectEnum
string
PriorityEnum
string
PaginatedRemoteFieldClassList
object
3 properties
TicketStatusEnum
string
DebugModeLog
object
3 properties 3 required
TicketAccessLevelEnum
string
TicketResponse
object
4 properties 3 required
PaginatedViewerList
object
3 properties
TicketEndpointRequest
object
1 property 1 required
FieldTypeEnum
string
TicketsGetParametersExpandSchemaItems
string
TicketRequest
object
The Ticket Object Description The Ticket object is used to represent a ticket, issue, task or case. Usage Example TODO
22 properties
ErrorValidationProblem
object
7 properties 3 required
RemoteFieldRequest
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Merge publishes across the network.

Merge
AE Profile APIs.io
Merge Default API
AE Profile APIs.io
Merge subpackage_accessKeys API
AE Profile APIs.io
Merge subpackage_accountDetails API
AE Profile APIs.io
Merge subpackage_accountingPeriods API
AE Profile APIs.io
Merge subpackage_accounts API
AE Profile APIs.io
Merge subpackage_accountToken API
AE Profile APIs.io
Merge subpackage_activities API
AE Profile APIs.io
Merge subpackage_addresses API
AE Profile APIs.io
Merge subpackage_applicationCredentials API
AE Profile APIs.io
Merge subpackage_applications API
AE Profile APIs.io
Merge subpackage_articles API
AE Profile APIs.io
← Back to M APIs
API Details
ID
merge:merge-subpackage-tickets-api
Base URL
https://api.merge.dev/api/hris/v1
Docs
https://www.merge.dev/
Provider
Merge
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=merge-subpackage-tickets-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/merge-subpackage-tickets-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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