<turbo-stream action="update" target="wiki_card"><template>

<h1>Salesforce API Versions : Object Visibility</h1>
<div class="trix-content"><p>Salesforce releases <strong>three API versions every year</strong> (Spring, Summer, Winter). Each release may introduce new standard objects, fields, and features—or retire older ones. Understanding which API version your integration uses is essential for ensuring compatibility and preventing missing-field or missing-object errors.</p><p>This article provides a quick, practical overview tailored for Rapidi users and integration administrators.<br><br></p><h2><strong>1. Why API Versions Matter</strong></h2><p>Every Salesforce object and field is tied to one or more API versions. If your integration uses an older API version that <strong>predates</strong> an object or field, Salesforce simply <strong>won’t expose it</strong> to your calls.</p><p>This affects:</p><ul><li><strong>Object availability</strong> in REST requests</li><li><strong>Metadata visibility</strong> (fields, picklists, layouts)</li><li><strong>Rapidi mappings and schemas</strong></li></ul><p><br></p><h2><strong>2. Rapidi’s Default API Version</strong></h2><p>Rapidi integrations use Salesforce REST API <strong>version 42.0</strong> by default.</p><ul><li>Version 42.0 corresponds to <strong>Spring ’18</strong>.</li><li>Any object or field introduced <strong>after Spring ’18</strong> will <strong>not</strong> be visible unless the API version is upgraded.</li></ul><p><br></p><h2>3. Key Objects Introduced in the Latest API Versions (v44–v60+)</h2><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>API Range</td><td>Product</td><td>Example Objects</td></tr></thead><tbody><tr><td>v44–46</td><td>CDC / Platform Events</td><td>ChangeEventHeader</td></tr><tr><td>v48–50</td><td>Field Service (FSL)</td><td><li><p>ServiceAppointmentDependency</p>
</li>
<li>
<p>MaintenanceAsset</p>
</li>
<li>
<p>MaintenanceWorkRule</p>
</li>
<li>
<p>ResourceAbsence</p>
</li>
<li>
<p>ResourcePreference</p></li></td></tr><tr><td>v48–52</td><td>CPQ</td><td><li><p>SBQQ__Dimension__c</p>
</li>
<li>
<p>SBQQ__SubscriptionRatePlanCharge__c</p>
</li>
<li>
<p>SBQQ__ContractTerm__c</p>
</li>
<li>
<p>SBQQ__PriceRuleAction__c</p></li></td></tr><tr><td>v48–53</td><td>Sales Engagement</td><td><li><p>SalesCadence</p>
</li>
<li>
<p>SalesCadenceStep</p>
</li>
<li>
<p>SalesCadenceStepTracker</p>
</li>
<li>
<p>WorkQueue</p>
</li>
<li>
<p>WorkQueueItem</p>
</li>
<li>
<p>InboundMessage</p>
</li>
<li>
<p>EngagementChannelType</p>
</li>
<li>
<p>TaskFeedItemRelation</p></li></td></tr><tr><td>v48–55</td><td>Einstein Bots</td><td><ul><li><p>MessagingEndUser</p>
</li>
<li>
<p>MessagingSession</p>
</li>
<li>
<p>MessagingMessage</p>
</li>
<li>
<p>BotSession</p>
</li>
<li>
<p>BotEvent</p>
</li>
</ul></td></tr><tr><td>v49–56</td><td>Manufacturing Cloud</td><td><li><p>AccountForecast</p>
</li>
<li>
<p>AccountForecastProduct</p>
</li>
<li>
<p>SalesAgreement</p>
</li>
<li>
<p>SalesAgreementProduct</p></li></td></tr><tr><td>v50–57</td><td>Einstein Activity Capture</td><td><li><p>ActivityMetric</p>
</li>
<li>
<p>ActivityHistoryExtended</p>
</li>
<li>
<p>EinsteinEmailInsight</p>
</li>
<li>
<p>EmailMessageRelation</p>
</li>
<li>
<p>InboxConfiguration</p>
</li>
<li>
<p>InboxUserSettings</p></li></td></tr><tr><td>v54–58</td><td>Education Cloud</td><td><li><p>ProgramPlan</p>
</li>
<li>
<p>ProgramEnrollment</p>
</li>
<li>
<p>CourseOffering</p>
</li>
<li>
<p>CourseOfferingSchedule</p>
</li>
<li>
<p>TermGrade</p></li></td></tr><tr><td>v54–58</td><td>Loyalty Management</td><td><ul><li><p>LoyaltyProgram</p>
</li>
<li>
<p>LoyaltyMember</p>
</li>
<li>
<p>LoyaltyTransaction</p>
</li>
<li>
<p>Reward</p>
</li>
<li>
<p>Voucher</p>
</li>
<li>
<p>Tier</p>
</li>
</ul></td></tr><tr><td>v56–60</td><td>Data Cloud</td><td><li><p>DataCloudAsset</p>
</li>
<li>
<p>DataCloudBatch / DataCloudBatchInput / DataCloudBatchOutput</p>
</li>
<li>
<p>DataCloudObject</p>
</li>
<li>
<p>DataCloudOutput</p>
</li>
<li>
<p>Segment</p>
</li>
<li>
<p>SegmentMember</p>
</li>
<li>
<p>SegmentDefinition</p></li></td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><h2>4<strong>. When to Request an API Version Upgrade</strong></h2><p>You should reach out to Rapidi Support if:</p><ul><li>You see an object in Salesforce UI but not in Rapidi</li><li>You are integrating CPQ, Sales Engagement, Data Cloud, FSL, or any post-2018 Salesforce feature.</li><li>You need the most recent metadata for automations or mappings.</li></ul><h2>5<strong>. Summary</strong></h2><ul><li>Rapidi uses <strong>Salesforce API v42.0</strong> by default.</li><li>Many newer Salesforce products and objects require versions <strong>v48+ through v60+</strong>.</li><li>When an object or field is missing, it is usually because the API version predates it.</li><li>Contact Rapidi Support to upgrade your API version when integrating with newly released Salesforce features.</li></ul></div>
</template></turbo-stream>

