Lab 1: Search for an API in Exchange


API’s are the reusable assets that simplify and accelerate the creation of modern software applications. As a Mulesoft developer you will need to consume API’s created by other members of the organization and publish new API’s for others to consume. This new consumption model is the foundation of a new approach for delivering software solutions where API’s form the building blocks of the modern enterprise.

This first lab will focus on using Anypoint Exchange to search for API’s and other assets published in the private exchange.

Step 1: Login to Anypoint Platform

  1. Go to

    Login screen
  2. Enter your credentials into the Username and Password fields.

    Enter credentials
  3. You should see the following landing page once you are logged in to Anypoint Platform.

    Anypoint platform
  4. Click on the Business Group that is on the right top of the screen.

    module1 lab1 click bg
  5. Select the sub business group.

    module1 lab1 select bg

Step 2: Access Anypoint Exchange

  1. Click on the icon labeled "Discover & share"

    API Manager Icon
  2. You will now be presented the landing page for the Anypoint Exchange portal:

    Anypoint Exchange

    Anypoint Exchange should be your initial starting point for just about any project. If you are looking to reuse an API then Anypoint Exchange is obviously where you should start. But even if you are creating a new API to be reused by others, it makes sense to first look in Exchange to see if the API already exists. Sometimes you will find that someone else has already undertaken the task of creating the API, or has created a subset of what you need.

  3. Anypoint Exchange allows for discovery on the public or private exchange. Every organization will automatically have a private exchange created for them.

    Software assets stored in Anypoint Exchange can only be discovered by users that have permissions for the private exchange for that organization. Furthermore, organization administrators can also create independent business groups to provide even more restrictive discovery. Anypoint Exchange users can only search within their currently selected business group.

    module1 lab1 orgs

    As you can see from the screen above, there are organizational search criteria on the left hand side of the page. By default searches will search both the Mulesoft exchange and the private exchange, but you can restrict your searches by selecting a different organizational level.

    There are two more items behind the last organization My applications and Public Portal. We will describe them but they are covered in Module 5 and Lab 4.

    module1 lab1 myapps
    • My applications: These are the clients registered in the organization that are consuming the APIs that are deployed in the organization.

    • Public Portal: You can define a public portal to let any user to consume any public org API that the organization may publish.

      To search for an API, use the search bar at the top of the Anypoint Exchange portal:

      Exchange search

      Anypoint Exchange supports keyword searching to find the API you are looking for. However, Anypoint Exchange can be used as a discovery tool for more than just API’s. Anypoint Exchange is the enterprise repository for the following types of reusable software assets:

    • Connector - Packaged connectivity to an endpoint developed and deployed on MuleSoft’s Anypoint Platform with third-party APIs and standard integration protocols.

    • Template - Packaged integration patterns that address common use cases and are built on best practices. Applications to which you add your scenario-specific information to complete a use case or solution.

    • Example - Implementation projects that explain development elements within Anypoint Studio and how these can be leveraged to achieve specific API and integration objectives.

    • REST API - API descriptions in RAML format that make the consumption of REST API’s faster and easier.

    • SOAP API - API descriptions in WSDL format that make the consumption of a SOAP API’s faster and easier.

    • RAML Fragment - Shared fragments of RAML files that can be used to assemble new API’s with common traits.

    • Custom - A general category for sharing resources such as links, blogs, articles, videos and more.

  4. Click on the search field and type "omni", then hit the Enter Key.

    The list of Exchange assets should now be filtered to look something like this:

    Exchange search
    The number of icons listed may change.
  5. Click on the tile named Omni Channel Experience API.

    Select API

    You should now see the page dedicated to the API definition.

    API Page

    Exchange provides several new features to support and encourage discovery and collaboration.

    First note the content in the portal to help you learn how to use the API. We will learn how to create this content in Lab 4 - Publish the Omni-Channel API to Exchange. But for now, let’s do a quick survey of the key features of the Exchange portal:

    API Page
    1. Options Panel - The options panel has three options.

      • Share: This option allows you to share the API with users, users that have a role, or publish to the Public portal.

      • Download: This option is to download the RAML Spec or Mule Plugin to use it as a Connector.

      • Edit: This option allows to edit the API portal.

    2. Information Panel - This provides general information about the API. It shows the instances implemented.

      By clicking on the "ellipsis" button a new menu is displayed where you can:

      • Download as RAML

      • Download as OAS

      • View code in API Designer

      • Deprecate version

      • Delete version

        Much of this information is automatically generated during the design and development of the API.

        API Page

    3. Tags - Tags make it easier to search and discover API’s. Rather than relying on the title or description of the API, tags allow for you to create categories of API’s related to each other by tags.

    4. Dependencies - New to Exchange, dependencies are automatically generated during the design and development process. Dependencies are important to speed API consumption by helping the API consumer understand what else is relevant to the API. It also provides a quick way to navigate the exchange and procure additional assets required in order to effectively use the API.

      module1 lab1 dependencies
    5. Ratings and Reviews - New to Exchange, API users can review and comment on an API. This enables collaboration with the API owner and the ability to share experiences using the API that might help other API consumers.

      module1 lab1 rating reviews
    6. API Summary - This is the API specification. API resources can be seen here. You can click on each resource and view the documentation.

    7. API Instances - This gives you the opportunity to edit the API Implementation endpoints. You can also add other implementations.

      module1 lab1 visibility settings
    8. Version - You can select and see the portal of each API Version.

      Let’s explore how to design an API in the next lab.

Please proceed to Lab 2