Merge subpackage_files API
The subpackage_files API from Merge — 6 operation(s) for subpackage_files.
Merge subpackage_files 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 7 operations across 6 paths, and defines 25 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Merge subpackage_files API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (tokenAuth).
tokenAuth— Token-based authentication with required prefix "Bearer"
Paths & Operations 7
Across 6 paths, the API surfaces 7 operations — 6 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Schemas 25
The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are File (19 properties), FileRequest (12 properties), Permission (10 properties), WarningValidationProblem (7 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Merge 12
Other APIs Merge publishes across the network.
This is an independent, third-party profile of Merge subpackage_files 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.