Conga Configuration API

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

Operations 14

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /api/config-management/v1/configurations Add a new configuration · Add a configuration #
Ask an LLM
“How do I add a brand-new configuration entry to the platform?”
“Can I group new configurations under a category like CLM or eSign?”
Tell an agent
Add a new configuration {Name} with value {Value} under category {Category}.
Create configuration {Name} set to {Value}.
PUT /api/config-management/v1/configurations Update an existing configuration value · Update a configuration #
Ask an LLM
“How do I change the value of a configuration setting that already exists?”
“Can I edit a configuration entry inside a specific category?”
Tell an agent
Update configuration {Name} in category {Category} to value {Value}.
Change the existing {Name} setting to {Value}.
GET /api/config-management/v1/configurations/categories List configuration categories · Get configuration categories #
Ask an LLM
“What configuration categories are available?”
“Which categories are my configurations grouped into?”
Tell an agent
List all configuration categories.
Show the categories used to group configurations.
POST /api/config-management/v1/configurations/export Export custom configuration as a zip · Export custom configuration #
Ask an LLM
“How can I export my custom configuration to move it to another environment?”
“Can I download configuration for only certain categories as a zip file?”
Tell an agent
Export the custom configuration for these categories as a zip.
Download a zipped export of my custom configuration.
POST /api/config-management/v1/configurations/import Import custom configuration from a zip · Import custom configuration #
Ask an LLM
“How do I load a configuration zip exported from another environment?”
“What happens if an imported configuration already exists?”
Tell an agent
Import custom configuration from zip file {file}.
Upload configuration package {file} into this environment.
GET /api/config-management/v1/configurations/{category} List all configurations in a category · Get configurations by category #
Ask an LLM
“Which configurations belong to the eSign category?”
“Can I see every setting in one configuration category?”
Tell an agent
List all configurations in category {category}.
Show every {category} configuration setting.
POST /api/config-management/v1/configurations/{category} Fetch several named configurations at once · Get multiple configurations #
Ask an LLM
“Can I fetch a handful of specific configuration names from a category in one request?”
“How do I look up multiple named settings together?”
Tell an agent
Get these named configurations from category {category}.
Fetch the listed configuration names within {category} in one call.
DELETE /api/config-management/v1/configurations/{category}/{name} Delete a configuration · Delete a configuration #
Ask an LLM
“Can I remove a configuration setting I no longer need?”
“Is deleting a configuration by category and name permanent?”
Tell an agent destructive · confirm first
Delete configuration {name} from category {category}.
Remove the {category} setting named {name}.
GET /api/config-management/v1/configurations/{category}/{name} Get a single configuration · Get a configuration #
Ask an LLM
“What is the current value of one specific configuration?”
“Where can I read a single setting by its category and name?”
Tell an agent
Get configuration {name} in category {category}.
Show the value of the {category} setting {name}.
GET /api/esign/v1/esignatures/configuration Get the eSignature provider configuration · Get sign configuration #
Ask an LLM
“How is my eSignature provider currently configured?”
“Can I view the sign configuration for one particular provider type?”
Tell an agent
Show the eSignature configuration.
Get the sign configuration for provider type {signProviderType}.
PUT /api/esign/v1/esignatures/configuration Save the eSignature provider configuration · Update the sign configuration #
Ask an LLM
“How do I connect and configure an eSignature service for contracts?”
“Will saving the sign configuration give me a consent URL to authorize the provider?”
Tell an agent
Save sign configuration {Configuration} for provider type {signProviderType}.
Update the {signProviderType} eSignature settings with state {State}.
POST /api/esign/v1/esignatures/configuration/activate Activate an eSignature provider · Activate a sign provider #
Ask an LLM
“How do I enable a configured sign provider so it can be used for signatures?”
“Does a sign provider need to be activated before sending documents for signature?”
Tell an agent
Activate sign provider {signProviderType}.
Turn on {signProviderType} for eSignature operations.
POST /api/esign/v1/esignatures/configuration/default Set the default eSignature provider · Set the default sign provider #
Ask an LLM
“Which sign provider should new eSignature transactions use by default?”
“Can I make one sign provider the default for every new signature request?”
Tell an agent
Make {signProviderType} the default sign provider.
Use {signProviderType} as the default for all new eSignature transactions.
GET /v1/Configuration/environment-info Get environment and region info · Retrieves environment and region details from configuration #
Ask an LLM
“Which environment and region is this service running in?”
“How do I check the configured region?”
Tell an agent
Show environment and region details.
Get the current environment info.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/conga:conga-configuration-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

conga-configuration-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Conga Configuration API
  version: '1.0'
  description: 'Operations tagged Configuration across 3 of this provider''s published API definitions: conga-configuration-management.json, conga-esignature.json, conga-ingress.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://rls.congacloud.com
- url: https://preview-rls09.congacloud.com
- url: https://rls.congacloud.com/api/ingress
tags:


# --- truncated at 32 KB (33 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/conga/refs/heads/main/openapi/conga-configuration-api-openapi.yml