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

The subpackage_applicationCredentials API from Merge — 2 operation(s) for subpackage_applicationcredentials.

Merge subpackage_applicationCredentials 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_applicationCredentials. 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 5 operations across 2 paths, and defines 4 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.

5 operations 2 paths 4 schemas 1 DELETE2 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_applicationCredentials API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (tokenAuth).

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

Paths & Operations 5

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

subpackage_applicationCredentials 5
GET
/api/v1/application-credentials/
List application credentials
list 5 params → 200
POST
/api/v1/application-credentials/
Create application credential
create 1 param body → 201
GET
/api/v1/application-credentials/{id}/
Get application credential
retrieve 2 params → 200
DELETE
/api/v1/application-credentials/{id}/
Delete application credential
destroy 2 params → 200
PATCH
/api/v1/application-credentials/{id}/
Update application credential
partial-update 2 params body → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ApplicationCredentialPublicResponse (7 properties), ApplicationCredentialPublicCreate (4 properties), PaginatedApplicationCredentialPublicResponseList (4 properties), PatchedApplicationCredentialUpdate (3 properties). Each schema is shown below with its type and property counts.

PatchedApplicationCredentialUpdate
object
3 properties
PaginatedApplicationCredentialPublicResponseList
object
4 properties 4 required
ApplicationCredentialPublicResponse
object
Public API response — excludes scope override fields.
7 properties 7 required
ApplicationCredentialPublicCreate
object
Public API request body for creating an application credential.
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-subpackage-applicationcredentials-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_applications API
Merge subpackage_articles API
Merge subpackage_associations API
Where this information came from

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