This topic lists frequently asked questions and provides answers.
Exchange provides a drafts feature. Content in the draft state is hidden until the draft is published.
One user can create drafts and share the URLs with a second user, and the second user can review and publish these pages.
All contributors have the same permissions, including the permission to publish drafts. The separation of duties is not enforced by Exchange and must be observed by the users.
Users can delete a draft, which discards all changes made in the draft.
The MuleSoft Developer Portal is at https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/.
If you are an Anypoint Platform Organization Administrator or Exchange Administrator, when you first log into Exchange, Exchange creates a Public Portal for you. The link to the portal appears in the left navigation bar. After you add API assets to the portal, it becomes visible to the Internet. See Why don’t my assets appear in my Public Portal? for how to add assets to the portal.
The URL for your portal is in the form
You can add SOAP API, HTTP API, AsyncAPI, and OAS or RAML REST API assets to the Public Portal by clicking the Share button and clicking Add to the public portal. When you share an asset to the Public Portal, the asset is then public and visible by anyone on the internet at the URL of your Public Portal.
Click the asset in Exchange and click Share. Click Add to the Public Portal. Click the API version field checkbox to uncheck the field. Click Share. In Exchange, refresh the browser screen and you can see that the Visibility setting in the asset’s Overview has changed to Private.
After changing the name for an asset, press the Return (or Enter) key on your keyboard. If you don’t press Return, Exchange reverts the asset name back to what it was before you changed it.
You can use RAML data types, but not a JSON referenced by another JSON schema.
Exchange only works in Windows with the latest versions of Chrome, Firefox, and Internet Explorer 11. IE 9 is not supported and displays Exchange incorrectly.
You can upload an SVG icon with the icon classifier using a PUT to the Exchange REST API. Exchange adds the round border around the icon. You need to pass the authorization header with a bearer and access token.
For example, add the icon file to the HTTP body and use a PUT such as:
You can use the Exchange Experience API to detect the difference if it exists so you don’t republish to Exchange when there is no change.
Help us improve with your feedback.