It ensures that the web services used by the organization are defined, available and accessible.
APINIZER opens access to the organizations services through virtual addresses. Therefore, requests go through APINIZER which enables the services to be virtualized and the content to be monitored.
In situations such as structural defects in data, data size exceeding the allowed amount or a SQL injection within the content, APINIZER determines whether there are any threats and acting as a firewall, prevents them from entering the internal systems.
APINIZER can change the format of messages that are received through services and/or messages that return from internal services.
It restricts some of the requests that are delivered to the services on the gateway to prevent the organization's servers from working under excessive load and to ensure that the internal system functions in a stable manner.
Statistical information such as instant requests received on servers, success status of the requests, average data sizes and average response times can be monitored.
APINIZER enables creating automatic alarms for specified durations and conditions on the servers and ensures that relevant subscribers are notified.
If the content of messages are stored, it is possible to conduct full text search in incoming and outgoing messages.
It allows creating source codes for Web Services that use data types defined within the application. This saves software developers from time and errors.
With APINIZER, only authorized users can access service. Authorization can be integrated to the organization's current single-sign-on infrastructure. It can also be made possible for defined users on the application to send data to the service.
It ensures that users are allowed to access the requested sources within permitted authorities. It allows masking and transformation on data and also enables removing unwanted parts of the data.
APINIZER checks the compatibility between incoming messages and data schemas within internal services and detects any issues before being delivered to the application server.
When the establishment requires security, it ensures that only messages which are from IP addresses that are not listed as restricted or blocked can be received by the services within the gateway. The accessible hours for services can also be set by using the gateway.
APINIZER can direct the incoming requests to different servers in order to distribute the load among all servers within the organization.
Optionally, messages received by the services and messages which return from internal services can be stored on APINIZER.