How Do European Banks Create An Awesome Developer Experience for Open Banking APIs?

For developers to embrace their APIs, banks need to invest in creating an awesome developer experience (DX).

Get it right and banks can differentiate themselves from the crowd by building sustainable developer communities. Get it wrong and they may struggle to keep up with the competition.

So what makes an awesome API Developer Experience?

The article Building Effective API Programs: Developer Experience (DX) provides a good explanation of the key elements that contribute to a positive developer experience.

To provide an overall best practice guide, I have embellished the main themes from this article with other best practices from additional reference sources.

API Design

The article Why API Developer Experience Matters More Than Ever suggests the following measurements can help validate a well designed API;

  1. Task Invocation Ratio
    • Minimise the number of API calls required to achieve a developer goal.
  2. Structure
    • Ensure the developer can easily navigate the request/response to add or access information.
  3. Developer Stack Size
    • Minimise the number of additional tools and libraries.
  4. Error Handling
    • Provide helpers for the developer to track errors and identify where they are happening.
  5. Vocabulary
    • Minimise the vocabulary the developer needs to understand to use the API.
  6. Filtering
    • Create filters to help the developer access the data they require more efficiently.
  7. Search
    • Allow data to be searched via the API.

Developer Portal

This is the main developer entry point to sign up, access and use the API.

  1. API Design
    • The API should be standards based, well designed, flexible and simple to use.
  2. On-boarding
    • Clear explanation of the purpose and benefits of the API.
    • Ability to try the API pre-signup.
    • Easy on-boarding, simple and frictionless to get started.
  3. Documentation
    • Getting started guides and quick start tutorials
    • Interactive API documentation based on industry standards (i.e Swagger/OpenAPI).
    • Code snippets that can be cut and pasted.
    • Diagrams and detailed tutorials to explain complex concepts that form part of the API, such as OAUTH exchanges.
    • Developer friendly language in documentation and avoid an authoritative tone.
  4. SDKs
    • Software Development Kits (SDKs) for popular languages.
  5. Diversity
    • The DX should cater for language, gender, race, disability, ethnicity, etc.
  6. Dashboard
    • A dashboard provides developers with key information, such as their requests, callbacks and log information for anything that has gone wrong. This can help developers save time.
    • Provide metrics on the reliability of the API.
  7. Feedback Loop
    • Provide developers with a feedback loop to help them raise and track issues or ideas to further improve the developer experience.

Community Building

Community building is enabled through physical and virtual interactions with developers.

  1. Physical Interations
    • Developer events/conferences, hackathons, workshops, boot camps, etc
    • Face to face developer meetings
  2. Virtual Presence
    • Chatrooms, such as a Slack channel can help developers share best practice, ask questions and collaborate.
    • Webinars

Developer Evangelists

The developer evangelist is described by Manfred Bortenschlager as a “technology person trapped inside a marketing person’s body”. The evangelist provides:

  1. Diverse Skill-Set
    • Passion
    • Coding
    • Strong web presence
    • Public speaking comes naturally
  2. Events
    • Presents and give talks
    • Organises and hosts hackathons and developer days
  3. Communication
    • Newsletters and blogs
    • RSS Feeds
    • Social media comms
    • Videos and webinars
  4. Content Creation
    • Sample code
    • Tutorials
    • Quick start guides
  5. Market Sensing
    • Feedback loop to improve the developer experience

Pilot Partners and Case Studies

Pilot partners are early adopters who can help test and provide initial feedback to improve the APIs and experience. They can also be used to provide early case studies for marketing and promotional activities.

Acceleration via Ecosystem Partners

Identify alliances and partnerships that can be formed with complementary APIs that can extend the value offered to developers.


Measurement helps understand the effectiveness of the developer portal. Measures can include:

  1. Page visits
  2. Signups
  3. API traffic
  4. Support Requests

Evaluation Framework

In future articles, we will be using these themes to develop a scorecard. This will allow us to evaluate bank DXs in a methodical way and determine who is truly creating awesome DXs.

Best In Class Developer Experiences

The following are examples of best in class developer experiences;








Google Maps


Recommended Articles

The following articles provided the reference material for this blog;

PSD2: A List of European Bank API Developer Portals

Why Every API Needs a Dashboard

Developer Experience Matters

Building Effective API Programs: Developer Experience (DX)

Why API Developer Experience Matters More Than Ever

User Personas for HTTP APIs

Patterns of Developer Experience

%d bloggers like this: