This documentation is for WSO2 API Manager 1.10.0 View documentation for the latest release.
Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
Page Comparison - Create and Publish an API (v.12 vs v.13) - API Manager 1.10.0 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Log in to the API Publisher.
  2. Select the option to design a new API and click Start Creating.
  3. Give the information in the table below and click the Add button to add the resource.

    FieldSample value
    NamePhoneVerification
    Context
    /phoneverify

     

    Tip

    Tip: You can define the API's version as a parameter of its context by adding the {version} into the context.For example,{version}/phoneverify.The API Manager assigns the actual version of the API to the {version} parameter internally. For example, https://localhost:8243/1.0.0/phoneverify. Note that the version appears before the context, allowing you to group your APIs according to versions.

    Version1.0.0
    VisibilityPublic
    ResourcesURL patternCheckPhoneNumber
     Request types

    GET, POST

     

  4. After the resource is added, expand its GET method and update the Produces to application/xml and Consumes to application/json. Next, add the following parameters. You use these parameters to invoke the API using our integrated API Console in later tutorials. Once done, click Implement .

    Parameter NameDescriptionParameter TypeData TypeRequired
    PhoneNumberGive the phone number to be validatedQueryStringTrue
    LicenseKeyGive the license key as 0 for testing purposeQueryStringTrue

    Info

    Alternatively, click Save to save all the changes made to API before it is completed. You can come back later to edit it further by selecting the API and clicking Edit.

    To change the state of a partially complete API, select the API and click on the Lifecycle tab. You can update the state of the API to any of the available options. For more information about the states of the API see Manage the API Lifecycle.

  5. Click the Managed API option.

  6. The Implement tab opens. Give the information in the table below.

    FieldSample value
    Endpoint typeHTTP endpoint
    Production endpoint

    This sample service has two operations as CheckPhoneNumber and CheckPhoneNumbers. Let's use CheckPhoneNumber here.
    http://ws.cdyne.com/phoneverify/phoneverify.asmx

    To verify the URL, click the Test button next to it.

    Sandbox endpointhttp://ws.cdyne.com/phoneverify/phoneverify.asmx To verify the URL, click the Test button next to it.

  7. Click Manage and give the information in the table below.

    FieldSample valueDescription
    TransportsHTTP and HTTPSThe transport protocol on which the API is exposed. Both HTTP and HTTPS transports are selected by default. If you want to limit API availability to only one transport (e.g., HTTPS), un-check the other transport.
    Tier AvailabilitySelect allThe API service is available at different levels. They allow you to limit the number of successful hits to an API during a given period of time.

  8. Click Save & Publish. This publishes the API that you just created to the API Store so that subscribers can use it. You can also save APIs without publishing. Publish the API later in the Lifecycle tab or select any of the available options. For more information about the states of the API see Manage the API Lifecycle.

...