Publish an API
Publishing an API on API Central consists of two steps; API providers can choose to do one or the other, or both.
Require Authorization to Access an API
Access credentials provide powerful options for managing your API. Here are some examples:
- Fully control which consumer applications are allowed to get access to which resources within the API. Authentication is available at no cost through the management platform. Credentials work with both REST and SOAP styles, and can be added seamlessly on top of other authN/authZ schemes.
- Control the number of requests each consumer is allowed to make. This is achieved through metering (also available at no cost).
- Get usage statistics: who’s using which data, when, and how often. This is essential for capacity planning, and provides accurate insights into what consumers are interested in.
- Identify who consumers are and communicate with them, for instance, to announce new API releases, to warn about down time, or to collect feedback.
Add Interactive Docs for the API
You can choose to publish documentation on some or all of the endpoints of your API.
The API portal goes beyond static documentation by providing an interactive client (based on Swagger) that allows users to work with the API endpoints directly from the browser. That is, users can learn the API and test it without having to write any code. This capability greatly reduces the barrier to entry for potential API consumers.
The documentation can be published for RESTful APIs, whether or not they are managed via credentials.
Contact firstname.lastname@example.org for details.