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

The subpackage_toolPacks API from Merge — 4 operation(s) for subpackage_toolpacks.

Merge subpackage_toolPacks 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.

Tagged areas include subpackage_toolPacks. 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 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://ah-api.merge.dev.

9 operations 4 paths 11 schemas 2 DELETE3 GET2 PATCH1 POST1 PUT

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_toolPacks 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 4 paths, the API surfaces 9 operations — 2 DELETE, 3 GET, 2 PATCH, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

subpackage_toolPacks 9
GET
/api/v1/tool-packs/
List Tool Packs
list 3 params → 200
POST
/api/v1/tool-packs/
Create Tool Pack
create 1 param body → 201
GET
/api/v1/tool-packs/{id}/
Get Tool Pack
retrieve 2 params → 200
DELETE
/api/v1/tool-packs/{id}/
Delete Tool Pack
destroy 2 params → 200
PATCH
/api/v1/tool-packs/{id}/
Update Tool Pack
partial-update 2 params body → 200
GET
/api/v1/tool-packs/{tool_pack_id}/connectors/
List connectors in a Tool Pack
list-connectors 2 params → 200
PUT
/api/v1/tool-packs/{tool_pack_id}/connectors/
Update connectors in a Tool Pack
replace-connectors 2 params body → 200
PATCH
/api/v1/tool-packs/{tool_pack_id}/connectors/
Update connectors in a Tool Pack (partial)
bulk-upsert-delete-connectors 2 params body → 200
DELETE
/api/v1/tool-packs/{tool_pack_id}/connectors/{slug}/
Remove a connector from a Tool Pack
delete-connector 3 params → 200

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are ConnectorPublic (8 properties), ToolPackPublic (4 properties), ConnectorTool (4 properties), ToolPackConnectorInput (4 properties). Each schema is shown below with its type and property counts.

ToolPackConnectorBulkInputAuthScope
string
Authentication scope. INDIVIDUAL: each user authenticates separately. SHARED: users in the same registeredcompany share one credential. Defaults to INDIVIDUAL…
ToolPackConnectorInputAuthScope
string
How credentials are shared for this connector. - INDIVIDUAL: each registered user authenticates with their own credential - SHARED: users in the same registere…
ToolPackConnectorBulkInput
object
One item in a tool pack connector update request.
4 properties
ConnectorTool
object
Full version of ConnectorTool serializer that includes inputschema details.
4 properties 4 required
PatchedToolPackPublicWrite
object
4 properties
ConnectorPublicAuthScope
string
How credentials are shared for this connector. - INDIVIDUAL: each registered user authenticates with their own credential - SHARED: users in the same registere…
PaginatedToolPackPublicList
object
4 properties 2 required
ToolPackConnectorInput
object
Shared validation for connector identifier inputs. At least one identifier must be provided. When both are set, slug wins and the deprecated connectorid is dis…
4 properties
ConnectorPublic
object
Public tool-pack-scoped connector shape. Used across public endpoints that return a connector attached to a tool pack: both the nested connectors[] in GET /api…
8 properties 8 required
ToolPackPublic
object
4 properties 4 required
ToolPackPublicWrite
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-subpackage-toolpacks-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_toolPacks 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.