## [Shell Developer Portal (2026)](/nominees/2026/shell) ![Screenshot of Shell Developer Portal's hero section](/sites/default/files/styles/nominees_image/public/2026-09/Screenshot%202026-09-07%20at%2011.04.00.png?itok=bGJvCW-C) Owner Shell [ Visit the portal ](https://developer.shell.com/) ## NOMINEE OVERVIEW The Shell Developer Portal is the primary destination for developers, partners, and business stakeholders looking to discover and integrate Shell's digital capabilities. The developer portal is the single entry point for integrating with Shell's B2B Mobility and energy digital capabilities — spanning Fleet Card Management, Digital Payments, Transaction Data & Reporting, and EV/Recharge, alongside APIs from Loyalty, Lubricants, and Shell Aviation. Rather than exposing each business line as a disconnected system, the portal gives external partners, client IT teams, and internal Shell teams one consistent path from discovery to production: a unified API & Product Catalog with interactive testing, SDKs in six languages with dedicated AI chat support, an AI-powered coding assistant (API Copilot MCP) for tools like VS Code and Cursor, Salesforce-backed ticketing, proactive change notifications, and support in 16 languages. The portal exists to turn Shell's organically-grown, multi-business-unit API portfolio into one dependable, navigable developer experience. ## NOMINATION RATIONALE ### 1) BEST REIMAGINED ONBOARDING EXPERIENCE IN A DEVELOPER PORTAL **Why is this category a strong match?** The Shell Developer Portal excels at helping users get started. Onboarding begins with discovery, helping both technical and business users understand what Shell APIs can do, whether they fit a specific use case, and how to get started. Users can explore business-focused content, use cases, AI-powered semantic search, API overviews, multilingual content, Quick Start Guides, and self-service onboarding journeys that reduce the effort required to move from evaluation to implementation. We also believe onboarding does not end with obtaining credentials or making a first API call. The portal supports the full journey from discovery and evaluation through implementation, support, maintenance, and ongoing product discovery. Integrated support processes, release notes, API notifications, and MCP capabilities help users remain successful long after their initial integration. By combining business discovery, AI-assisted findability, self-service onboarding, implementation guidance, support, and lifecycle communications, the Shell Developer Portal has evolved from a documentation destination into an adoption platform for Shell's digital capabilities. **In what ways does the portal shine in this category?** The Shell Developer Portal excels at helping users get started. Onboarding begins with discovery, helping both technical and business users understand what Shell APIs can do, whether they fit a specific use case, and how to get started. Users can explore business-focused content, use cases, AI-powered semantic search, API overviews, multilingual content, Quick Start Guides, and self-service onboarding journeys that reduce the effort required to move from evaluation to implementation. We also believe onboarding does not end with obtaining credentials or making a first API call. The portal supports the full journey from discovery and evaluation through implementation, support, maintenance, and ongoing product discovery. Integrated support processes, release notes, API notifications, and MCP capabilities help users remain successful long after their initial integration. By combining business discovery, AI-assisted findability, self-service onboarding, implementation guidance, support, and lifecycle communications, the Shell Developer Portal has evolved from a documentation destination into an adoption platform for Shell's digital capabilities. ### 2) BEST UNIFIED OR FEDERATED ENTERPRISE DEVELOPER PORTAL **Why is this category a strong match?** We didn't build the Shell Developer Portal from a blank slate with one clean architecture in mind. It grew out of several Shell businesses that had already been running their own systems for years — Fleet Solutions with its card platform, EV with the Recharge network, plus Loyalty, Lubricants and Aviation each doing their own thing. Different backends, different login methods, different teams. When we started pulling this together into one portal, the goal was never to force everything to look identical. It was to make sure a developer coming in from outside doesn't have to figure out five separate systems just to get one thing working. The Shell Developer Portal unifies API access across multiple, independently-run Shell business lines — Mobility/Fleet Solutions (Card Management, Digital Payments, Transaction Data & Reporting), Shell EV/Recharge, Loyalty, Lubricants, and Shell Aviation — into a single, coherent developer experience. Each business line has its own product roadmap, customer base, and backend systems, yet developers interact with all of them through one consistent onboarding flow, one API/Product Catalog, one notification system, and one Salesforce-backed support model. Rather than forcing every domain into identical technical patterns, the portal lets each product expose its own capabilities while keeping the navigation, documentation structure, integration lifecycle, and even language localization consistent across every business line and market. This is precisely the "federated but coherent" outcome the category rewards. **In what ways does the portal shine in this category?** The product catalog covers four pretty different product lines (EV, Card Management, Data & Reporting, Digital Payments), and even though they come from separate teams internally, every product page follows the same layout, has interactive testing built in, and comes with SDKs in six languages. Once someone's used one product page, they already know how to use the rest. A unified SDK layer over heterogeneous services: SDKs in six languages (Java, .NET, TypeScript, PHP, Python, Ruby) wrap different authentication models behind one consistent developer experience. We have also put a fair amount of work into AI, and not just as a chatbot bolted on the homepage. There's a general assistant for browsing the catalog, but there's also a chat scoped specifically to each SDK, so once you pick your language it can actually answer questions about that SDK. Internally we use AI to help draft quick-start guides as new APIs come online, and our marketing team uses it to help keep content consistent across all these different product lines, which matters a lot when you've got this many business units feeding into one portal. Localized for a global federation: available in 16 languages (including machine-translated Beta coverage), so developers in any market get the same unified experience in their own language. Support was something we took seriously early on. Every ticket raised through the portal goes into Salesforce, so it's tracked properly and someone on our support team actually investigates and replies, rather than it disappearing into an inbox somewhere. We also made a deliberate call on where to invest advanced tooling like notifications and ticketing, focusing that on Mobility first rather than trying to do everything everywhere at once. 2026