rlm-business-apis

Reference Revenue Cloud Business API endpoints across nine domains for Salesforce integrations.

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill rlm-business-apis-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rlm-business-apis
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/rlm-business-apis
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill rlm-business-apis-bgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers building integrations with Salesforce Revenue Cloud (RLM) need accurate endpoint paths, request patterns, and domain boundaries across 149 REST APIs, and this Skill provides a grounded reference for API v68.0 (Winter '27 / Release 264). ## Core Features & Use Cases - Nine-Domain API Index: Covers PCM, Product Discovery, Product Configurator, Pricing, Rate Management, Transaction Management, Usage Management, Billing, and Context Service with base paths and key operations. - Integration Patterns: Documents authentication via Bearer tokens, the quote-to-asset transaction lifecycle, pricing calculation calls, and context definition activation requirements. - Use Case: When writing an Apex callout to place an order, look up the current POST /connect/rev/sales-transaction/actions/place endpoint instead of the deprecated v63 /commerce/ routes, then load the per-domain reference doc for the exact request shape. ## Quick Start Ask the agent to show the correct Revenue Cloud API endpoint and request pattern for placing a sales transaction using the rlm-business-apis skill.

Frequently Asked Questions about rlm-business-apis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I place an order with the Revenue Cloud API?

Use POST /connect/rev/sales-transaction/actions/place, the current quote and order entry point in v68.0. The older /commerce/quotes/actions/place and /commerce/sales-orders/actions/place routes are deprecated since v63 and capped at 300 line items.

What is the difference between PCM and Product Discovery APIs?

PCM APIs under /connect/pcm/ provide direct catalog CRUD with standard REST semantics for admin and integration use cases. Product Discovery APIs under /connect/cpq/ and /revenue/product-discovery/ are context-aware, buyer-session-scoped operations that apply entitlements and pricing rules for storefront and CPQ scenarios.

How does authentication work for Revenue Cloud Business APIs?

All APIs use standard Salesforce OAuth. Send an Authorization: Bearer header with the access token from org_config.access_token, with paths relative to /services/data/v68.0/.

Can I create price book entries directly through the Pricing API?

No. The Pricing API computes prices via POST /connect/core-pricing/pricing, and you must never write PBE records directly through the API. Use the pricing endpoints to calculate prices, waterfalls, adjustments, and promotion evaluations.

Why do Context Service API calls fail before use?

Context definitions must be activated before they can be used by the Context Service APIs. Context definitions store session state and configuration consumed by Product Discovery, Pricing, and Configuration APIs.

Are the v68.0 Revenue Cloud API docs final for Release 264?

No. Release 264 is pre-GA, so a live 264 org should be treated as ground truth over the documentation. The bundled Postman collection is still the prior v66.0 baseline and is being regenerated against a live 264 org.