---
schema_version: "1"
id: fedb1a72c264a0850ceaef00bcab9ac827bab0ba277bcbfe90fb5405f48cd66e
title: API Usage Considerations for Salesforce Connect—Cross-Org Adapter
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/xorg_considerations_api_usage.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.xorg_considerations_api_usage.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 853cc20be9f7cf2d3d7a1349dec4eeed031c9563d629466786751c1ed57ddb6a
description: With the cross-org adapter, Salesforce Connect uses Lightning Platform REST API calls to access records in other Salesforce orgs. Depending on how the external object is accessed, each call counts toward the API usage limits of only the provider org or of both provider and subscriber orgs.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# API Usage Considerations for Salesforce Connect—Cross-Org Adapter

With the cross-org adapter, Salesforce Connect uses Lightning Platform REST API calls to access records in other Salesforce orgs. Depending on how the external object is accessed, each call counts toward the API usage limits of only the provider org or of both provider and subscriber orgs.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col>
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience (not for high-data-volume
            external objects)</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Available in: <strong>Developer</strong> Edition</p>
            <p style="margin-bottom:0;">Available for an extra cost
              in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong>
              Editions</p>
          </td>

        </tr>
      </tbody>
    </table>

When a user accesses an external object in one of the following ways, the Lightning Platform REST API call counts toward the API usage limits of the provider org.

- Opening a list view of external object records
- Viewing an external object record detail page
- Viewing a parent object record that contains an external object related list
- Viewing a child object record that contains an external lookup field
- Executing a search that also searches external objects
- Accessing an external object from a flow, Visualforce page, Apex class, or Apex trigger
- Creating, editing, or deleting an external object record
- Running a report
- Editing a report and causing the preview to load in the report builder

If a user or system accesses an external object through the SOAP API, Bulk API, or Lightning Platform REST API, that access counts toward the API usage limits of both the subscriber org and the provider org.

#### See Also

- [_Salesforce Limits Quick Reference Guide_: API Request Limits and Allocations](https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_api.htm)
- [Considerations for Salesforce Connect—Cross-Org Adapter](https://help.salesforce.com/s/articleView?id=platform.xorg_considerations.htm&release=264.0.0&type=5 "Understand the special behaviors, limits, and recommendations for using the cross-org adapter for Salesforce Connect.")
- [Subscriber and Provider Orgs in Salesforce Connect—Cross-Org Adapter](https://help.salesforce.com/s/articleView?id=platform.xorg_subscriber_provider.htm&release=264.0.0&type=5 "The provider org stores the data that the subscriber org accesses.")