Hear from Salesforce leaders on how to create and deploy Agentforce agents.
Contact Us 1-800-596-4880

Open Beta Release: The cloud IDE is in open beta. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.

Publishing API Projects to Exchange

logo cloud IDE Cloud IDE

logo desktop IDE Desktop IDE

Publish your API project to Anypoint Exchange so that other team members can find and use it.

Before You Begin

Before publishing an API project:

Publish an API Project to Exchange

To publish your API project to Exchange:

  1. Log in to your Anypoint Platform account.

  2. In Explorer, open your API project and click the Publish API Project to Exchange icon.

    Publish API Project to Exchange icon

    If you don’t open the project, you can also right-click the API specification and select Publish API Project to Exchange.

    Alternatively:

    1. Open the Command Palette.

    2. Enter publish and select the following command:

      MuleSoft: Publish API Project to Exchange
      command
  3. If prompted, click Allow, and follow the prompts to sign in to Anypoint Platform.

  4. Confirm or change each item in Publish API Project to Exchange:

    • Asset Version

    • API Version

      If the API project has never been published to Exchange, the default version is 1.0.0.

      The API version isn’t required for API fragments.

    • Business Group

      If you selected a business group when you created the API project, this field isn’t shown in the form. You can view and update the business by expanding Project Metadata.

  5. Optionally, expand Project Metadata and click API Project Properties to update metadata for the API project, such as updating the asset name and ID and adding tags and categories, updating the business group, and so on. For more information, see Add Metadata to the API Project.

    1. After you complete your updates, click Apply.

  6. In the banner click Sync centralized governance rulesets and run validation to ensure the API project conforms to the applied rulesets.

    This step is optional, but it’s recommended as a best practice. You must be logged in to your Anypoint Platform account and have a business group defined in the API project metadata to validate rulesets.

    Publish API Project to Exchange form with banner to sync centralized rulesets
  7. Click Publish.

    When publishing is complete, you see a message that the API specification successfully published to Exchange.

    If the API project has errors, you must fix the errors before you can publish to Exchange. Errors are listed in the Problems tab. Click the Publish API Project to Exchange icon to bring the Problems tab into focus.

  8. Click View Asset to see the published asset in Exchange.

  9. When prompted to implement the API, select one of the following:

    • No to avoid scaffolding the API specification into your integration.

    • Yes to scaffold the API specification into a new project.

Locate Your API in Exchange

After publishing your API specification, you can find it in Anypoint Exchange:

  1. Navigate to Anypoint Platform and log in using your credentials.

  2. Navigate to Anypoint Exchange.

    Your API specification appears as an asset in your organization, for example:

    API specification in Exchange

You can select the API, navigate through its summary, and see all the endpoints you defined in the previous tasks.

Publish a GraphQL API Spec to Exchange

To publish a GraphQL API specification to Exchange:

  1. Navigate to Anypoint Platform and log in using your credentials.

  2. Navigate to Anypoint Exchange.

  3. Click Publish new asset:

    Publish new asset button in Exchange
  4. Complete the Publish a new asset form:

    Publish a new asset form on Exchange
    1. For Name, type a name for your asset.

    2. For Asset types, select GraphQL API.

    3. For Method, select Upload a GraphQL API Schema.

    4. For File upload, click Choose file and browse for your .graphql schema file.

    5. Click Advanced to change the version number.

    6. For Lifecycle state, select Stable.

  5. Click Publish.

Your GraphQL API spec is now available on Exchange, for example:

"GraphQL API spec on Exchange