Skip to main content
    Back to All Solutions

    iShield Solutions Series, Platform & AI · Integration

    API, Integration & Event Platform

    API gateway, iPaaS, event bus, connectors and EDI on one sovereign runtime.

    Talk to Sales
    Overview

    What this solution does

    API management, integration flows, event streaming, managed connectors and business-to-business exchange on one Link runtime — under one identity, policy and audit approach, so each style of integration is governed the same way.

    Why this composition: API, iPaaS, event and EDI sound like four products because most vendors sell them that way. Run on one runtime with one identity, audit and residency plane and the per-tool integration tax disappears.

    • Enterprise challenge

      Four tools, four rulebooks

      APIs, flows, events and partner exchange are often run on separate tools, each with its own access model and logs.

    • Enterprise challenge

      Partners onboarded by hand

      Every new partner format becomes a project, and reconciliation happens in spreadsheets.

    • Enterprise challenge

      Events nobody can replay

      When a consumer misses events, recovery means asking the producer to send them again.

    How it works

    Four integration styles, one control plane

    APIs, flows, events and partner documents each follow their own path — and all of them pass through the same identity, policy, schema and audit controls.

    • Interface
    • Policy check
    • System
    • Event
    • Integration service
    • Evidence

    1. 01 InterfaceAPI

      Consumer calls an API

      An internal application or partner calls a published API with registered credentials.

      Who acts, controls and evidence
      Who acts
      API consumer, under its registration
      Evidence
      Call record
      Module: API Management & Developer Portal

    2. 02 Policy checkAPI

      Gateway policy

      Authentication, scope and rate limits are applied before the request is routed.

      Who acts, controls and evidence
      Decided by
      Rules set by the API owner and security team
      Control
      Credentials, scopes, rate limits
      Evidence
      Decision record
      If it fails
      Refused or throttled calls receive a clear response and are recorded.
      Module: API Management & Developer Portal

    3. 03 SystemAPI

      Backend service responds

      The request reaches the right backend and version; the response returns through the gateway.

      Who acts, controls and evidence
      Who acts
      Service owner

    4. 04 EventFlow

      Trigger

      A schedule, event or call starts an integration flow.

      Who acts, controls and evidence
      Who acts
      Integration team defines triggers
      Module: iPaaS (Flows, Connectors)

    5. 05 Integration serviceFlow

      Flow version runs

      The released version of the flow maps and routes the data between systems.

      Who acts, controls and evidence
      Who acts
      Integration developer
      Control
      Versioned flows and environments
      Evidence
      Run history
      If it fails
      A failed run is retried or held for review with its reason.
      Module: iPaaS (Flows, Connectors)

    6. 06 SystemFlow

      Connected apps updated

      Managed connectors deliver the result to the applications involved.

      Who acts, controls and evidence
      Who acts
      Application owners
      Evidence
      Delivery acknowledgement
      Module: Connector Hub (200+)

    7. 07 EventEvent

      Producer publishes

      A system publishes a business event to a topic.

      Who acts, controls and evidence
      Who acts
      Event owner
      Module: Event Bus (Kafka / AMQP-compatible)

    8. 08 Policy checkEvent

      Schema check

      The event is checked against its registered schema and version.

      Who acts, controls and evidence
      Decided by
      Event owner maintains the schema
      Control
      Registered schemas and compatibility rules
      If it fails
      Non-conforming events are rejected or quarantined.
      Module: Schema Registry & Replay

    9. 09 Integration serviceEvent

      Subscribers consume or replay

      Subscribers receive the event; a consumer that missed events can replay them within the retention window.

      Who acts, controls and evidence
      Who acts
      Consuming teams
      Evidence
      Event history
      Module: Schema Registry & Replay

    10. 10 InterfacePartner

      Partner document arrives

      A partner sends an order, invoice or status message over an agreed channel and format.

      Who acts, controls and evidence
      Who acts
      Partner, under its agreement
      Module: B2B / EDI (EDIFACT, X12, AS2, PEPPOL)

    11. 11 Integration servicePartner

      Validate and translate

      The document is validated and translated into the internal format.

      Who acts, controls and evidence
      Who acts
      B2B integration team
      Control
      Partner profiles and mapping rules
      If it fails
      Invalid documents are rejected with a reason the partner can act on.
      Module: B2B / EDI (EDIFACT, X12, AS2, PEPPOL)

    12. 12 EvidencePartner

      Reconciled business record

      The business record is created and reconciled against what the partner sent.

      Who acts, controls and evidence
      Who acts
      Business operations
      Evidence
      Reconciliation record

    13. Shared control plane · applies to every lane

      Shared identity, policy, schema and audit

      Every lane uses the same identity, access rules, versioning and audit records.

    Illustration of four integration styles sharing one control plane — not a product screen. Supported protocols, formats and delivery behaviour depend on implementation and configuration.
    What it does

    Core capabilities

    API lifecycle

    Design, secure, publish and monetize APIs, with mTLS, OAuth and rate limits where configured.

    Low-code iPaaS

    Visual flows with versioning, environments and CI/CD release.

    Event streaming

    Topics, schemas and replay windows; delivery behaviour depends on the configured event pattern.

    EDI & partner onboarding

    EDIFACT, X12, AS2, SFTP and PEPPOL exchanges with reconciliation, where the partner format is supported.

    Roles

    • Head of Integration

      Owns the integration estate and its operating model

    • Head of Architecture

      Sets integration patterns and standards

    • Integration developers

      Build APIs, flows, event handlers and partner mappings

    • Security team

      Sets access, credential and audit rules

    • Partner managers

      Onboard partners and agree formats

    What it composes

    Modules included across iShield

    This solution composes capabilities from the platforms below. Each module links to its place in the platform's module index.

    Governance & recovery

    Controls, failures and recovery

    Governance and security

    • One access model for APIs, flows, events and partners
    • Every release versioned and approved through the integration lifecycle
    • Credentials managed centrally and rotated without code changes

    Failures and recovery

    • A backend or partner is unavailable: Calls fail with a controlled response; flows and documents are retried or held for review.
    • A consumer misses events: It replays them within the retention window instead of asking the producer to resend.
    • A partner document is invalid: It is rejected with a reason the partner can act on.

    Reference frameworks

    Context only — no certification or conformity statement.

    OpenAPI
    Describing published API contracts.
    AsyncAPI
    Describing event channels and messages.
    OAuth 2.0 and OpenID Connect
    Authorisation and sign-in at API boundaries.
    OWASP API Security Top 10
    Reviewing API design and gateway policy.
    Cross-platform boundaries

    Who owns what

    • Systems of record keep their own data; Link carries the exchanges between them.
    • Exchanges with other iShield platforms depend on how they are implemented and configured.
    Business outcomes

    What changes

    • One operating model for four integration styles
    • Partners onboarded through reusable profiles
    • Recovery from consumer outages without manual re-sends

    Bring API, Integration & Event Platform to your enterprise

    Discuss how this solution fits your integration estate, and the phased delivery and deployment options for your environment.

    Your privacy choices

    We use strictly necessary storage to run this website. With your permission we also use first-party analytics to understand which pages are useful. Analytics stays off unless you choose "Accept all" or turn it on in "Manage". You can change your choice at any time from "Cookie settings" in the footer. See our Privacy Policy.