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

The Default API from Merge — 4 operation(s) for default.

Merge Default 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 5 operations across 4 paths, and defines 19 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.

5 operations 4 paths 19 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 Default 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 4 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.

Operations 5
POST
/hris/v1/field-mappings
Field Mappings Create
field-mappings-create 4 params body → 201
DELETE
/hris/v1/field-mappings/{field_mapping_id}
Field Mappings Destroy
field-mappings-destroy 3 params → 204
PATCH
/hris/v1/field-mappings/{field_mapping_id}
Field Mappings Partial Update
field-mappings-partial-update 4 params body → 200
GET
/hris/v1/remote-fields
Remote Fields Retrieve
remote-fields-retrieve 4 params → 200
GET
/hris/v1/target-fields
Target Fields Retrieve
target-fields-retrieve 2 params → 200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are RemoteFieldAPIResponse (16 properties), ExternalTargetFieldAPIResponse (16 properties), CreateFieldMappingRequest (10 properties), WarningValidationProblem (7 properties). Each schema is shown below with its type and property counts.

RemoteFieldApiCoverage
ValidationProblemSource
object
1 property 1 required
FieldMappingApiInstanceRemoteField
object
3 properties 3 required
DebugModelLogSummary
object
3 properties 3 required
ExternalTargetFieldAPI
object
3 properties
FieldMappingInstanceResponse
object
4 properties 3 required
ErrorValidationProblem
object
7 properties 3 required
PatchedEditFieldMappingRequest
object
5 properties
FieldMappingApiInstanceRemoteFieldRemoteEndpointInfo
object
3 properties 3 required
ExternalTargetFieldAPIResponse
object
16 properties
CreateFieldMappingRequest
object
10 properties 4 required
RemoteFieldAPIResponse
object
16 properties
AdvancedMetadata
object
6 properties 1 required
RemoteEndpointInfo
object
3 properties 3 required
DebugModeLog
object
3 properties 3 required
RemoteFieldAPI
object
6 properties 4 required
FieldMappingApiInstanceTargetField
object
3 properties 3 required
WarningValidationProblem
object
7 properties 3 required
FieldMappingApiInstance
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-default-api-openapi.yml Raw ↑

Other APIs Merge publishes across the network.

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
Merge subpackage_associations API
Where this information came from

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