TREN
Ferra

Ferra API

An enterprise API management platform: API gateway, security and policy engine, message transformation, lifecycle management, developer portal and analytics in a single product. All services the institution exposes internally and externally are managed in one layer.

Solution

What we provide

Ferra API sits in front of all of the institution's services as a single API gateway. Authentication, authorisation, quotas and rate limiting, message validation and transformation, caching, fault tolerance and logging are applied to services as policies without writing code. Services are versioned and managed from design to retirement, published through the developer portal and monitored with real-time analytics.

  • All services in one security and policy layer; service code is untouched
  • SOAP services republished as REST, REST services republished with different schemas
  • Developer portal accelerates partner and customer integration
  • Usage, performance and access reports ready for audit

Ferra API covers the entire API lifecycle. Services are imported from an OpenAPI or WSDL definition or from an existing endpoint; security, traffic, transformation and monitoring policies are defined and assigned on screen; versions are published side by side and retired in a controlled manner. The gateway is horizontally scalable, multi-environment (development, test, production) and deployed on-premises. It is used for open banking and corporate customer APIs in banking, and for partner and channel integrations in other sectors. Deployed together with Ferra Ledger, API calls are kept as immutable records and serve as evidence in disputes.

  • API gateway: single-point publishing of REST, SOAP and gRPC services; horizontal scaling and load balancing
  • Security policies: authentication, authorisation, API keys, IP and content filtering, threat protection
  • Traffic management: rate limiting, quotas, throttling, caching, circuit breaker and retry
  • Message validation and transformation: schema validation, SOAP↔REST and XML↔JSON conversion, header and body mapping, service aggregation
  • API lifecycle: design, OpenAPI/WSDL import, versioning, multi-environment publishing, retirement
  • Developer portal: automatic documentation, subscription and approval flow, sandbox, API key management
  • Monitoring and analytics: real-time traffic, latency and error dashboards, request/response logging, alerts, SLA reports
  • Open banking: consent and approval flows, regulatory reporting templates
  • Ferra Ledger integration: the origin, integrity and time of API calls are kept as immutable records