Conga Sign API

sign APIs

Business capability
Contract Management BC-150.10

Operations 12

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/clm/v1/sign/esignatures/wetsign/{transactionId}/end Finish a CLM wet signature and attach it to the contract · End wet signature flow #
Ask an LLM
“Once a contract has been signed on paper, can I close out the wet signature in CLM and attach the scanned copy to the agreement?”
“What does ending a wet signature flow on the contracts side do with the signed document I upload?”
Tell an agent
End CLM wet signature transaction {transactionId} and attach the signed copy to its contract.
Close the contract-side wet signature {transactionId} using the scanned file {file}.
POST /api/esign/v1/esignatures Create an eSignature envelope for documents · Create an envelope #
Ask an LLM
“How do I send contract documents out for electronic signature from Conga?”
“Can one envelope go to recipients with CC and BCC copies and an expiration date?”
Tell an agent
Create an eSignature envelope for documents {DocumentIds} addressed to {Recipients}.
Send documents {DocumentIds} to {Recipients} for signature through {signProviderType}, expiring after {Expiration}.
GET /api/esign/v1/esignatures/eventlogs Page through all eSignature event logs · Get all event logs with pagination #
Ask an LLM
“Where can I see the full log of eSignature listener events across every package?”
“Can I page through signature event logs by record number, say records 26 to 50?”
Tell an agent
Show the first 25 eSignature event log entries across all packages.
List eSignature event log records {from} through {to}.
GET /api/esign/v1/esignatures/eventlogs/{packageId} Get the event log for one signature package · Get event logs by package ID #
Ask an LLM
“What events have been recorded for a single signature package I sent?”
“Can I see the listener event history for just one eSignature package ID?”
Tell an agent
Pull the event log for signature package {packageId}.
Show me everything the listener recorded for package {packageId}.
GET /api/esign/v1/esignatures/signertypes List signer roles an eSignature provider allows · List allowed signer types #
Ask an LLM
“What signer types can I put in the Role field when building an envelope?”
“Which recipient roles does a given eSignature service provider accept?”
Tell an agent
List the allowed signer types for {signProviderType}.
Show which signer roles I can assign to envelope recipients.
GET /api/esign/v1/esignatures/templates List templates held by the eSignature provider · Get sign provider templates #
Ask an LLM
“What signing templates already exist in my eSignature provider account?”
“Can I see the provider-side templates I could reuse when creating an envelope?”
Tell an agent
List the eSignature templates available in {signProviderType}.
Fetch the sign provider's template list.
GET /api/esign/v1/esignatures/transaction/{objectId}/latestSignTransaction Find which sign provider handled a record's latest signing · Get the latest sign provider #
Ask an LLM
“Which eSignature provider was used for the most recent signing on this agreement?”
“Can I tell whether the last signature request on a record went through the provider I expect?”
Tell an agent
Find the sign provider used on the latest eSign transaction for record {objectId}.
Tell me which signature service handled the newest signing request on {objectId}.
GET /api/esign/v1/esignatures/transactionByObjectId/{objectId} Look up signature transaction details by record ID · Get transaction details by object ID #
Ask an LLM
“I only have the agreement record ID I used for the envelope; can I still get its signing status?”
“Is there a way to look up eSignature transaction details from the object ID instead of the package ID?”
Tell an agent
Get the eSignature transaction details for record {objectId}.
Look up the signing transaction that was created for object {objectId}.
GET /api/esign/v1/esignatures/usersearch/{searchString} Search users and contacts to add as signers · List users #
Ask an LLM
“Can I search users and contacts by part of their name to pick signature recipients?”
“How do I find a colleague to add as a signer when I only remember a few letters of their name?”
Tell an agent
Search users and contacts matching {searchString} for signature recipients.
Find people whose names contain {searchString} so I can add them as signers.
POST /api/esign/v1/esignatures/void/{objectId} Void a pending eSignature request · Create api esign esignatures void by object id #
Ask an LLM
“Can I void a signature request that's already been sent out on an agreement?”
“Is it possible to record a reason and notify the other recipients when I void an envelope?”
Tell an agent destructive · confirm first
Void the eSignature request on record {objectId}.
Void the envelope for {objectId} with reason {voidReason} and notify the other recipients: {notifyOthers}.
POST /api/esign/v1/esignatures/wetsign/{transactionId}/end Mark an eSign wet-sign transaction complete · End wet-sign flow #
Ask an LLM
“In the eSign service, can I mark a wet-sign transaction as ended and upload the paper-signed document?”
“What happens to the eSignature transaction when I finish a wet-sign and supply the signed file?”
Tell an agent
Mark eSign wet-sign transaction {transactionId} as ended.
Upload {file} as the signed document and end the eSign wet-sign flow {transactionId}.
GET /api/esign/v1/esignatures/{transactionId} Get signing status and dates for a package · Get transaction details by transaction #
Ask an LLM
“Has my envelope been signed yet, and when was it sent and signed?”
“If a recipient declined to sign, where do I see the reason they gave?”
Tell an agent
Get the status, sent date and signed date for transaction {transactionId}.
Check whether package {transactionId} was declined and why.

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-sign-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-sign-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Conga Sign API
  version: v1
  description: 'Operations tagged Sign across 2 of this provider''s published API definitions: conga-contracts.json, conga-esignature.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
security:
- bearerAuth: []
tags:


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