apibanking
All customer stories

Transforming how developers work with banking APIs

A leading bank replaced Word documents shared over email with a searchable, AI-ready developer portal. Partner and corporate developers now find, understand and integrate its APIs on their own.

Challenge

The bank offered thousands of APIs to partners and corporate customers, but the developer experience had not kept up. Each API was documented in a Word file, with the actual specs attached as embedded spreadsheets, and then sent out by email.

1,000sof partner and corporate APIs

A huge catalogue, documented API by API in standalone files, with no shared structure.

Weeksjust to find the right API

Partner developers depended on the bank team to point them to the right document, then had to decode it.

Monthsto complete an integration

Integrations dragged on, and much of the bank team’s time went into support instead of building.

BeforeMonths
  1. Request specs by email
  2. Receive a Word document
  3. Open embedded Excel specs
  4. Call to clarify fields
  5. Wait for sample payloads
  6. Call again on error codes
  7. Raise a support ticket
AfterDays
  1. Search the portal
  2. Read the guide
  3. Try it in the sandbox
  4. Subscribe and go live
A partner developer's path from first question to a working integration.

Solution

We rebuilt the experience on an industry-standard docs system. The redesign covered everything from the information architecture down to the exact format of each type of page.

A documentation system built around developer intent

Content strategyShaped around business outcomes and each audience
Information architecture and UXOne structure across all products
Learn and understand
  • ConceptsBank and industry terms, explained
  • Onboarding guideHow a partner gets set up
  • TutorialsLearn by building
Get information
  • API referenceGenerated from the code itself
  • How-to guidesStep by step to an outcome
  • Glossary and FAQsQuick answers
Solve a problem
  • TroubleshootingFixes for common errors
Learning and developmentUpskilling the content team
Every page is organised around what the developer is trying to do, not around the team that owns the API.

Everything in one place

Each product gets its own microsite, which brings together learning, reference, a self-service integration console and a helpdesk.

Learn
  • Product and programme concepts
  • Tutorials
  • Use cases
Use
  • How-to integration guides
  • API reference
  • Process flows
Integration console
  • Business profile and onboarding
  • API subscription
  • Test environment and master data
Helpdesk
  • Raise and track requests
  • Tickets routed to the right team
  • Answers fed back into the docs
AI assistant and MCP serverDevelopers can ask questions in plain language, or connect their own AI tools straight to the docs.

An operating model that keeps it current

Product-aligned squads

Each product microsite has a dedicated content squad working with the product and engineering teams that own the APIs.

Shared standards

A central team owns the information architecture, UX, style guide and quality, so every microsite feels like one portal.

A closed loop

Support tickets go back to the squads, so every question a developer asks makes the docs better.

Results

Developers now go from first question to a working integration without leaving the portal. The bank's teams spend less time on support and more time launching products.

Illustrative product page with getting started steps, a flow diagram and overview
Product pages start with concepts and flows before the API detail.
Illustrative API catalogue mapped against journeys, with an assistant answering a question
APIs mapped to journeys, with an assistant that answers in context.
Found in seconds

Every API can now be searched, browsed by product and journey, and linked to directly. No inbox required.

Integrations in days

Concepts, guides, references and a sandbox in one place mean developers can build without waiting on the bank.

Less support load

Fewer clarification calls and tickets free the bank team to focus on new products and partners.

AI-ready by design

Structured, MCP-compatible content lets developers query the docs with AI tools and generate working code from them.

Want developers to love your APIs?