---
title: "Salesforce API Versions : Object Visibility"
description: "Salesforce API Versions : Object Visibility"
keywords: "Salesforce API Versions Object Visibility"
url: "https://myrapidi.com/wiki/salesforce_api_versions_object_visibility"
locale: "en"
published: "2025-11-20T11:48:39Z"
modified: "2025-11-20T11:49:10Z"
---

Salesforce releases **three API versions every year** (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.

This article provides a quick, practical overview tailored for Rapidi users and integration administrators.

## **1. Why API Versions Matter**

Every Salesforce object and field is tied to one or more API versions. If your integration uses an older API version that **predates** an object or field, Salesforce simply **won’t expose it** to your calls.

This affects:

- **Object availability** in REST requests
- **Metadata visibility** (fields, picklists, layouts)
- **Rapidi mappings and schemas**

## **2. Rapidi’s Default API Version**

Rapidi integrations use Salesforce REST API **version 42.0** by default.

- Version 42.0 corresponds to **Spring ’18**.
- Any object or field introduced **after Spring ’18** will **not** be visible unless the API version is upgraded.

## 3. Key Objects Introduced in the Latest API Versions (v44–v60+)

| API Range | Product | Example Objects |
| --- | --- | --- |
| v44–46 | CDC / Platform Events | ChangeEventHeader |
| v48–50 | Field Service (FSL) | - ServiceAppointmentDependency

- MaintenanceAsset

- MaintenanceWorkRule

- ResourceAbsence

- ResourcePreference

 |
| v48–52 | CPQ | - SBQQ\_\_Dimension\_\_c

- SBQQ\_\_SubscriptionRatePlanCharge\_\_c

- SBQQ\_\_ContractTerm\_\_c

- SBQQ\_\_PriceRuleAction\_\_c

 |
| v48–53 | Sales Engagement | - SalesCadence

- SalesCadenceStep

- SalesCadenceStepTracker

- WorkQueue

- WorkQueueItem

- InboundMessage

- EngagementChannelType

- TaskFeedItemRelation

 |
| v48–55 | Einstein Bots |
- MessagingEndUser

- MessagingSession

- MessagingMessage

- BotSession

- BotEvent

 |
| v49–56 | Manufacturing Cloud | - AccountForecast

- AccountForecastProduct

- SalesAgreement

- SalesAgreementProduct

 |
| v50–57 | Einstein Activity Capture | - ActivityMetric

- ActivityHistoryExtended

- EinsteinEmailInsight

- EmailMessageRelation

- InboxConfiguration

- InboxUserSettings

 |
| v54–58 | Education Cloud | - ProgramPlan

- ProgramEnrollment

- CourseOffering

- CourseOfferingSchedule

- TermGrade

 |
| v54–58 | Loyalty Management |
- LoyaltyProgram

- LoyaltyMember

- LoyaltyTransaction

- Reward

- Voucher

- Tier

 |
| v56–60 | Data Cloud | - DataCloudAsset

- DataCloudBatch / DataCloudBatchInput / DataCloudBatchOutput

- DataCloudObject

- DataCloudOutput

- Segment

- SegmentMember

- SegmentDefinition

 |

## 4 **. When to Request an API Version Upgrade**

You should reach out to Rapidi Support if:

- You see an object in Salesforce UI but not in Rapidi
- You are integrating CPQ, Sales Engagement, Data Cloud, FSL, or any post-2018 Salesforce feature.
- You need the most recent metadata for automations or mappings.

## 5 **. Summary**

- Rapidi uses **Salesforce API v42.0** by default.
- Many newer Salesforce products and objects require versions **v48+ through v60+**.
- When an object or field is missing, it is usually because the API version predates it.
- Contact Rapidi Support to upgrade your API version when integrating with newly released Salesforce features.