rlm-business-apis

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

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill rlm-business-apis-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rlm-business-apis
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/rlm-business-apis
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill rlm-business-apis-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Developers building Salesforce Revenue Cloud integrations struggle to find correct REST endpoints, base paths, and request patterns across the many RLM API domains, and risk using deprecated routes or wrong resource families. ## 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. - Transaction Lifecycle Guidance: Documents the quote-to-asset flow including place, clone, amend, renew, and cancel actions with current versus deprecated endpoints. - Grounded Reference Docs: Links to per-domain markdown references covering 149 endpoints re-extracted from the Release 264 (v68.0) developer guide, plus a Postman collection and interactive HTML viewer. - Use Case: When writing an Apex callout to place a sales transaction, use this Skill to identify the current /connect/rev/sales-transaction/actions/place endpoint instead of the deprecated v63 /commerce/ routes. ## Quick Start Ask the agent to read the rlm-business-apis skill and explain which Revenue Cloud API endpoint to use for placing a quote as an order.

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 a quote or order using the Revenue Cloud API?▼

Use POST /connect/rev/sales-transaction/actions/place, the current entry point for placing sales transactions. The older /commerce/quotes/actions/place and /commerce/sales-orders/actions/place routes are deprecated since v63 and cap 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 applying entitlements and pricing rules for storefront and CPQ scenarios.

How do I authenticate Revenue Cloud Business API calls?▼

All APIs use standard Salesforce OAuth with an Authorization: Bearer <access_token> header. Paths are relative to /services/data/v68.0/ and span multiple resource families, so use each endpoint's own path from the reference docs.

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, and adjustments instead.

Why does my Context Service API call fail?▼

Context definitions must be activated before use. If a context definition is not activated, Product Discovery, Pricing, and Configuration APIs that depend on it will not maintain buyer context correctly.

Is the Postman collection current for Release 264?▼

No. The downloadable Postman collection JSON is still the prior v66.0 baseline and is being regenerated against a live 264 org. Since 264 is pre-GA, treat a live 264 org as ground truth over the docs.