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

Conga Merge API

This controller initiates Composer API Merge

Conga Merge API is one of 347 APIs that Conga publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Merge. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 6 operations across 6 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://rls.congacloud.com/api/ingress.

6 operations 6 paths 22 schemas 4 GET2 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://rls.congacloud.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Conga Merge API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (JWT). By default, every request must be authenticated.

  • JWT — Provide oauth authentication

Paths & Operations 6

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

Merge 6

This controller initiates Composer API Merge

POST
/v1/Merge
Initiate the merge workflow
Merge_Post body → 200400500
GET
/v1/Merge/Preview/{correlationId}
Returns the url list of merged and preview documents for a given correlationId.
Merge_GetPreviewFiles 1 param → 200400500
POST
/v1/Merge/Upload
Initiate the merge workflow after uploading JSON data
Merge_Upload body → 200400500
GET
/v1/Merge/{correlationId}/Accept
Accept merge
Merge_AcceptPreview 1 param → 200204400500
GET
/v1/Merge/{correlationId}/Reject
Reject merge
Merge_RejectPreview 1 param → 200204400500
GET
/v1/Merge/{id}
Get merge info
Merge_Get 1 param → 200204400500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are ComposerMergeBaseRequest (10 properties), SalesforceRequest (10 properties), ProblemDetails (6 properties), MergedPreviewDocument (6 properties). Each schema is shown below with its type and property counts.

ComposerMergeResponseModel
object
3 properties
MergedPreviewDocument
object
6 properties
Activity
object
5 properties
ComposerMergeRequest
IntegrationOption
string
SalesforceRequest
object
10 properties
StatusCodes
string
Result
object
2 properties
ProblemDetails
object
6 properties
MergeInfo
object
Merge Information
3 properties
TemplateSourceRequest
object
2 properties
DestinationRequest
object
2 properties
StatusMessage
object
2 properties
SaveCopy
object
2 properties
SignTransaction
object
4 properties
Adaptation
object
2 properties
DataSource2
object
Array of objects containing metadata on the payload source ps: usecase identified for webhooks in the request. Further data sources discovered will be introduc…
4 properties
DataSourceType
string
Type of data source used
SignCommands
object
2 properties
InfoObject
object
Info Object
1 property
ComposerMergeBaseRequest
object
10 properties
OutputRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

conga-merge-api-openapi.yml Raw ↑

Other APIs Conga publishes across the network.

Conga Advantage Platform MCP Server
Conga GraphQL API
Conga 2. Order Actions API
Conga 3. Order Line Items API
Conga Account API
Conga Account Attachments Blacklist API
Conga Account Attachments Whitelist API
Conga Account Designer Settings API
Conga Account Email Reminder Settings API
Conga Account Feature Settings API
Conga Account Package Settings API
Conga Account Roles API
Where this information came from

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