This documentation is for WSO2 API Manager 1.10.0 View documentation for the latest release.
Page Comparison - Invoke an API using the Integrated API Console (v.1 vs v.3) - API Manager 1.10.0 - WSO2 Documentation

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added a note to state that HTTPS APIs can not be tried out via API Console.

WSO2 API Manager has an integrated Swagger UIUI, which is part of the Swagger project. 

Swagger is a 100% open source, standard, language-agnostic specification and a complete framework for describing, producing, consuming, and visualizing RESTful APIs, without the need of a proxy or third-party services. Swagger allows consumers to understand the capabilities of a remote service without accessing its source code and interact interacts with the service with a minimal amount of implementation logic. Swagger helps describe a services service in the same way that interfaces describe lower-level programming code. 

The Swagger UI is a dependency-free collection of HTML, JavaScript, and CSS that dynamically generate documentation from a Swagger-compliant API. Swagger Swagger-compliant APIs give you interactive documentation, client SDK generation and more discoverability. The  The Swagger UI has JSON code and its UI facilitates easier code indentation, keyword highlighting and shows syntax errors on the fly. You can add resource parameters, summaries and descriptions to your APIs using the Swagger UI.

Also, see the Swagger 2.0 specification.

Let's see how to use the API Console in the Store to invoke an API.


See the following topics for a description of the concepts that you need to know when invoking an API:


You can only try out HTTPS based APIs via the API Console, because the API Store runs on HTTPS.

The examples here use the PhoneVerification API, which is created in section Create and Publish an API. Include PageAPIMShared:Invoke an API using the Integrated API Console V2APIMShared:Invoke an API using the Integrated API Console V2

  1. Log in to the API Store and click an API (e.g., PhoneVerification).

  2. Subscribe to the API (e.g., PhoneVerification 1.0.0) using the default application and an available tier.
    Image Added

  3. Go to the My Subscriptions page and generate a production key to the default application using which you subscribed to the API.
    Image Added

  4. Click the APIs menu in the API Store and then click on the API that you want to invoke. When the API opens, go to its API Console tab.
    Image Added

  5. Expand the GET method, provide the required parameters and click Try it Out. For example,

    PhoneNumberE.g., 18006785432
    LicenseKeyGive 0 for testing purpose
    AuthorizationThe API console is automatically populated by the access token that you generated in step 3 after subscribing to the API. 

    The token is prefixed by the string "Bearer" as per the OAuth bearer token profile. OAuth security is enforced on all published APIs. If the application key is invalid, you get a 401 Unauthorized response in return.

    Base URL

    Appears at the bottom of the console. Using the base URL and the parameters, the system creates the API URL in the form https://<host_name>:8243/<context>/<version>/<Resource, if any><backend service requirements included as parameters, if any>. For example, in https://localhost:8243/phoneverify/1.0.0/CheckPhoneNumber, /phoneverify is the context, 1.0.0 is the version and CheckPhoneNumber is the resource.


    If you cannot invoke the API's HTTPS endpoint (causes the SSLPeerUnverified exception), it could be because the security certificate issued by the server is not trusted by your browser. To resolve this issue, access the HTTPS endpoint directly from your browser and accept the security certificate.

    Image Added

  6. Note the response for the API invocation. As we used a valid phone number in this example, the response is valid.
    Image Added

 You have invoked an API using the Swagger API console.