Skip to main content
Attention:You’ve reached a page related to the Tyk Classic Portal. If you were searching for API documentation of the new Tyk Developer Portal please use the latest Postman collection page.

Future deprecation of Tyk Classic PortalThis product is no longer actively developed as it has been superseded by the new Tyk Developer Portal.
Please note that the Tyk Classic Portal now has limited support and maintenance. Please contact us at support@tyk.ioif you have any questions.
The API Catalog is part of the API Developer Portal of the Dashboard. It is the central place for you to manage which APIs your registered developers have access to. The API catalog is completely separate from the regular API list section of the dashboard, as you may only wish to expose some of those APIs managed by Tyk to end users. API Catalog entries are not actual directly tied to APIs in any way, they are connected to policies. The reason for this is that policies can give access to a bundle of underlying APIs and therefore can represent a facade of services exposed as a single interface. The concept of the API Catalog is that you publish what you wish your external APIs to appear as. So, for example, if you have a widgets API that is composed of 4 microservices (i.e. /comments, /pricing, /details, and /SKU), which are managed as four separate APIs in your Dashboard, but combined under a single Security Policy (so one token can access all four APIs), then you may not wish to have your users know these are microservices, they are just endpoints in your widgets API. This approach allows you to separate “management” from “consumption” using a simple CMS-based bundling approach.