Network API Portfolio
Home > Projects > Network API Portfolio

Network API Portfolio.

Network API Portfolio

A dual-platform web ecosystem streamlining supplier management and API discovery across two audiences and two backend systems. A CAMARA-compliant developer hub that unifies API discovery, onboarding, and testing — enabling partners to go from intent to integration in hours, not weeks.

1 / 2
Back to Work
Date 2026
Client Vodafone Group Commercial
Category Developer Portal · SharePoint & Eloqua
Tags UX/UI, B2B, API, Vodafone, Developer Portal

Network API Portfolio

(Vodafone Group Commercial)

01

No Unified Access to Vodafone's Network APIs

Vodafone partners struggled to discover and access network APIs. No unified portal existed – each API had its own documentation style, auth method, and testing environment. Nothing was consistent, and manual provisioning created weeks of delay at every integration point.

Fragmented Access – Partners had no single place to discover, onboard, or test APIs. Every new integration required manual support intervention.

No Standardisation – Each API team maintained its own documentation. No shared auth patterns, no consistent sandbox environments, no unified developer experience.

The Objective: Design a CAMARA-compliant, self-service developer hub that unifies all Vodafone network APIs – enabling partners to discover, onboard, and test without any manual provisioning.

Network API Portal – key screens
02

Build Once. Integrate Once. Scale Everywhere.

One Portal. Every API. Zero Friction. – A CAMARA-compliant developer hub that unifies API discovery, onboarding, and testing in one authenticated environment. Partners generate keys, explore sandboxes, and manage subscriptions without manual provisioning.

Three User Types – Structured the portal around partners, internal developers, and admins – with distinct flows, dashboards, and permission levels for each audience.

Stakeholder Research – Ran workshops with Vodafone product managers, partner developers, and API ops teams to map pain points and define success criteria.

Information Architecture – Built a dual-portal model: a public partner-facing API catalogue and an authenticated developer environment – sharing a common design system but serving distinct needs.

Network API – full presentation
03

Structuring a Developer Experience at Scale

PhaseAction & Outcome
Stakeholder ResearchWorkshops with Vodafone PMs, partner developers, and API ops. Mapped all pain points and defined success metrics for both partner-facing and internal-facing flows.
Information ArchitectureStructured the portal around 3 user types – partners, developers, admins. Built separate entry points with shared underlying design system and auth layer.
CAMARA ComplianceAligned all API schemas, documentation formats, and onboarding flows with CAMARA open-gateway standards – enabling interoperability across Vodafone Group markets.
Self-Service FlowsDesigned end-to-end self-service onboarding: API key generation, sandbox provisioning, and subscription management – eliminating all manual intervention from the partner journey.
04

Measurable Developer Experience Gains

64% reduction in task completion time vs the legacy toolset – validated through usability testing with partner developers across 3 integration scenarios.

3× faster partner onboarding – From weeks of manual provisioning to days of self-service access. Partners can generate keys, explore sandboxes, and submit for production access without a single support ticket.

40+ Countries – CAMARA-compliant architecture enables deployment across the full Vodafone Group footprint – a single portal design that scales globally without market-specific rebuilds.

Platform

Web Portal

APIs

3

Onboarding

3× Faster

Countries

40+

05

One Portal or Two?

The core architectural question was whether to build a single unified portal or two distinct products – one for partners and one for internal developers. We resolved this with a dual-entry model sharing a common design system: same components, same tokens, different navigation paths and permission scopes.

CAMARA compliance was treated as a design constraint, not an afterthought – every IA decision was checked against the open-gateway standard, which ultimately made the portal more consistent and predictable for all developer audiences.

Have a project in mind? Let's talk.

Get In Touch

Clients.

Over the years we have worked for and cooperated with various companies from various industries.
Some of them can be found here:

ALTEOASIC MinerzContentodmÉges HelyettHomeMedIpari MarketingLogi StoreMacmillanMagyarok a VilágMedtrendRichmondScanomedShopper ParkVodafoneALTEOASIC MinerzContentodmÉges HelyettHomeMedIpari MarketingLogi StoreMacmillanMagyarok a VilágMedtrendRichmondScanomedShopper ParkVodafone

Let's talk.

Unleashing brand potential through creative design and innovation.

Get In Touch