Scheer PAS API Management

API-Management from Scheer PAS offers you maximum control with the administration and optimization of your programming interfaces.

This comes from the differing levels of access rights for the use and administration of API’s, services and clients. The supply and publishing of agreements (contracts) can also be controlled flexibly and in real time. Access to interfaces is possible via (fixed) contracts as well as via the use of open API’s. The documentation of your API’s is secured over their complete lifecycle with the help of Swagger (Open API Specification)

You benefit from the comprehensive functionality of the Process Automation Suite integration platform. All connected REST and SOAP interfaces are secured via API Management. In addition, REST and SOAP interfaces from other systems can also be administered. You can now offer the flexible use of individual API’s to your developers and partners as well as to your end-customers. Scheer PAS API Management makes possible the direct import of xUML Service endpoints into API-Management.

The availability of policies offers additional benefits for your agility. These are a succession of differing statements that are applied sequentially at diverse points (API, plan, client etc.) and which can be adapted flexibly to specific needs. Policies in API-Management offer the opportunity to adapt the behaviour of an interface quickly and easily.

API-Management procedure with Scheer PAS

The provision of a programming interface takes place in multiple steps. First of all the API must be chosen, or rather, newly created. Following this, a plan, or a group of rules (policies) is defined. In doing so, multiple plans can be defined. The next step is to create a user for the API (customer) and to define a contract. The contract links a specific plan to an API. Any number of contracts can be created per customer.

In order to administer a large number of interfaces, API’s, plans and customers must be classified into groups. These groups are called “organizations”. Users within an organization are allocated rights in the form of roles. For example, a user with the role “API viewer” may view all the API’s in an organization, but not edit them.

The benefits of API-Management

  • Centralized security: via automatically applied guidelines and centralised administration of users, access rights and authentication
  • Version administration: versioning of APIs and clients
  • Scalability: through the use of multiple and specialised gateways
  • Caching: the load in the backend can be reduced through the caching of data-intensive requests or data which seldom changes
  • Optimization:using metrics and access controls performance can be optimized by targeted changes
  • Monitoring of data traffic from individual clients and API’s
  • Simplified statements of account
  • Quota-Limits: offer a way of limiting the total number of requests to an interface. For example, a daily limit of 1,000 requests can be set
  • Rate-Limits: offer a way of ensuring that the backend does become overloaded. For example a maximum of 100 requests per minute – the ideal prevention of denial of service attacks (DOS)
  • Time controlled availability: APIs are only available – or not available – for a freely defined period of time
  • Traffic limitations: limitations on data volume can be set for the API or individual clients

Download the API Management Paper now!

The Scheer API Management offers you full control over the APIs. The whitepaper will show you what modern API management looks like in practice.
On compact 5 pages we explain API Management with Scheer and its components.
Simply fill out the form and we will send you a link to the whitepaper.

API Management in overview