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

The subpackage_opportunities API from Merge — 5 operation(s) for subpackage_opportunities.

Merge subpackage_opportunities 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 7 operations across 5 paths, and defines 33 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.

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

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

Paths & Operations 7

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

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

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Opportunity (19 properties), OpportunityRequest (13 properties), PatchedOpportunityRequest (13 properties), RemoteFieldClass (11 properties). Each schema is shown below with its type and property counts.

PatchedOpportunityRequest
object
The Opportunity Object Description The Opportunity object is used to represent a deal opportunity in a CRM system. Usage Example TODO
13 properties
OpportunityFieldMappings
object
2 properties
ValidationProblemSource
object
1 property 1 required
OpportunityEndpointRequest
object
1 property 1 required
OpportunitiesGetParametersShowEnumOrigins
string
ItemTypeEnum
string
DebugModelLogSummary
object
3 properties 3 required
OpportunitiesIdGetParametersRemoteFields
string
OpportunitiesIdGetParametersExpandSchemaItems
string
OpportunityResponse
object
4 properties 3 required
PatchedOpportunityEndpointRequest
object
1 property 1 required
LinkedAccountStatus
object
2 properties 2 required
OpportunitiesGetParametersExpandSchemaItems
string
FieldFormatEnum
string
OpportunityStatusEnum
string
ItemFormatEnum
string
Opportunity
object
The Opportunity Object Description The Opportunity object is used to represent a deal opportunity in a CRM system. Usage Example TODO
19 properties
MetaResponse
object
5 properties 3 required
RemoteField
object
2 properties 1 required
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
OpportunityRequest
object
The Opportunity Object Description The Opportunity object is used to represent a deal opportunity in a CRM system. Usage Example TODO
13 properties
OpportunitiesGetParametersRemoteFields
string
RemoteFieldClass
object
11 properties
ItemSchema
object
3 properties
PaginatedRemoteFieldClassList
object
3 properties
DebugModeLog
object
3 properties 3 required
OpportunitiesGetParametersStatus
string
FieldTypeEnum
string
PaginatedOpportunityList
object
3 properties
WarningValidationProblem
object
7 properties 3 required
OpportunitiesIdGetParametersShowEnumOrigins
string
ErrorValidationProblem
object
7 properties 3 required
RemoteFieldRequest
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

merge-subpackage-opportunities-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_opportunities 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.