The gateway
Receives every call, applies the security and traffic policies and routes it to the back-end service.
VOGO eBS API Gateway
API — Application Programming Interface, the interface through which applications exchange data. An API gateway is the single gate every call to these interfaces goes through: it checks their identity, limits their traffic, routes them and logs them.
Installed at the organisation. APIs are published once and consumed safely by internal applications and by partners.
Every API goes through the gateway: the request is authenticated, checked against the usage plan of the application making it, transformed if needed and routed to the service that answers. No application talks directly to the back-end systems anymore.
Teams publish APIs from a single console, with versions and states — created, published, deprecated, retired —, and internal developers and partners find them in the portal, create their applications, get the keys and test them on the spot.
Every call stays logged: who called, what, when and with what result. Reports show usage per API, per application and per consumer, and errors and latencies show up at once.
Publishing. Securing. Control. Measurement.
Routing requests to back-end services, JSON and XML transformations, mediation and load balancing.
OAuth 2.0, JWT, API keys, basic authentication and mutual TLS, with access scopes on each resource.
Usage plans per application and per consumer, request limits and protection against traffic spikes.
Several versions of the same API in parallel and controlled states: created, published, deprecated, retired.
The API catalogue, documentation, application subscription, key generation and testing straight from the portal.
Synchronous and asynchronous APIs, exposed uniformly, including old SOAP services published as REST.
Several APIs grouped into a single product, with its own usage plan and conditions.
Calls, errors and latencies per API, per application and per consumer, with reports and alerts.
Traffic through the gateway feeds the inventory and detection of VOGO eBS API Security.
Rejected calls, abuse and authentication errors reach VOGO eBS SIEM, correlated with the other events.
Users and applications authenticate with the same accounts and roles as in the rest of the VOGO eBS suite.
APIs for data exchange with other institutions are published, secured and audited from a single place.
Support, updates and training are provided by VOGO, as the product’s manufacturer.
Receives every call, applies the security and traffic policies and routes it to the back-end service.
API design, versions, lifecycle states and the policies of each.
The API catalogue, documentation, application subscription and access keys.
Issuing and validating OAuth 2.0 and JWT tokens, linked to the organisation’s identity.
Calls, errors and latencies, per API, per application and per consumer.
The product uses as mature open-source libraries: WSO2 API Manager.
It is the VOGO product for publishing, securing and governing APIs: all calls to the organisation’s interfaces go through a single point, which checks identity, applies traffic limits and logs every call.
API Gateway controls the traffic it receives: who has access, how much and to what. API Security watches all API traffic, including what does not go through the gateway, and detects attacks. Used together, the gateway blocks, and API Security sees and correlates.
Yes. VOGO eBS API Gateway is an integrated product, developed, licensed and supported by VOGO, with VOGO modules, console and support. The product uses as mature open-source libraries: WSO2 API Manager.
On premise, in the organisation’s infrastructure, on virtual machines or in containers. Calls and data never leave it.
Request a demo on your organisation’s APIs.
Note: The services are provided in line with the European DNSH principle – “Do No Significant Harm”, in accordance with Article 17 of Regulation (EU) 2020/852 on the establishment of a framework to facilitate sustainable investment and with the European Commission’s technical guidance on the application of the DNSH principle, C/2023/111.