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_passthrough API

The subpackage_passthrough API from Merge — 8 operation(s) for subpackage_passthrough.

Documentation Provider Profile APIs.io OpenAPI GitHub

Merge subpackage_passthrough 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 8 operations across 8 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 7 base URLs: https://api.merge.dev/api, https://api-eu.merge.dev/api, https://api-ap.merge.dev/api, https://api.merge.dev/api/chat/v1, https://api-eu.merge.dev/api/chat/v1, https://api-ap.merge.dev/api/chat/v1, https://api-ap.merge.dev/api/knowledgebase/v1.

8 operations 8 paths 12 schemas 8 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_passthrough API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (tokenAuth).

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

Paths & Operations 8

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

subpackage_passthrough 8
POST
/accounting/v1/passthrough
Create
create 2 params body → 200
POST
/ats/v1/passthrough
Create
create 2 params body → 200
POST
/passthrough
Create
create 2 params body → 200
POST
/crm/v1/passthrough
Create
create 2 params body → 200
POST
/filestorage/v1/passthrough
Create
create 2 params body → 200
POST
/hris/v1/passthrough
Create
create 2 params body → 200
POST
/knowledgebase/v1/passthrough
Create
create 2 params body → 200
POST
/ticketing/v1/passthrough
Create
create 2 params body → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are DataPassthroughRequest (8 properties), RemoteResponse (7 properties), MultipartFormFieldRequest_2 (5 properties), MultipartFormFieldRequest (5 properties). Each schema is shown below with its type and property counts.

RequestFormatEnum
string
MultipartFormFieldRequest
object
The MultipartFormField Object Description The MultipartFormField object is used to represent fields in an HTTP request using multipart/form-data. Usage Example…
5 properties 2 required
RemoteResponse
object
The RemoteResponse Object Description The RemoteResponse object is used to represent information returned from a third-party endpoint. Usage Example View the R…
7 properties 4 required
EncodingEnum
string
ResponseTypeEnum
string
DataPassthroughRequest
object
The DataPassthrough Object Description The DataPassthrough object is used to send information to an otherwise-unsupported third-party endpoint. Usage Example C…
8 properties 2 required
MethodEnum
string
RequestFormatEnum_2
string
JSON - JSON XML - XML MULTIPART - MULTIPART
MultipartFormFieldRequest_2
object
The MultipartFormField Object Description The MultipartFormField object is used to represent fields in an HTTP request using multipart/form-data. Usage Example…
5 properties 2 required
EncodingEnum_2
string
RAW - RAW BASE64 - BASE64 GZIPBASE64 - GZIPBASE64
ResponseTypeEnum_2
string
JSON - JSON BASE64GZIP - BASE64GZIP
MethodEnum_2
string
GET - GET OPTIONS - OPTIONS HEAD - HEAD POST - POST PUT - PUT PATCH - PATCH DELETE - DELETE

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-subpackage-passthrough-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-passthrough-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-passthrough-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/merge-subpackage-passthrough-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_passthrough 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.