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

The subpackage_scopes API from Merge — 16 operation(s) for subpackage_scopes.

Merge subpackage_scopes 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 24 operations across 16 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 7 base URLs: https://api.merge.dev/api, https://api-eu.merge.dev/api, https://api-ap.merge.dev/api, https://api.merge.dev/api/chat/v1, https://api-eu.merge.dev/api/chat/v1, https://api-ap.merge.dev/api/chat/v1, https://api-ap.merge.dev/api/knowledgebase/v1.

24 operations 16 paths 8 schemas 16 GET8 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_scopes API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (tokenAuth).

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

Paths & Operations 24

Across 16 paths, the API surfaces 24 operations — 16 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

subpackage_scopes 24
GET
/accounting/v1/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/accounting/v1/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/accounting/v1/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200
GET
/ats/v1/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/ats/v1/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/ats/v1/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200
GET
/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200
GET
/crm/v1/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/crm/v1/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/crm/v1/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200
GET
/filestorage/v1/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/filestorage/v1/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/filestorage/v1/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200
GET
/hris/v1/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/hris/v1/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/hris/v1/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200
GET
/knowledgebase/v1/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/knowledgebase/v1/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/knowledgebase/v1/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200
GET
/ticketing/v1/default-scopes
Default Scopes Retrieve
default-scopes-retrieve 1 param → 200
GET
/ticketing/v1/linked-account-scopes
Linked Account Scopes Retrieve
linked-account-scopes-retrieve 2 params → 200
POST
/ticketing/v1/linked-account-scopes
Linked Account Scopes Create
linked-account-scopes-create 2 params body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are IndividualCommonModelScopeDeserializerRequest (3 properties), IndividualCommonModelScopeDeserializer (3 properties), FieldPermissionDeserializerRequest (2 properties), FieldPermissionDeserializer (2 properties). Each schema is shown below with its type and property counts.

CommonModelScopeAPI
object
1 property 1 required
ModelPermissionDeserializer
object
1 property
IndividualCommonModelScopeDeserializerRequest
object
3 properties 1 required
FieldPermissionDeserializerRequest
object
2 properties
ModelPermissionDeserializerRequest
object
1 property
IndividualCommonModelScopeDeserializer
object
3 properties 1 required
LinkedAccountCommonModelScopeDeserializerRequest
object
1 property 1 required
FieldPermissionDeserializer
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-subpackage-scopes-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_scopes 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.