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

The Configuration API from Conga — 10 operation(s) for configuration.

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

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

This API exposes 14 operations across 10 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 3 base URLs: https://rls.congacloud.com, https://preview-rls09.congacloud.com, https://rls.congacloud.com/api/ingress.

14 operations 10 paths 16 schemas 1 DELETE5 GET6 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://rls.congacloud.com
Authentication
API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Conga Configuration API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (Bearer). It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (JWT).

  • Bearer — Please insert JWT with Bearer into field
  • JWT — Provide oauth authentication

Paths & Operations 14

Across 10 paths, the API surfaces 14 operations — 1 DELETE, 5 GET, 6 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Configuration 14
POST
/api/config-management/v1/configurations
Add a configuration
body → 200400500
PUT
/api/config-management/v1/configurations
Update a configuration
body → 200400500
GET
/api/config-management/v1/configurations/categories
Get configuration categories
→ 200400500
POST
/api/config-management/v1/configurations/export
Export custom configuration
body → 200400500
POST
/api/config-management/v1/configurations/import
Import custom configuration
body → 201400500
GET
/api/config-management/v1/configurations/{category}
Get configurations by category
1 param → 200400500
POST
/api/config-management/v1/configurations/{category}
Get multiple configurations
1 param body → 200400500
DELETE
/api/config-management/v1/configurations/{category}/{name}
Delete a configuration
2 params → 200400500
GET
/api/config-management/v1/configurations/{category}/{name}
Get a configuration
2 params → 200400500
GET
/api/esign/v1/esignatures/configuration
Get sign configuration
1 param → 200400500
PUT
/api/esign/v1/esignatures/configuration
Update the sign configuration
1 param body → 200400500
POST
/api/esign/v1/esignatures/configuration/activate
Activate a sign provider
1 param → 200400500
POST
/api/esign/v1/esignatures/configuration/default
Set the default sign provider
1 param → 200400500
GET
/v1/Configuration/environment-info
Retrieves environment and region details from configuration.
Configuration_GetEnvironmentAndRegionInfo → 200400500

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are ConfigurationAPIResponse (10 properties), ConfigurationListAPIResponse (10 properties), StringListAPIResponse (10 properties), BooleanNullableAPIResponse (10 properties). Each schema is shown below with its type and property counts.

ConfigurationAPIResponse
object
10 properties
ConfigurationListAPIResponse
object
10 properties
Configuration
object
Configuration data to be added.
3 properties
ErrorDetail
object
1 property
StringListAPIResponse
object
10 properties
BooleanNullableAPIResponse
object
10 properties
HttpStatusCode
string
StringAPIResponse
object
10 properties
APIResponseError
object
3 properties
Configuration_2
object
3 properties
SignConfig
object
2 properties
ErrorDetail_2
object
2 properties
SignProviderType
string
SignProviderResponse
object
7 properties
EnvironmentInfoResponse
object
Represents the environment and region information.
2 properties
ProblemDetails
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

conga-configuration-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 Configuration 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.