---
schema_version: "1"
id: 53eb61afbff2106727fa69eed8e6eebd6a57be88f6e68fc9603777de03062d63
title: Bring Apex APIs into API Catalog
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/api_catalog_bring_apex_apis_into.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.api_catalog_bring_apex_apis_into.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e23f079788444c4db8348df13cd00787159654a68713b883e3da2694aa174606
description: Bring Apex REST and AuraEnabled APIs into API Catalog to take advantage of the automatic agent action activation and make your APIs more discoverable.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Bring Apex APIs into API Catalog

Bring Apex REST and AuraEnabled APIs into API Catalog to take advantage of the automatic agent action activation and make your APIs more discoverable.

### 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: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Developer</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
          <colgroup>
            <col style="width:50%">
            <col style="width:50%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d22068e72">User Permissions Needed</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d22068e72 ">To access API Catalog:</td>
              <td class="slds-cell-wrap" style="vertical-align:top;" headers="d22068e72 ">
                <p>Available to Salesforce admins by default.</p>
                <p style="margin-bottom:0;">For other users, View Setup</p>
              </td>
            </tr>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d22068e72 ">To bring Apex APIs into API Catalog:</td>
              <td class="slds-cell-wrap" style="vertical-align:top;" headers="d22068e72 ">Customize Application</td>
            </tr>
          </tbody>
        </table>

API information brought into API Catalog must meet schema and governance requirements.

- Schema definitions
- Schema update requirements
- API governance ruleset definitions (applied to APIs annotated for agent actions)

APIs brought into API Catalog must meet the system limits.

- External Services system limits
- Other system limits for Apex APIs

If you reach system limits during the Apex deployment, remove APIs that you no longer need.

## Bring Apex REST APIs into API Catalog

If you have Apex REST code with custom agent actions and an LLM to create the OAS document for the REST code, you can bring the API into your API catalog.

Deploy an Apex REST class, OAS document, and associated metadata to use as an agent action. See [_Agentforce Developer Guide_: Build Custom Agent Actions using Apex REST (Beta)](https://developer.salesforce.com/docs/einstein/genai/guide/agent-apex.html).

The deployment automatically adds the OAS API to your org’s API catalog.

## Bring Apex AuraEnabled APIs into API Catalog

If you have Apex classes with methods annotated with @AuraEnabled, you can bring the API into your API catalog.

Deploy an AuraEnabled controller method to use as an agent action. See [_Agentforce Developer Guide_: Build Custom Agent Actions from Apex Controller Methods](https://developer.salesforce.com/docs/einstein/genai/guide/agent-auraenabled.html).

The deployment automatically adds the OAS API to your org’s API catalog.

## System Limits for Apex Documents in API Catalog

When you deploy Apex classes, there are maximum limits for registrations, schema size, operations, objects, and properties. These limits affect what is displayed in API Catalog.

 
| Limit | VALUE |
| --- | --- |
| Max Apex API registrations | 150 per org |
| Max schema size (JSON) | 10,000,000 characters (10.0 MB) |
| Max schema size (YAML) | 3,000,000 characters (3.0 MB) |
| Max active operations | 1250 per org |
| Max active and inactive operations | 10,000 total per org |
| Max active objects | 1250 per org |
| Max active and inactive objects | 10,000 total per org |
| Max object properties | 400,000 total per org |

#### See Also

- [_Agentforce Developer Guide_: Build Custom Agent Actions using Apex REST](https://developer.salesforce.com/docs/einstein/genai/guide/agent-apex.html)
- [_Agentforce Developer Guide_: Build Custom Agent Actions from Apex Controller Methods](https://developer.salesforce.com/docs/einstein/genai/guide/agent-auraenabled.html)
- [System Limits](https://help.salesforce.com/s/articleView?id=platform.external_services_schema_def_limits.htm&language=en_US)
- [Schema Definitions](https://help.salesforce.com/s/articleView?id=platform.external_services_schema_def_definition.htm&language=en_US)
- [Schema Update Support](https://help.salesforce.com/s/articleView?id=platform.external_services_appendix_update_schema.htm&language=en_US)
- [Manage External Services](https://help.salesforce.com/s/articleView?id=platform.external_services_view_edit.htm&language=en_US)