Versions Compared

Key

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

When creating a particular user creates an API using in the API Publisher, you s/he can set its level of visibility to either Public or Restricted by Roles in the Add New API page .of the API Publisher Web interface as follows:

This allows you to prevent certain user roles from viewing and modifying APIs created by another user role. The two visibility values mean the following:

  • Public : The API is When the API creator publishes this API to the API Store, it will be visible to all subscribers as well as anonymous users of the API storeStore.
  • Restricted by Roles :

    The API is

     When the API creator publishes this API to the API Store, it will be visible only to

    specific roles

    specified user roles in the API Store. When Restricted by Roles is selected, a new field called Visible to Roles appears where you can specify the user roles that have access to the API in a comma-separated list (no spaces).

    Info
    iconfalse
    If you specify the default subscriber role in

...

  • the Visible to Roles field

...

  • . Any user who self-subscribes to the API Store will be able to access the API. That is because the API Manager assigns the subscriber role to all users who sign up to the API Store. 

After a created API is published, it becomes available in the API Store for subscription. Given below is how visibility levels work for users in different tenant modes:

...