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

The subpackage_accounts API from Merge — 10 operation(s) for subpackage_accounts.

Merge subpackage_accounts 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 13 operations across 10 paths, and defines 49 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.

13 operations 10 paths 49 schemas 10 GET1 PATCH2 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_accounts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (tokenAuth).

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

Paths & Operations 13

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

subpackage_accounts 13
GET
/accounting/v1/accounts
List
list 21 params → 200
POST
/accounting/v1/accounts
Create
create 4 params body → 201
GET
/accounting/v1/accounts/{id}
Retrieve
retrieve 8 params → 200
GET
/accounting/v1/accounts/meta/post
Meta Post Retrieve
meta-post-retrieve 2 params → 200
GET
/crm/v1/accounts
List
list 16 params → 200
POST
/crm/v1/accounts
Create
create 4 params body → 201
GET
/crm/v1/accounts/{id}
Retrieve
retrieve 7 params → 200
PATCH
/crm/v1/accounts/{id}
Partial Update
partial-update 5 params body → 200
GET
/crm/v1/accounts/meta/patch/{id}
Meta Patch Retrieve
meta-patch-retrieve 3 params → 200
GET
/crm/v1/accounts/meta/post
Meta Post Retrieve
meta-post-retrieve 2 params → 200
GET
/crm/v1/accounts/remote-field-classes
Remote Field Classes List
remote-field-classes-list 10 params → 200
GET
/ticketing/v1/accounts
List
list 12 params → 200
GET
/ticketing/v1/accounts/{id}
Retrieve
retrieve 5 params → 200

Schemas 49

The contract defines 49 schemas that model the data the API accepts and returns. The most detailed are Account_2 (20 properties), Account (18 properties), AccountRequest (13 properties), AccountRequest_2 (12 properties). Each schema is shown below with its type and property counts.

AccountsIdGetParametersExpandSchemaItems
string
ValidationProblemSource
object
1 property 1 required
AccountsIdGetParametersShowEnumOrigins
string
AccountStatusEnum
string
DebugModelLogSummary
object
3 properties 3 required
AccountsGetParametersStatus
string
AccountRequest
object
The Account Object Description An Account represents a category in a company’s ledger in which a financial transaction is recorded against. The aggregation of…
13 properties
AccountsGetParametersRemoteFields
string
AccountFieldMappings
object
2 properties
TransactionCurrencyEnum
string
The currency code in ISO 4217 format.
ClassificationEnum
string
LinkedAccountStatus
object
2 properties 2 required
MetaResponse
object
5 properties 3 required
AccountsGetParametersExpandSchemaItems
string
RemoteData
object
The RemoteData Object Description The RemoteData object is used to represent the full data pulled from the third-party API for an object. Usage Example TODO
2 properties 1 required
AccountEndpointRequest
object
1 property 1 required
AccountsIdGetParametersRemoteFields
string
Account
object
The Account Object Description An Account represents a category in a company’s ledger in which a financial transaction is recorded against. The aggregation of…
18 properties
AccountAccountTypeEnum
string
AccountResponse
object
4 properties 3 required
PaginatedAccountList
object
3 properties
DebugModeLog
object
3 properties 3 required
AccountsGetParametersShowEnumOrigins
string
WarningValidationProblem
object
7 properties 3 required
ErrorValidationProblem
object
7 properties 3 required
AccountsGetParametersClassification
string
AccountsIdGetParametersExpandSchemaItems_2
string
AddressRequest
object
The Address Object Description The Address object is used to represent an entity's address. Usage Example TODO
9 properties
PatchedCRMAccountEndpointRequest
object
1 property 1 required
ItemTypeEnum
string
PhoneNumber
object
The PhoneNumber Object Description The PhoneNumber object is used to represent an entity's phone number. Usage Example Fetch from the GET Contact endpoint and…
4 properties
Address
object
The Address Object Description The Address object is used to represent an entity's address. Usage Example TODO
9 properties
AddressTypeEnum
string
AccountRequest_2
object
The Account Object Description The Account object is used to represent a company in a CRM system. Usage Example TODO
12 properties
FieldFormatEnum
string
PatchedAccountRequest
object
The Account Object Description The Account object is used to represent a company in a CRM system. Usage Example TODO
12 properties
ItemFormatEnum
string
RemoteField
object
2 properties 1 required
AccountsGetParametersExpandSchemaItems_2
string
CountryEnum
string
The country code in ISO 3166-1 alpha-2 format.
Account_2
object
The Account Object Description The Account object is used to represent a company in a CRM system. Usage Example TODO
20 properties
RemoteFieldClass
object
11 properties
ItemSchema
object
3 properties
CRMAccountResponse
object
4 properties 3 required
PaginatedRemoteFieldClassList
object
3 properties
CRMAccountEndpointRequest
object
1 property 1 required
FieldTypeEnum
string
RemoteFieldRequest
object
2 properties 1 required
Account_3
object
The Account Object Description The Account object is used to represent the account that a ticket is associated with. The account is a company that may be a cus…
9 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-subpackage-accounts-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_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 subpackage_accounts 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.