com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

Customizing API Store

Owned by Former user (Deleted)
Last updated: May 21, 2013 by Former user (Deleted)Version comment
2 min read

There are several ways in which you can customize the look and feel, features and functionality of the API Store as discussed below:

Changing the theme

API Store is the primary showcase of your organization's published APIs. You can change its overall look and feel using different themes. A theme helps improve the user-friendliness and appeal to a specific users.

The API Store comes with one theme by the name Light in addition to its default theme by the name Fancy. You can also write your own theme from scratch and set it as the default theme, or customize an existing theme by changing its logo, footer notes, About page etc. For instruction on creating/customizing themes, refer to the following tutorial in WSO2 library: http://wso2.org/library/articles/2012/06/api-store-themes.

To incorporate a theme in the API Store, simply log in to the API Store and click Themes in the top, right-hand corner of the window. Then select one from the available list. The theme changes immediately after selection.

New themes added also appear in the list to select from.

Changing language settings

You can change the language of the API Store Web interface to your local language. For configuration steps, see Internationalization and Localization.

Single login for all apps

You can configure single sign-on (SSO) in API Manager so that users who are subscribed to one application can log in to multiple other applications that they are authorized to access, using the same credentials. They do not have to repeatedly authenticate themselves. For configuration steps, see Single Sign-on with SAML 2.0.

Categorizing APIs

When creating an API, providers can add tags to it. Tags allow API providers to group/categorize APIs having similar attributes/behavior/domain. Shown below is an example of how tags are added to an API using the API Publisher Web interface.


Once a tagged API gets published to the API Store, its tags appear as clickable links to the API consumers, who can use them to quickly jump to a category of interest. Tags are visible in the right-hand panel of the API Store. For example,

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.