Central API Platform

RBC · Senior Product Manager

Central API Platform

6

Product Lines

7+

Downstream Consumers

~50% faster

Integration Time

API ProductsPlatform StrategyAPI ArchitectureVersioningDeveloper Experience

Overview

Helped replace point-to-point integrations with one reusable API contract for a multi-product lending portfolio, reducing duplicated integration work and making downstream status and errors predictable.

The Challenge

Each lending product had built its own point-to-point connections. Consumers received different shapes of the same facts, and every integration repeated decisions about authentication, error handling, versioning and status.

The Approach

Treated downstream teams as users and defined a shared contract covering authentication and authorisation, request validation, response formats, rate limits, status tracking, exceptions and backward compatibility. Recorded architecture decisions and schemas, and tested contracts before consumers built against them.

Key Outcomes

  • Defined one contract serving six product lines and more than seven downstream consumers.
  • Product integration became about 50% faster in the year-end review.
  • Standardised authentication, validation, status, error, throttling and versioning conventions.
  • Maintained backward compatibility and regression-tested changes across consuming systems.

The Result

A single API contract served six product lines and seven-plus downstream consumers without breaking changes during the work. Integration time was about 50% faster in the year-end review, and the pattern was reused by later lending integrations.