Skip to content
← Tools
Integration & APIs

Interface catalogue builder

Build the inventory every integration programme needs and almost nobody has — then see what it tells you about ownership, partner dependencies and crypto exposure.

4 rows

Interfaces

4

Tier 1

2

Partner-facing

1

No named owner

2

Indicative rebuild effort

19 person-days 2 simple, 1 medium, 1 complex, before any platform friction.

For a platform-to-platform move, run these counts through the migration assessor to add the friction multiplier.

What this catalogue is telling you

  • 1 Tier 1 interface with no named owner

    Revenue-or-regulatory traffic that nobody is accountable for. This is the first thing to fix, and it costs nothing but a conversation.

    Order intake from partner EDI

  • 1 partner-facing interface

    These set the critical path of any migration. You cannot move faster than your slowest trading partner will re-certify, and that is measured in months, not sprints.

    Order intake from partner EDI

  • 2 interfaces carrying data with 7+ year confidentiality

    Traffic captured today must still be secret well beyond most migration plans. These are the interfaces to migrate to post-quantum cryptography first, ahead of the busier ones.

    Order intake from partner EDI · Nightly GL posting

  • 1 Tier 1 interface rated complex

    Highest business impact combined with highest delivery risk. Sequence these first, while there is still contingency left in the plan.

    Order intake from partner EDI

Nothing is stored — not on a server, and not in your browser either. The catalogue lives in this page and leaves only when you export it, so closing the tab discards it. Export as you go. The columns are the ones that get used downstream: criticality and complexity for sequencing, owner for accountability, partner-facing for the critical path, and data retention because that is what decides cryptographic exposure rather than message volume.