The foundation of the headless architecture is a composable, shared catalog. Agents must be able to query products, attributes, and relationships dynamically without loading a configurator UI. PCM acts as the single source of truth for the commercial structure.
| API Domain / Endpoint | Technical Function | Agentic Application |
|---|---|---|
/connect/product-catalog-management/catalogs |
Retrieves available catalogs based on user context or account eligibility. | Agent determines which product catalog to query based on the Account's region or segment before generating a quote. |
/connect/product-catalog-management/products/{productId}
|
Fetches core product details, selling models, and standard attributes. | Agent retrieves product specifications to answer a buyer's technical question via conversational interface. |
/connect/product-catalog-management/product-components
|
Retrieves child products and bundle structures for a specified parent product. | Agent inspects bundle hierarchies to verify if a required component is present before advancing a quote. |
Unlike legacy CPQ which forces users through sequential UI screens, the Headless Configurator evaluates constraint rules via API. This allows the Agent to pass a payload of customer intent and receive a validated, fully configured bundle structure in milliseconds.
| API Domain / Endpoint | Technical Function | Agentic Application |
|---|---|---|
/connect/revenue/configurations |
Initiates a headless configuration session, returning the initial valid state of a bundle. | Agent starts an invisible configuration session in memory based on an email request for a new server cluster. |
/connect/revenue/configurations/{configId}/actions/validate
|
Processes a payload of selected options and attributes against the Constraint Rules engine. | Agent submits a drafted bundle. If an error returns (e.g., "Missing Power Supply"), the Agent autonomously adds the missing requirement. |
/connect/revenue/configurations/{configId}/actions/finalize
|
Commits the valid configuration structure to the database (creating Quote Line Items). | Agent finalizes the verified bundle structure and moves to the pricing calculation phase. |
The Salesforce Pricing engine decouples pricing logic from the quote object. It uses Context Definitions to map data from anywhere in Salesforce (or external systems) and runs it through sequential Pricing Procedures.
| API Domain / Endpoint | Technical Function | Agentic Application |
|---|---|---|
/connect/pricing/calculate |
The core execution endpoint. Accepts a payload of products and Context tags, returning calculated net prices. | Agent queries external PLM data, builds the context payload, and requests live pricing without creating a physical Quote record. |
/connect/pricing/procedures/{procedureId} |
Invokes a specific waterfall pricing procedure (e.g., Standard B2B, Distributor, or Renewal). | Agent dynamically selects the correct Pricing Procedure based on the Partner Tier identified in the context mapping. |
/connect/pricing/adjustments |
Applies discretionary discounts or overrides to the calculated payload. | Agent injects a dynamically generated 12% discount into the payload to counter a churn risk signal. |
Once the catalog is queried, the bundle configured, and the price calculated, the Agent must commit the transaction to the Salesforce data model to trigger downstream operations.
| API Domain / Endpoint | Technical Function | Agentic Application |
|---|---|---|
/connect/revenue/quotes |
Generates a Quote header and associated line items from the finalized configuration payload. | Agent converts a successful conversational negotiation into a formal Draft Quote for human review. |
/connect/revenue/orders |
Converts a Quote to an Order, invoking order splitting and consolidation rules. | Upon receiving an e-signature webhook, the Agent autonomously converts the Quote to an Order and sets status to Activated. |
/connect/revenue/assets/actions/amend |
Generates a new Quote based on an existing active Asset, applying true-up and pro-ration logic. | Agent detects a capacity breach via telemetry data and automatically generates a pro-rated amendment quote. |
Headless architecture extends beyond quoting into fulfillment. DRO APIs allow external systems or Agents to trigger, monitor, and resolve complex orchestration steps (e.g., software provisioning, physical shipping, billing system sync).
| API Domain / Endpoint | Technical Function | Agentic Application |
|---|---|---|
/connect/orchestration/plans |
Initiates a fulfillment orchestration plan based on Order activation. | Agent monitors the generated Orchestration Plan to track if the ERP system has successfully picked the inventory. |
/connect/orchestration/items/{itemId}/actions/complete
|
Signals to DRO that a specific fulfillment step is complete, advancing the workflow. | External provisioning system hits this API to confirm license creation; Agent reads the status and emails the customer their login details. |
/connect/orchestration/fallouts |
Logs a failure or exception in the fulfillment process. | Agent detects a fallout event (e.g., API timeout to billing system), attempts a self-healing retry, and escalates to IT if unsuccessful. |
To wire these REST endpoints to the Agentforce engine, the Technical Architect wraps these headless calls into Invocable Actions (via Apex or Flow). This abstracts the raw JSON payloads into declarative actions. The AI Agent is then grounded with a library of actions such as "Calculate Price," "Validate Bundle," and "Create Order." The Agent determines when to use them; the Headless 360 API dictates how the system executes them.