slug: conga provider: Conga generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 98 edges: - tag: Contract Lifecycle spec_file: conga-contract-lifecycle-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.95 evidence: '"Activate a contract", "Amend a contract", "Renew a contract", "Terminate a contract"' reason: Explicit contract lifecycle state transitions from activation to termination. - tag: Contract spec_file: conga-contract-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.94 evidence: POST /api/clm/v1/contracts "Create a contract record"; PUT "/{contractId}/signstatus Update a contract's signature status" reason: 'Core CLM surface: CRUD over contract records plus signature status — contract lifecycle management.' - tag: Price Lists spec_file: conga-price-lists-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.92 evidence: '"Retrieve price lists", schemas "PriceList", "PriceListCategory", "PriceListItem"' reason: Direct maintenance of price lists, price list items and categories — Price List Management. - tag: Clause spec_file: conga-clause-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.9 evidence: '"POST /api/xauthor/v1/clauses/alternate Get alternate clauses"; "GET /api/xauthor/v1/clauses/bundles/{name} Get a clause bundle"' reason: Clause retrieval, alternates validation and clause bundles are contract authoring operations within Conga's CLM/X-Author surface, realising contract lifecycle (drafting) capability. - tag: Clause Obligations spec_file: conga-clause-obligations-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.9 evidence: '"POST /api/clm/v1/clauses/{clauseId}/obligations Create a clause obligation request"' reason: CLM-pathed CRUD over obligations attached to contract clauses — obligation management is a core part of contract lifecycle management. - tag: Contract Clause spec_file: conga-contract-clause-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.9 evidence: POST /api/clm/v1/contracts/{contractId}/clause "Create a new contract clause"; "Update multiple clauses of a contract" reason: Clause authoring and maintenance within contract records is part of contract drafting/lifecycle management. - tag: In-Effect View spec_file: conga-in-effect-view-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.9 evidence: GET /api/clm/v1/contracts/{contractId}/in-effect-view/clauses "Get in-effect view of contract clause changes" reason: Explicit CLM endpoints returning the in-effect state of contract clauses, details and documents — squarely contract lifecycle management. - tag: ClauseLibrary spec_file: conga-clauselibrary-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.88 evidence: '"POST /api/xauthor/v1/clauses/promote Promote a clause"; "POST /api/xauthor/v1/clauses/query Get clauses"' reason: Clause library querying and promotion is standard contract lifecycle management (clause standardisation for drafting). - tag: AIRedline spec_file: conga-airedline-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: POST /api/xauthor/v1/contracts/{contractId}/AI/redline/check-in ... process the check-in or publish of the document based on the AI suggestion; AIRiskRedlineIdentificationRequest reason: Operations redline, preview and risk-check contract documents and check them in — contract drafting/negotiation activity, i.e. contract lifecycle management. - tag: Agreement spec_file: conga-agreement-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: POST /api/xauthor/v1/contracts — Create an agreement; Get agreement details by contract; schema Apttus.XAuthor.Core.Model.Agreement reason: Creates, queries and retrieves agreements/contracts including ownership and recently-viewed views — squarely contract lifecycle management. - tag: AgreementClause spec_file: conga-agreementclause-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: '"Create agreement clauses as final" on /api/xauthor/v1/contracts/{contractId}/clauses/final; "This class holds APIs related to agreement clauses"' reason: Operations create, finalize and revert clause entries inside contracts — clause authoring is squarely contract lifecycle management. - tag: AgreementDocument spec_file: conga-agreementdocument-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: '"Regenerate an agreement document with the selected template"; "Get agreement document versions"' reason: Manages versions, merges and regeneration of agreement (contract) documents — contract drafting/lifecycle, not generic document storage. - tag: AgreementOffline spec_file: conga-agreementoffline-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: '"Create an offline agreement"; "Import an offline agreement"; "Create store executed agreement"' reason: Creating, importing and storing executed agreements is contract lifecycle management. - tag: ClauseComparison spec_file: conga-clausecomparison-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: '"POST /api/xauthor/v1/clause/compare The Api is used to initiate the clause semantic comparison request"' reason: Semantic comparison of contract clauses supports contract drafting/negotiation review, a contract management activity. - tag: ClauseContent spec_file: conga-clausecontent-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: '"POST /api/xauthor/v1/clause-content/mark Mark plain text as a clause"; "Get the markup clause details for both template and agreement"' reason: Marking and inserting clause content into templates and agreements is contract document authoring within the contract lifecycle. - tag: Contract Documents spec_file: conga-contract-documents-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: POST /api/clm/v1/contracts/{contractId}/documents "Create a new contract document"; POST /api/clm/v1/contracts/storeexecuted "Create a contract from an executed contract" reason: Document artefacts of contracts (offline creation, executed contract storage, versions/review status) — contract lifecycle document handling, not generic file upload. - tag: Contract Obligations spec_file: conga-contract-obligations-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: POST /api/clm/v1/contracts/{contractId}/obligations "Create an obligation for a contract"; "Get the obligation and fulfillment details of the contract" reason: Management of contractual obligations attached to contract records — post-signature contract administration within CLM. - tag: Contract Obligations Fulfillment spec_file: conga-contract-obligations-fulfillment-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: '"Get all active obligation fulfillments for the Manage Fulfillment listing"; schema ContractObligationFulfillment' reason: Tracking and actioning fulfilment of contract obligations is contract compliance/administration within contract lifecycle management. - tag: Contract Relationship spec_file: conga-contract-relationship-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: GET /api/clm/v1/contracts/{contractId}/hierarchy "Get hierarchy of a contract"; POST "/relationships/link Link contracts using RelationshipFromType and RelationshipToType" reason: Linking contracts and modelling contract hierarchies (amendments, related agreements) is part of contract lifecycle management. - tag: Contract Request spec_file: conga-contract-request-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: POST /api/clm/v1/requests "Create a contract request"; POST "/{contractRequestId}/convert Convert a contract request to an agreement" reason: Contract intake requests and their conversion into agreements is the front end of the contract lifecycle. - tag: Invoices spec_file: conga-invoices-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.85 evidence: 'POST /invoices/approve Approve one or more invoices; POST /invoices/cancel Cancels one or more invoices; schemas: Invoice, InvoiceLineItem, RelatedARTransaction' reason: Direct lifecycle operations on invoices and invoice line items — generation, approval and adjustment/cancellation of customer invoices. - tag: Obligations spec_file: conga-obligations-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: openapi description "Controller for managing obligations."; "Get activated contracts with obligations" on /api/clm/v1/obligations/ reason: CLM endpoint retrieving activated contracts and their obligations — contractual obligation tracking is part of the contract lifecycle, mapping to Contract Management. - tag: PriceLists spec_file: conga-price-lists-api-openapi.yml reanchored_from: conga-pricelists-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.85 evidence: Catalog APIs for Pricelists; GET /price-lists/active Retrieve a price list reason: Directly retrieves price lists — price book/list management. - tag: Quote spec_file: conga-quote-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.85 evidence: POST /quotes Create quotes; POST /quotes/{Id}/accept Accept a quote and create an order; POST /api/cart/v1/quotes/{quoteId}/carts/activate Launch a cart reason: Quote lifecycle including cart-based configuration and acceptance into an order — configure-price-quote. - tag: Review spec_file: conga-review-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.85 evidence: '"Get contract review details in CLM", "Initiate a review", "Add reviewers to a review cycle in CLM" on /api/clm/v1/contracts/{contractId}/reviews' reason: Operations run review cycles on contract records in Conga's CLM, i.e. a stage of the contract lifecycle (drafting/negotiation review), mapping to Contract Management. - tag: Role Admin spec_file: conga-role-admin-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.85 evidence: '"Create a new role", "Assign admin permissions to a role", "Assign permission groups to a role" under /api/user-management/v1/roles' reason: Role, permission-group and admin-permission administration in the user-management service — role-based access control, i.e. Identity & Access Management. - tag: User Admin spec_file: conga-user-admin-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.85 evidence: '"Create a user", "Deactivate a user", "Generate integration user secret"; schemas "AssignPermissionGroups", "DeletePermissionGroups"' reason: Full user account lifecycle (create, bulk upsert, deactivate) plus credential/secret issuance and permission-group assignment — classic identity and access administration. - tag: Contract Team Members spec_file: conga-contract-team-members-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.82 evidence: POST /api/clm/v1/contracts/{contractId}/teammembers "Add contract team members"; schema ContractTeamMembers, TeamMemberType reason: Operations manage the team assigned to a contract record within the CLM (contract lifecycle) API, i.e. contract lifecycle administration rather than HR staffing — Contract Management is the fitting capability. - tag: Incentive Coupons spec_file: conga-incentive-coupons-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.82 evidence: POST /incentives/{ParentId}/coupons/generate/{numberOfCoupons} "Auto generates specified number of incentive coupons" reason: Coupon generation and lifecycle for incentive programmes is promotional offer management, matching discount & promotion management. - tag: Package Deployment spec_file: conga-package-deployment-api-openapi.yml capability_id: BC-4210.40 capability_id_l1: BC-4210 capability_name: Deployment Orchestration confidence: 0.82 evidence: Deploy source artifact package / Promote a package to the target environment / Revert a custom code deployment package with given name / Track package deployment status reason: Deploy, promote, rollback and monitor custom-code artefact packages across environments — deployment orchestration within software release and deployment management. - tag: PlatformComposerFeatureFlag spec_file: conga-platformcomposerfeatureflag-api-openapi.yml capability_id: BC-4210.50 capability_id_l1: BC-4210 capability_name: Feature Flag Management confidence: 0.82 evidence: GET /v1/FeatureFlags/{featureFlagName} Evaluate PlatformComposer feature flag for the given Salesforce Org Id reason: Runtime evaluation of a named feature flag scoped to an org — feature flag management, the runtime control side of release engineering. - tag: Related Price List Items spec_file: conga-related-price-list-items-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.82 evidence: POST /price-list-items/{ParentId}/related-price-list-items "Create related price list items"; schema RelatedPriceListItem reason: CRUD over price list items and their relations — price book / price list maintenance. - tag: AgreementSigningCycle spec_file: conga-agreementsigningcycle-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: '"Retrieves a list of agreement signing cycles based on the specified signing provider type and agreement ID"' reason: E-signature signing cycles for agreements = contract execution stage of the contract lifecycle. - tag: AlternateClause spec_file: conga-alternateclause-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: '"Link alternate clauses"; "Unlink alternate clauses"; "Reorder alternate clauses"' reason: Managing alternate contract clause options is clause-library/contract drafting work within contract lifecycle management. - tag: CartActions spec_file: conga-cart-actions-api-openapi.yml reanchored_from: conga-cartactions-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.8 evidence: POST /api/cart/v1/carts/{cartId}/finalize Finalize a cart; GET /api/cart/v1/carts/{cartId}/configstatus Retrieve Configuration status reason: Cart lifecycle actions (activate, abandon, clone, finalize, configuration status) with QuoteOverride schema in Conga's CPQ — squarely configure-price-quote handling. - tag: CartItems spec_file: conga-cart-items-api-openapi.yml reanchored_from: conga-cartitems-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.8 evidence: POST /api/cart/v1/carts/{cartId}/reprice Reprice cart items reason: Add, update, clone and reprice quote line items with PriceListItem, ProductConfiguration and ProductOptionGroup schemas — CPQ line-item configuration and pricing. - tag: Consumption Billing spec_file: conga-consumption-billing-api-openapi.yml capability_id: BC-4250.20 capability_id_l1: BC-4250 capability_name: Rating & Charging confidence: 0.8 evidence: '''Controller for CRUD operations on usage inputs, supporting rating, unrating, and draft rating'' and ''Rates the specified usage input records''' reason: Usage-input rating and re-rating is squarely usage-based rating and charging; usage capture (metering) is adjacent but rating is the explicit operation. - tag: Document Generation spec_file: conga-document-generation-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: POST /api/clm/v1/contracts/{contractId}/generate — Generate a document; POST /api/clm/v1/contracts/{contractId}/supportingdocument reason: Operations generate, preview, regenerate and join documents against a contract id in the CLM API, i.e. producing contract documents as part of the contract lifecycle. - tag: Initiate Billing spec_file: conga-initiate-billing-api-openapi.yml capability_id: BC-4250 capability_id_l1: BC-4250 capability_name: Subscription Billing & Revenue Management confidence: 0.8 evidence: 'POST /schedules/initiate Create billing records based on Order Line Item (OLI) status; POST /schedules/renew Renew Schedules; schemas: BillingScheduleDetails, BillingHeader' reason: Operations create, amend, renew, swap and terminate billing schedules that drive recurring charges for subscriptions — subscription billing and revenue management. Evidence spans schedule generation and adjustment rather than naming a single sub-capability, so L1 only. - tag: IntelligentImport spec_file: conga-intelligentimport-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: POST /api/xauthor/v1/intelligent-imports/documents/mark-clauses-and-fields Extract and mark the clauses and fields in the request document; GET .../status/{contractId}/{attachmentId} reason: Extraction of clauses and fields from contract documents keyed by contractId is contract lifecycle management (third-party paper import into CLM). - tag: Invoice Configurations spec_file: conga-invoice-configurations-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.8 evidence: Provides endpoints for configuring and managing invoice run requests; GET /configure-requests/{id}/estimate Retrieves a preview of an invoice request, including billing schedule records and estimated invoice details reason: Configuration and preview of invoice runs is invoice generation control within subscription billing — invoicing and statement management. - tag: Playbook spec_file: conga-playbook-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: Provides API endpoints for managing playbooks associated with a contract ... Get the list of playbooks based upon contract type, source and legal entity ... ClauseRule, DocumentRule reason: Retrieves negotiation/redline playbooks and clause rules matched to a specific contract — a contract lifecycle (authoring/negotiation) capability. - tag: PlaybookExecution spec_file: conga-playbookexecution-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: '"executing playbooks against contract documents and retrieving playbook execution results including clause and document rule outcomes"' reason: Operations execute contract playbooks and return clause rule outcomes on contract documents — contract lifecycle/review automation, i.e. Legal Management / Contract Management. - tag: Rebates spec_file: conga-rebates-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.8 evidence: POST /api/cart/v1/carts/{cartId}/rebate-estimates "Perform the estimated rebate details for a cart."; POST /rebates "Create rebates" reason: Creates and administers rebate programmes and estimates rebate amounts on a cart — rebate management is named explicitly within Discount & Promotion Management. - tag: RuleExecution spec_file: conga-ruleexecution-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.8 evidence: '"Provides API endpoints for executing individual playbook rules against contract documents and retrieving clause-level and document-level rule execution results"' reason: Executes contract playbook rules against contract documents and returns clause-level redline recommendations — automated contract review/authoring within the contract lifecycle. - tag: ContractCheckin spec_file: conga-contractcheckin-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.78 evidence: '"This class contains APIs related to agreement document checkins"; POST /api/xauthor/v1/contracts/{contractId}/check-in; schema ContractClauseBaseModel, ClauseReconcileModel' reason: Checks agreement documents back in with clause reconciliation and metadata processing — core contract drafting/versioning within contract lifecycle management. - tag: DAI spec_file: conga-dai-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.78 evidence: '"Extract and mark the clauses and fields in the request document and also update the metadata"; path /discovery-ai/contracts/{contractid}/documents/{attachmentId}/markup-document; schema DAIExtractedClauses' reason: Operations perform AI-driven clause and field extraction and markup on contract documents, which is contract lifecycle/intelligence work sitting under Contract Management. - tag: Incentive Conditions spec_file: conga-incentive-conditions-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.78 evidence: POST /rebates/{ParentId}/conditions "Create incentive conditions"; schema IncentiveCondition under "Rebate Administration" reason: Defines the qualifying conditions of rebate/incentive programmes, which is rebate and promotion policy administration under discount & promotion management. - tag: Property Permission spec_file: conga-property-permission-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.78 evidence: PUT /api/user-management/v1/property-permissions/{permissionGroupName}/{propertyName} Upsert a new property permission reason: Field-level permission administration within a user-management service — access control/authorisation, i.e. identity & access management. - tag: AgreementDocumentCheckin spec_file: conga-agreementdocumentcheckin-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.75 evidence: '"Check in a document specific to an agreement"; schema Apttus.XAuthor.Common.DTO.Contracts.DocumentCheckInResponse' reason: Check-in of agreement documents with clause approval payloads is part of contract authoring workflow; slightly plumbing-like but bound to contracts. - tag: Carts spec_file: conga-carts-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.75 evidence: POST /api/cart/v1/carts Create carts; schema Conga.Revenue.Entities.Platform.ProductConfiguration reason: CRUD over CPQ carts (product configurations) in Conga's Revenue/CPQ platform — the container for quote configuration, mapping to Quote & Configuration Management. - tag: ClauseMetadata spec_file: conga-clausemetadata-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.75 evidence: '"GET /api/xauthor/v1/clauses/metadata Get a template clause''s metadata"; schemas "AgreementClauseFilterMetadata", "RiskRating", "ClauseTypes"' reason: Metadata describing agreement/template clauses including clause types and risk rating serves contract authoring; slightly lower confidence because the surface is metadata-descriptive rather than transactional. - tag: ClauseVersion spec_file: conga-clauseversion-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.75 evidence: '"GET /api/xauthor/v1/clauses/{clauseId}/versions/{clauseVersionId}/richtext-content Get clause content as text or HTML"' reason: Versioned retrieval of contract clause content supports contract drafting/authoring; thin surface (single operation) so moderate confidence. - tag: Field Permission spec_file: conga-field-permission-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: 'POST /api/user-management/v1/field-permissions ''Set field permissions''; GET ''...field permission details by object and permission group name''; schemas: FieldPermission, FieldAccessConfigRequest' reason: User-management API granting and revoking field-level access rights to permission groups — access control administration, i.e. identity and access management. Fine-grained authorisation config, so slightly below top confidence. - tag: Incentive Limits spec_file: conga-incentive-limits-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.75 evidence: POST /incentives/{ParentId}/limits "Create incentive limits"; schema IncentiveLimit reason: Caps and limits on incentive/rebate programmes are part of discount and promotion policy administration; sub-capability inferred from the incentive/rebate parent resource. - tag: Invoice Request Results spec_file: conga-invoice-request-results-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.75 evidence: GET /request-results/{id}/invoices Retrieves all invoices associated with a specific invoice request result reason: Retrieval of invoices produced by an invoice run belongs to invoicing and statement management; the surface is read-only reporting on the invoice generation process. - tag: Price Dimensions spec_file: conga-price-dimensions-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.75 evidence: '"Create price dimensions", schema "PriceDimension"' reason: CRUD over pricing structure dimensions used by CPQ pricing setup — pricing management, closest to price list/price book maintenance. - tag: Price Matrices spec_file: conga-price-matrices-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.75 evidence: '"Create price matrices", schema "PriceMatrix"' reason: Maintenance of pricing matrices used to derive prices; pricing structure/price book maintenance under Pricing Management. - tag: Price Matrix Entries spec_file: conga-price-matrix-entries-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.75 evidence: '"Retrieve price matrix entries", schema "PriceMatrixEntry" with "CurrencyField"' reason: CRUD over individual priced matrix entries (currency amounts) — pricing structure maintenance. - tag: Rebate Programs spec_file: conga-rebate-programs-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.75 evidence: POST /programs Create Rebate Programs; schema IncentiveProgram reason: Administration of rebate/incentive programme definitions, which is squarely discount, promotion and rebate policy management. - tag: Rebate Rules spec_file: conga-rebate-rules-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.75 evidence: POST /rebates/{ParentId}/rules "Create rebate rules"; schema IncentiveRule reason: CRUD over rebate rules attached to a rebate programme; rebates are explicitly named in the Discount & Promotion Management capability. - tag: User Group spec_file: conga-user-group-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: '"Create a user group", "Update a user group"; schemas "UserGroupCreateRequest", "UserGroupUpsertRequest"' reason: User group CRUD inside the user-management service is access-grouping administration, part of identity and access management rather than any HR or organisational capability. - tag: User Group Member spec_file: conga-user-group-member-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: '"Create user group members in bulk", "Delete a user group member"; schema "UserGroupMember"' reason: Membership assignment to access groups within the user-management API — group/role membership administration under IAM. - tag: AgreementTemplate spec_file: conga-agreementtemplate-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.72 evidence: '"Get a template for an agreement"; schemas Template, TemplateStage, ClauseFormat' reason: Agreement template retrieval supports contract drafting; narrow read-only surface so moderate confidence. - tag: BusinessObject spec_file: conga-business-object-api-openapi.yml reanchored_from: conga-businessobject-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.72 evidence: POST /api/cart/v1/business-objects/{businessObjectId}/carts/reactivate Reactivates the cart syncing the fields from quote to cart. reason: Operations launch, read and reactivate the CPQ cart for a quote-like business object, with ProductConfigurationOverride schema — this is configure-price-quote cart handling, i.e. Quote & Configuration Management. - tag: Object Permission spec_file: conga-object-permission-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.72 evidence: '"Create a new object permission", "Validate object action permission"; schemas ObjectPermission, UserScopeConfig, ScopePermissionConfig under /api/user-management/v1/' reason: User-management surface defining and validating per-object/action permissions and scopes — authorisation administration, which sits under Identity & Access Management. It is genuine access-control administration rather than mere authentication plumbing. - tag: Opportunity spec_file: conga-opportunity-api-openapi.yml capability_id: BC-410.30 capability_id_l1: BC-410 capability_name: Opportunity & Pipeline Management confidence: 0.72 evidence: '"Get all opportunity records", "Insert a new opportunity record", "Upsert multiple opportunity records"; schema OpportunityRequestExample' reason: CRUD/query surface over sales Opportunity records in Conga's revenue platform, realising Opportunity & Pipeline Management. Confidence tempered because it is a generic data-object API pattern. - tag: Permission Groups spec_file: conga-permission-groups-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.72 evidence: Get the master list of permission groups / Add permission group names to the master list / Clone the permission group reason: CRUD over permission groups in the user-management service — authorisation/role administration, i.e. identity and access management. - tag: Price Programs spec_file: conga-price-programs-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.72 evidence: '"Create incentives", "Retrieve incentives", schema "Incentive"' reason: Operations explicitly manage incentives (rebates/promotions) despite the price-program path — Discount & Promotion Management. - tag: Price Rule Entries spec_file: conga-price-rule-entries-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.72 evidence: '"Create price rule entries", schema "PriceRuleEntry" with "CurrencyField"' reason: Administration of price rule entries governing computed prices — pricing structure maintenance within Pricing Management. - tag: Price Rules spec_file: conga-price-rules-api-openapi.yml capability_id: BC-440 capability_id_l1: BC-440 capability_name: Pricing Management confidence: 0.72 evidence: POST /rule-sets/{ParentId}/rules Create price rules; schema PriceRule reason: CRUD over price rules that govern how prices are computed — pricing management; too generic to pin a specific L2. - tag: ProductOptionGroups spec_file: conga-productoptiongroups-api-openapi.yml capability_id: BC-820.40 capability_id_l1: BC-820 capability_name: Product Configuration & Variant Management confidence: 0.72 evidence: POST /products/{ParentId}/option-groups/{Id}/bulk Add multiple existing OptionGroups as sub OptionGroups to Product Bundle reason: Defines option groups and bundle hierarchies for products — configuration, options and bundles, i.e. product configuration & variant management. - tag: Rebate Rule Entries spec_file: conga-rebate-rule-entries-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.72 evidence: 'POST /rebate-rules/{ParentId}/entries "Create rebate rule entries"; schemas: IncentiveRuleEntry' reason: Operations administer the entry-level detail of rebate (incentive) rules, i.e. the rules governing rebate/incentive amounts — this is rebate and promotion policy administration under Pricing Management. Not sales commission (schemas sit under Rebate Administration). - tag: RedlineExecutionStatus spec_file: conga-redlineexecutionstatus-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.72 evidence: '"Tracks extraction and redlining progress for rules applied against a contract document."' reason: Polls status of AI redlining applied to a contract document — contract drafting/negotiation activity within Contract Management. Status polling is technical, but the object is explicitly a contract redline. - tag: Action Permissions spec_file: conga-action-permissions-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: GET /api/user-management/v1/actionpermissions — Get the master list of all action permissions; schemas ActionPermission, ActionPermissionsGroup reason: A user-management endpoint enumerating action permissions/permission groups, i.e. the authorisation model behind user access. Best fits Identity & Access Management; confidence tempered because it is a single read-only lookup. - tag: AgreementReview spec_file: conga-agreementreview-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.7 evidence: GET /api/xauthor/v1/contracts/{contractId}/reviews with schema Apttus.XAuthor.Core.Model.DocumentReviewInfo reason: Retrieves review information for a contract document — contract negotiation/review stage of CLM; evidence is thin (one unsummarised operation). - tag: Constraint Rule Actions spec_file: conga-constraint-rule-actions-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.7 evidence: '''Create constraint rule actions'', ConstraintRuleActionExpression — Administration Constraint Rule Actions API on a CPQ platform' reason: Constraint rules in Conga CPQ govern valid product configuration/inclusion-exclusion during quoting, i.e. configure-price-quote rule administration. - tag: Constraint Rule Conditions spec_file: conga-constraint-rule-conditions-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.7 evidence: '''Create constraint rule conditions'', schema ConstraintRuleCondition' reason: Conditions of CPQ constraint rules controlling allowed product configurations during quoting — Quote & Configuration Management. - tag: Constraint Rules spec_file: conga-constraint-rules-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.7 evidence: '''Retrieve constraint rules'' / ''Create constraint rules'', schema ConstraintRule' reason: CPQ constraint rule administration governing valid configurations in quotes; fits Quote & Configuration Management. - tag: Contact spec_file: conga-contact-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.7 evidence: '''Get all contact records'', ''Upsert multiple contact records'', ''Get object contact record count and size on disk''' reason: CRUD over contact master records constitutes customer/contact data management, though the surface is a generic data-object API. - tag: Contract Request Team Members spec_file: conga-contract-request-team-members-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.7 evidence: POST /api/clm/v1/requests/{contractRequestId}/teammembers "Add contract request team members"; schema ContractRequestTeamMembers reason: Assigns collaborators/roles on a contract request within CLM — supports contract lifecycle handling rather than HR or generic access control, though it is an administrative sub-surface. - tag: Contract Type Document Requirement Settings spec_file: conga-contract-type-document-requirement-settings-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.7 evidence: '"Controller for managing Contract Type Document Requirement Settings"; GET /api/clm/v1/settings/documents/contract-type-requirements "Query document requirement settings by contract type and action"' reason: Configures which documents are required per contract type within the CLM surface — a contract lifecycle governance setting. Confidence moderated because it is a settings/configuration surface. - tag: Credit Memos spec_file: conga-credit-memos-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.7 evidence: '"API controller for managing credit memo operations"; POST /creditmemos/approve "Approve one or more credit memos"; schema RelatedARTransaction, CreditMemoLineItem' reason: Credit memo approval/cancellation with AR transaction linkage is customer-side billing adjustment, i.e. accounts receivable management; could alternatively be read as invoice adjustment in a subscription billing frame. - tag: Incentives spec_file: conga-incentives-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.7 evidence: POST /api/cart/v1/carts/{cartId}/incentives Add an incentive; Conga.Revenue.Cart.Manager.Model.IncentiveModel reason: Incentives are attached to the pricing cart, i.e. promotions/rebates/discounts applied to a quote line — discount and promotion management rather than sales compensation. - tag: Milestone Schedule spec_file: conga-milestone-schedule-api-openapi.yml capability_id: BC-4250 capability_id_l1: BC-4250 capability_name: Subscription Billing & Revenue Management confidence: 0.7 evidence: '"Mark billing schedule details complete" / "Get billing schedule details for order line items" (MilestoneScheduleHeaderDTO, BillingHeaderMilestoneResponse)' reason: Operations manage milestone-based billing schedules against billing headers and order line items — recurring/contract billing management; unclear whether it sits under rating or invoicing so L2 left null. - tag: Price Program Rule Entries spec_file: conga-price-program-rule-entries-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.7 evidence: '"Create incentive rule entries", schema "IncentiveRuleEntry"' reason: Rule entries defining incentive amounts within incentive programmes — discount/rebate/promotion rule administration. - tag: Price Program Rules spec_file: conga-price-program-rules-api-openapi.yml capability_id: BC-440.30 capability_id_l1: BC-440 capability_name: Discount & Promotion Management confidence: 0.7 evidence: '"Retrieve incentive rules", schema "IncentiveRule"' reason: Administration of incentive rules under price programs — discount/rebate programme rule management. - tag: Price Rule Sets spec_file: conga-price-rule-sets-api-openapi.yml capability_id: BC-440.10 capability_id_l1: BC-440 capability_name: Pricing Strategy Management confidence: 0.7 evidence: POST /rule-sets Create price rule sets; schema PriceRuleset reason: Administration of pricing rule sets in a CPQ platform — configuration of pricing logic/structure, best fit Pricing Management; sub-capability uncertain between pricing strategy and price list maintenance. - tag: PriceEscalator spec_file: conga-priceescalator-api-openapi.yml capability_id: BC-440.20 capability_id_l1: BC-440 capability_name: Price List Management confidence: 0.7 evidence: POST /price-list-items/{ParentId}/price-escalators Create price escalators; schema PriceEscalator reason: Escalators attached to price list items — maintenance of pricing structures within price books. - tag: Product Attribute Groups spec_file: conga-product-attribute-groups-api-openapi.yml capability_id: BC-820.40 capability_id_l1: BC-820 capability_name: Product Configuration & Variant Management confidence: 0.7 evidence: POST /products/{ParentId}/attribute-groups Create product attribute groups; schema ProductAttributeGroup reason: Product attribute grouping used to drive configurable product options — product configuration and variant management. - tag: Product Attribute Rules spec_file: conga-product-attribute-rules-api-openapi.yml capability_id: BC-820.40 capability_id_l1: BC-820 capability_name: Product Configuration & Variant Management confidence: 0.7 evidence: POST /attribute-rules Create product attribute rules; schema ProductAttributeRule reason: Rules constraining product attribute combinations — configuration and variant management for configurable products. - tag: Product Option Components spec_file: conga-product-option-components-api-openapi.yml capability_id: BC-820.40 capability_id_l1: BC-820 capability_name: Product Configuration & Variant Management confidence: 0.7 evidence: GET /product-option-group/{ParentId}/products Retrieve product option components; schema ProductOptionComponent reason: Manages the option components inside product option groups, i.e. bundle options and variants of a catalogued product — product configuration and variant management in the CPQ catalog. - tag: Products spec_file: conga-products-api-openapi.yml capability_id: BC-820 capability_id_l1: BC-820 capability_name: Product Lifecycle Management confidence: 0.7 evidence: POST /products Create multiple products; GET /products/{id}/constraint-rules Retrieve all constraint rules; schemas Product, ProductCategory, PriceListItem reason: Full CRUD and structuring of the product catalog including categories, attributes and constraint rules. Clearly product lifecycle/catalog management; the surface spans specification, categorisation and configuration so no single L2 is decisive. - tag: Proposal Locations spec_file: conga-proposal-locations-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.7 evidence: POST /quotes/{ParentId}/locations Create proposal locations; schema ProposalLocation reason: Child records of quotes (proposals) capturing per-location detail used when configuring and pricing a proposal — part of the quote/CPQ surface. - tag: Record Type Permission spec_file: conga-record-type-permission-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: PUT /api/user-management/v1/recordtype-permissions "Update a record type's permission for a given permission group and object" reason: User-management API assigning object/record-type permissions to permission groups — authorisation administration, mapped to Identity & Access Management. - tag: Sign spec_file: conga-sign-api-openapi.yml capability_id: BC-150.10 capability_id_l1: BC-150 capability_name: Contract Management confidence: 0.7 evidence: '"POST /api/clm/v1/sign/esignatures/wetsign/{transactionId}/end End wet signature flow", "POST /api/esign/v1/esignatures Create an envelope", "List allowed signer types"' reason: E-signature envelope creation, signer types, voiding and wet-sign completion, published under the CLM definition — the execution/signature step of the contract lifecycle. Confidence 0.7 since e-signature is a generic document-execution service that may serve non-contract documents too. - tag: Split Criteria spec_file: conga-split-criteria-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.7 evidence: '"Provides endpoints for managing invoice split criteria setups, including creation, activation, and deactivation."; schema SplitCriteriaSetup' reason: Configures how invoices are split when generated, i.e. invoice generation rules within billing. Mapped to Invoicing & Statement Management; some ambiguity versus general accounts receivable invoicing. - tag: User spec_file: conga-user-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: '"Get all action permissions for the current user", "Get field permission details by object name", "Get users with full access on given objects"' reason: Surface exposes logged-in user identity, object/field-level permissions and access lookups — access management plumbing, not an HR employee record. Some locale/currency personalisation operations dilute the fit.